// Formats concise GitHub issue titles and descriptions. Use when turning a problem into a tracking issue.
Systematic evidence-based debugging using runtime logs. Generates hypotheses, instruments code with NDJSON logs, guides reproduction, analyzes log evidence, and iterates until root cause is proven with cited log lines. Use when the user reports a bug, unexpected behavior, or asks to debug an issue.
Formats commit titles and descriptions using Conventional Commits. Use when suggesting or writing git commit messages.
Retrieves up-to-date docs for libraries and frameworks. Use when checking current Fastify, Vitest, Zod, or Node APIs before coding.
Removes overengineered or noisy AI-generated code from recent backend changes. Use when a diff reads as too defensive or too abstract.
Helps discover and install useful agent skills for this repo. Use when a user asks how to do a recurring task or asks whether a skill exists for Fastify, Vitest, Zod, security review, or similar backend workflows.
Resolves merge conflicts conservatively and verifies the repo still builds. Use when the tree contains conflict markers or git reports unresolved merges.
| name | issue-format |
| description | Formats concise GitHub issue titles and descriptions. Use when turning a problem into a tracking issue. |
GitHub issue:
- Title:
Short issue title- Description: Present-tense summary of the bug, limitation, or follow-up.