Categories
Indexed Skills (5)
nibble-scan
Audit code for real defects, not style. Runs a deterministic structural pre-pass, then reviews for security, reliability, performance, and dead-logic bugs across any language, each with a concrete failure trigger. Report only, no fixes yet. Use when reviewing unfamiliar code or hunting the cause of a class of failures.
nibble-commit
Commit one atomic fix with a structured message that documents root cause, impact, fix strategy, and backwards compatibility. Use to close out a single fix cleanly, so the history explains itself later and reviewers can approve one small bite at a time.
nibble-fix
Apply the smallest change that fixes the root cause, preserving public contracts and every untouched line, then verify with the project's own commands. Use after the root cause and fix strategy are known, when it is time to actually change code in a repo you want to keep stable.
nibble-map
Get your bearings in an unfamiliar repo fast, before changing anything. Finds the stack, the exact build and test commands, and the entry points in one pass. Use as the first bite whenever you land in a codebase you do not already know.
nibble-trace
Pin the root cause of a single issue or file and draft a minimal fix strategy, without editing anything. Low token, focused. Use once a specific bug or failing case has been chosen and you need the true cause before changing code.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.