Help us improve
Share bugs, ideas, or general feedback.
From unity-coding-skills
Diagnoses and fixes bugs using a test-first workflow: reproduce with a failing test, diagnose root cause, then fix.
npx claudepluginhub nowsprinting/unity-coding-skills --plugin unity-coding-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/unity-coding-skills:fix-bugThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Guide for diagnosing and fixing bugs. This skill defines a test-first debugging workflow:
Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
Guide for diagnosing and fixing bugs. This skill defines a test-first debugging workflow: reproduce the bug with a failing test, diagnose the root cause, then fix it.
This skill must be used outside plan mode. Before doing anything else, check the current mode:
ExitPlanMode is NOT in the deferred tools list (i.e., directly callable) → in plan mode → stop immediately and tell the user:
"This skill (
/fix-bug) must be used outside plan mode. Please exit plan mode first."
ExitPlanMode is in the deferred tools list → not in plan mode → proceed.Do not read code files during this step. You may only read specs and design docs.
Extract the following from the user's prompt:
If any of the three cannot be determined from the prompt, use AskUserQuestion to ask
the user before proceeding. All three must be known before moving to Step 2.
Also determine the report type:
Also check the relevant documentation (specs, design docs) for consistency with the
user's bug report. If the documentation and the report conflict, use AskUserQuestion
to clarify with the user which is correct. If the docs contain errors or are missing
relevant information, add them to the list of files to be modified in this bug fix.
Skip this step if Step 1 identified this as an existing test failure case. Proceed directly to Step 3.
Search the project's test code for existing tests closest to the bug scenario. These serve two purposes:
When the bug condition involves on-screen display or a user-facing UI operation, search for integration tests with UI operations or visual verification tests — the reproduction test must be at that layer, so the placement anchor and style reference must be too.
Use Explore agents to locate relevant test files and test cases.
Load the test-designing-guide skill to design the reproduction test case, then load test-writing-guide to implement it. Place the reproduction test near the similar tests found above.
If an existing test is testing the wrong behavior (i.e., the test itself is buggy), rewrite that test to correctly reproduce the bug rather than adding a new one.
Run tests using the /run-tests skill and verify that the reproduction test fails:
If multiple tests fail and it is unclear which one corresponds to the reported bug, use
AskUserQuestion to ask the user which test to focus on.
If reproduction has been attempted 3 times without success, return to Step 1 and
use AskUserQuestion to re-clarify the bug report with the user.
Present the reproduction evidence to the user via AskUserQuestion before proceeding.
Include:
Once the user confirms the reproduction is as expected:
With the reproduction confirmed, investigate the root cause:
Before applying the fix, check whether the affected area has adequate coverage for adjacent behavior:
/run-teststest-deduplicator agent with: list of test files added or modified in this iterationwarning or higher severity level: for each modified file,
run mcp__jetbrains__open_file_in_editor → mcp__ide__getDiagnostics → fix as a single set, one file
at a time (opening all files at once exceeds the editor tab limit).
Use mcp__ide__getDiagnostics rather than the Unity compiler output because the Unity editor compiler does not reflect .editorconfig severity settings./run-tests command to confirm they still pass/simplify skill (Skill({skill: "simplify"}) — not a plugin skill) to apply quality improvements to the modified code/run-tests command to confirm they still pass