| name | zno-fix |
| description | Use when the user writes /zno-fix or reports a bug or defect. Reproduces or reasons about the defect, locates the root cause, fixes it with a regression test when possible, verifies the fix, and updates the changelog if behavior changed. |
Zno-Fix โ Bug Fix
<skills-root> below means the directory containing all zno-* skills (e.g. ~/.claude/skills or ~/.agents/skills).
Workflow
- Restate the defect briefly: expected vs actual behavior.
- Reproduce the defect, or when reproduction is impractical, reason about it from the code path and state the assumption explicitly.
- Locate the root cause before writing the fix. Do not patch symptoms.
- If the project has a test framework configured, write a failing regression test that captures the defect, then fix minimally until it passes.
- Verify: run the relevant tests/build and check the original reproduction path.
- Keep docs lightweight for fixes: update
docs/development/03-feature-changelog.md if behavior changed (scaffold it first with --scaffold feature if missing). Only touch other docs when the fix changed rules, structure, or operations (mapping in references/docs-map.md).
- Before marking the task complete, satisfy the verification gate in
references/verification.md (at least 2 pieces of evidence).
- If the fix affects user-visible UI or browser workflows, the final response must include page-level manual test steps (template in
references/verification.md).
Even when the user says to skip docs for a tiny fix, keep the change small and still update the changelog if behavior changed.
Shared references (read only when needed)
<skills-root>/zno-init/references/docs-map.md โ full doc set, doc update rules, scaffold triggers.<skills-root>/zno-init/references/verification.md โ verification gate and final-response page test steps.
