Skills to orchestrate coding agents to do long horizon tasks with little to no steering
Agent
Review code for adherence to project guidelines, style guides, and best practices. Use after writing or modifying code, especially before committing changes or creating pull requests. Checks for style violations, potential issues, and adherence to the patterns in the repo's guideline files. The reviewer needs to know…
Agent
Analyze code comments for accuracy, completeness, and long-term maintainability. Use after generating large documentation comments or docstrings, before finalizing changes that add or modify comments, when reviewing existing comments for technical debt or comment rot, and when verifying that comments accurately…
Agent
Review a change against the history of the code it touches. Use git blame and log to catch changes that contradict why the surrounding code exists — reintroducing a fixed bug, removing a guard that was added on purpose, or undoing a deliberate decision. Reports only high-confidence findings backed by a specific past…
Agent
Review a set of changes for test coverage quality and completeness. Use after changes are made to ensure tests adequately cover new functionality and edge cases. Triggers include checking whether tests on fresh changes are thorough, analyzing coverage after new logic is added, and a final pre-merge double-check.
Agent
Review a change against prior pull requests. Use the PR/commit history to catch an approach that was already tried, discussed, or reverted — so the change does not re-litigate a settled decision or redo work that was rejected. Reports only high-confidence findings backed by a specific prior PR or revert.
Agent
Security review of a change. Use when the diff touches a trust boundary, parses input, handles auth/authz, moves user or secret data, shells out, or feeds untrusted text to an LLM. Runs a fast STRIDE pass and reports only high-confidence, exploitable findings with a concrete fix.
Agent
Review code changes to identify silent failures, inadequate error handling, and inappropriate fallback behavior. Use proactively after completing work that involves error handling, catch blocks, fallback logic, or any code that could suppress errors.
Agent
Expert analysis of type design. Use when introducing a new type to ensure it follows best practices for encapsulation and invariant expression, when reviewing all types being added in a change, and when refactoring existing types to improve their design quality. Provides both qualitative feedback and quantitative…