Loading...
Loading...
Found 4 Skills
Review a pull request or a branch against the repository's standards — skill frontmatter and body, docs and bilingual pairs, Agent Notes, and scripts — and report blockers separately from suggestions, prioritizing correctness and required behavior over style.
Use when working in a repository to find non-obvious simplification candidates — dead, duplicated, speculative, over-built, added-then-removed, or hand-rolled-where-a-dependency-exists surface across code, docs, and skills — and turn the worthwhile ones into proposed Agent Notes or inline TODO/FIXME/XXX markers; also when asked to audit or coalesce superseded Agent Notes, or fold worthwhile simplification ideas from another PR or branch.
Record bug-fix decisions as Agent Notes bound to regression tests so AI-driven code changes cannot silently regress. Use when fixing a bug, reviewing a fix, verifying a notes tree, or asking when to write a postmortem. Do not use for general feature docs or changelogs.
Use when auditing or fixing prose that reads like a leaked reasoning transcript — dead design-session citations such as (decision N), audit item codes, or §N of uncommitted drafts; change narration such as "used to", "no longer", "this cut"; stack or review vantage ("a later PR in this stack", "rejected in review"); reviewer-addressed justifications; control-flow narration; or hedged planning residue in comments, JSDoc, docs, or Agent Notes.