Stats
Actions
Tags
From supersaiyan
Append a discovered-but-out-of-scope bug to .supersaiyan/discovered-bugs.md so it is never silently ignored. Use whenever investigation surfaces an issue unrelated to the current task — for example, a separate broken feature spotted during UI verification.
How this skill is triggered — by the user, by Claude, or both
Slash command
/supersaiyan:log-unrelated-bugThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You have discovered an issue that is **out of scope** for the current
You have discovered an issue that is out of scope for the current task. Do not silently ignore it and do not fix it during this task. Append a structured entry to the project bug log so it surfaces later.
Ensure the log directory and file exist:
mkdir -p .supersaiyan && touch .supersaiyan/discovered-bugs.md
Get the current ISO date for the entry header:
date -Iseconds
Use the Write or Edit tool to append an entry in this exact format (read the file first if it has existing entries; preserve them):
## <one-line title> — <ISO date from step 2>
**Description:** <what was observed vs expected, 1-3 sentences>
**Steps to reproduce:**
1. <step>
2. <step>
**Found during:** <task or route you were investigating>
**Status:** unreviewed
**Discovered by:** supersaiyan/<agent name or "main">
---
Tell the user in one sentence what was logged. Example: "Logged unrelated bug 'Login form does not submit on Enter' to .supersaiyan/discovered-bugs.md. Continuing with original task."
Resume the original task.
ui-validator found it,
say supersaiyan/ui-validator. If the main agent found it, say
supersaiyan/main.npx claudepluginhub florian60430/supersaiyan --plugin supersaiyanCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.