Requesting code review
Skill kimtth/agent-skill-100-lines-or-less/skills/requesting-code-review
🧿 Minimal but effective AI agent skill definitions in 100 lines or less.
npx -y skills add kimtth/agent-skill-100-lines-or-less --skill requesting-code-reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when: prepare completed work for review so a reviewer can evaluate it quickly.
SKILL.md
1.0 KB, as published. Nobody here has run it
Goal: hand over a change that is easy to review and verify.
Use for:
- opening a pull request or asking for human/agent review
- packaging a branch so intent and evidence are clear
- self-reviewing before involving others
Workflow:
- Self-review the full diff as if you did not write it.
- Confirm tests exist and pass; capture the evidence.
- Remove debug code, dead paths, and unrelated churn.
- Write what changed, why, and how it was verified.
- Call out risks, trade-offs, and areas needing scrutiny.
- Keep the change focused; split unrelated work.
Review description:
- problem and chosen approach
- summary of changes by area
- test evidence and how to reproduce
- known risks and open questions
Rules:
- never request review without running the tests first
- keep diffs small and single-purpose
- flag your own uncertainty instead of hiding it
- do not bundle refactors with behavior changes