Code Reviewer
- 5 installs
- 8 repo stars
- Updated February 18, 2026
- avdlee/swift-agent-skills-cursor
code-reviewer is a Claude skill that reviews a change set for correctness, maintainability, and security risks before a pull request.
About
This skill instructs an agent to review code for correctness, maintainability, and security risks. It sequences the review to flag behavioral regressions first, then security concerns like XSS, SQL injection, command injection, and secrets, followed by readability and missing tests. Developers use it before opening a pull request or after large refactors.
- Five-step review order starting with behavioral regressions
- Security checklist covers XSS, SQL injection, command injection, and secrets
- Recommends concrete fixes with minimal churn and flags missing tests
Code Reviewer by the numbers
- 5 all-time installs (skills.sh)
- Ranked #881 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
- Data as of Jul 28, 2026 (Skillselion catalog sync)
code-reviewer capabilities & compatibility
- Capabilities
- code review · security audit · regression detection
- Use cases
- code review · security audit · testing
- IDEs
- cursor ide
What code-reviewer says it does
Review code for correctness, maintainability, and security risks. Use when preparing a PR or auditing a change set.
Flag security concerns (XSS, SQL injection, command injection, secrets).
npx skills add https://github.com/avdlee/swift-agent-skills-cursor --skill code-reviewerAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 5 |
|---|---|
| repo stars | ★ 8 |
| Last updated | February 18, 2026 |
| Repository | avdlee/swift-agent-skills-cursor ↗ |
What it does
Review a change set for regressions, security risks, readability, and missing tests before a PR.
Who is it for?
Reviewing a PR or large refactor for regressions and security issues
Skip if: Style-only nitpicks or generating new features
When should I use this skill?
Preparing a pull request, after a large refactor, or validating risky changes
What you get
A prioritized review flagging regressions, security concerns, and missing tests with concrete fixes.
- review findings
- concrete fix recommendations
- list of missing tests
By the numbers
- 5-step review procedure
Files
Code reviewer
When to use
- Before opening a pull request
- After large refactors
- When validating risky changes
Instructions
1. Identify potential behavioral regressions first. 2. Flag security concerns (XSS, SQL injection, command injection, secrets). 3. Evaluate readability, structure, and naming consistency. 4. Recommend concrete fixes with minimal churn. 5. Call out missing tests or validation steps.
Related skills
Improve Codebase ArchitectureSafely deepen clusters of shallow modules into cohesive, testable units while respecting their external dependencies.566k196k
Caveman ReviewGet ultra-compressed, one-line code review comments that cut noise while keeping every actionable fix.270k94.7kCodebase DesignShared vocabulary for designing deep modules: improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable.266k196kCavecrewDelegate coding tasks to specialized subagents that return compressed output, keeping the main context window usable for much longer sessions.220k94.7kCode ReviewReviews a branch or PR diff on two axes at once: conformance to coding standards plus a code-smell baseline, and whether it actually implements the original spec.201k196k
Requesting Code ReviewDispatch a consistent, high-signal code reviewer subagent that catches plan deviations and quality issues before merging or continuing development.183k264kFAQ
When should I use this skill?
Before opening a pull request, after large refactors, and when validating risky changes.
What security issues does it look for?
XSS, SQL injection, command injection, and leaked secrets.