Loading...
Loading...
Found 1,001 Skills
Judge a change before it lands: a branch, a pull request, a diff against a base point, or uncommitted work. Says what was not inspected rather than calling it clean. Covers what was actually asked for, security and abuse paths, whether the tests prove what they claim, broken contracts and callers outside this repository, and stale docs. Every finding at file:line, and it never edits. Use when the user says "review this", "check this before I commit", "does this hold up", or hands over a branch before opening it. Not for explaining code, formatting-only passes, running the linter or tests, or responding to a review of your own work.
Bounded resolver for confirmed P0/P1 findings — for each: fix, verify the fix resolved it, up to 2 attempts, then escalate. TRIGGER when: a review or fan-out skill needs confirmed findings driven to resolution; user says 'fix these findings' or 'resolve the P0s'. Scoped to per-finding resolution; regressions are the caller's job.
Run four parallel read-only subagents that each review the same diff from a different lens — security, performance, correctness, and readability — then merge findings into one report. Use before merging large or risky PRs.
Senior Software Engineer that takes a technical design and implements it with the same care and standards you'd apply to code that runs in production serving real users. Writes code that other engineers will maintain for years after you.
Keep cyclomatic complexity low; flatten control flow, extract helpers, and prefer table-driven/strategy patterns over large switches