Agent skill · Security

structured-code-review

Performs a structured five-stage code review covering requirements compliance, correctness, code quality, testing, and security/performance. Each stage uses targeted checklists and categorized feedback (Blocker/Major/Minor/Nit) with actionable suggestions and rationale. Use when the user asks for code review, PR feedback, pull request review, or wants their code checked for bugs, style issues, or vulnerabilities — triggered by phrases like "review my code", "check this PR", "review my changes", "pull request review", or "code feedback".

Rohit Ghumare73,165★ · +3,601/wk · 3 repos on radarProfile →
codexcursorApache-2.0
Install
npx skills add rohitg00/skillkit --skill structured-review --agent codex

Same command for any agent — swap --agent for claude-code, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Version: 1.0.0
Path: packages/core/src/methodology/packs/collaboration/structured-review/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,422
Language: TypeScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Structured Code Review You are performing a structured, multi-stage code review. This methodology ensures thorough review while providing actionable, constructive feedback. ## Core Principle **Review in stages. Each stage has a specific focus. Don't mix concerns.** A structured review catches more issues and provides better feedback than an unstructured scan. ## Review Stages ### Stage 1: Requirements Compliance First, verify the code meets its requirements. **Checklist:** - [ ] Implements stated requirements - [ ] Handles specified edge cases - [ ] No scope creep (unexpected additions) - [ ] No missing functionality **Feedback at this stage:** - "This doesn't appear to handle the case when X is empty" - "The requirement specified Y, but this implements Z" - "This adds feature F which wasn't requested - is that intentional?" ### Stage 2: Correctness Next, verify the code works correctly. **Checklist:** - [ ] Logic is sound - [ ] No obvious bugs - [ ] Error paths are handled - [ ] No unfinished code (TODOs without tickets) **Feedback at this stage:** - "This will throw if `user` is null" - "The loop exits early before processing all items" - "What happens when the API call fails?"

What's inside
Steps it walks through
  1. Core Principle
  2. Review Stages
  3. Stage 1: Requirements Compliance
  4. Stage 2: Correctness
  5. Stage 3: Code Quality
  6. Stage 4: Testing
  7. Stage 5: Security & Performance
  8. Writing Good Feedback
  9. Feedback Levels
  10. Constructive Feedback Template
  11. Review Checklist Summary
  12. Integration with Other Skills
More from skillkit
All skills →
About this skill
What does the structured-code-review skill do?

Performs a structured five-stage code review covering requirements compliance, correctness, code quality, testing, and security/performance. Each stage uses targeted checklists and categorized feedback (Blocker/Major/Minor/Nit) with actionable suggestions and rationale. Use when the user asks for code review, PR feedback, pull request review, or wants their code checked for bugs, style issues, or vulnerabilities — triggered by phrases like "review my code", "check this PR", "review my changes", "pull request review", or "code feedback".

How do I install it?

Run `npx skills add rohitg00/skillkit --skill structured-review --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From rohitg00/skillkit, a repository with 1,422 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going