skills.rest
whinchman
whinchmanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

code-reviewer

Reviews completed code for bugs, security issues, and correctness, filing findings into a bug tracker.

Updated May 2, 2026
Search Tags:#code quality#code review#agent workflow#security audit#bug detection#git diff
One-click install
npx skills add https://github.com/whinchman/midi-man-mk3 --skill code-reviewer-whinchman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/whinchman/midi-man-mk3/tree/main/.claude/skills/code-reviewer
Command: npx skills add https://github.com/whinchman/midi-man-mk3 --skill code-reviewer-whinchman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It automates systematic code review of completed work, catching bugs, security vulnerabilities, and correctness issues before code is merged, without modifying the application code itself. ## Core Features & Use Cases - Systematic Review Checklist: Examines every changed file for correctness, bugs, security flaws, integration issues, code standards, and testing violations. - Structured Findings: Documents each issue with file, line, severity (critical/warning/info), description, and a suggested fix. - Bug Filing & Workflow Integration: Files critical and warning findings into .workflow/BUGS.md, updates task statuses, and delivers an approve/request-changes verdict. - Use Case: After a Coder agent finishes a feature branch, run this Skill to diff the branch against the default branch, audit every change, and produce a review report with actionable fixes before opening a pull request. ## Quick Start Ask the agent to review the current feature branch against the default branch and file any bugs it finds.

Frequently Asked Questions about code-reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a feature branch before merging?▼

Identify the base branch and run git diff <default_branch>...<feature-branch> to get the full change set. Review every changed file for correctness, security, and integration issues, then document findings with severity and suggested fixes.

What does an automated code review check for?▼

It checks correctness and edge cases, bugs like race conditions and resource leaks, security issues such as injection and exposed secrets, integration with existing code, adherence to project code standards, and whether tests are properly isolated unit tests.

Can the code reviewer modify the code it reviews?▼

No. The reviewer never modifies application code and never pushes or merges to the default branch. It only produces review findings and files bugs as follow-up tasks for other agents to fix.

What test practices are flagged during code review?▼

Integration and end-to-end tests are not permitted; only unit tests are allowed. Any test making real HTTP calls, database connections, or external service requests is flagged as critical, and mocks must assert correct arguments.

When should I not rely on this review workflow?▼

It depends on task files in .workflow/tasks/ or recently completed agent tasks to find work, so it fits repositories using that workflow structure. Standalone ad-hoc reviews are possible but require manually specifying the diff scope.

Related Skills

Explore More Software Engineering Skills→
raydocsraydocs

flow-impl-review

Review code diffs for quality, security, and architecture.

Community
Advanced
marcuskroghmarcuskrogh

iterate

Create tasks, branches, and pull requests for post-ship fixes linked to prior work.

Community
Advanced
phraphra

code-review

Review modified code files and auto-fix mechanical issues.

Community
Advanced
in-the-loop-labsin-the-loop-labs
48

ai-critic

Fetches and applies AI-generated code review suggestions from pair-review.

Official
Intermediate