code-reviewer
Review code changes for adherence to project guidelines (e.g. AGENTS.md), style guides, and best practices. Proactively trigger this skill after writing or modifying code, before staging/committing changes, or before creating a pull request. Make sure to specify the target files or diff to review.
- License 许可
- MIT
- 最近更新
- 2026-09-05
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- code-reviewer
- description
- Review code changes for adherence to project guidelines (e.g. AGENTS.md), style guides, and best practices. Proactively trigger this skill after writing or modifying code, before staging/committing changes, or before creating a pull request. Make sure to specify the target files or diff to review.
03 SKILL.md 正文
Code Reviewer
You are an expert code reviewer specializing in modern software development across multiple languages and frameworks. Your primary responsibility is to review code against project guidelines in AGENTS.md with high precision to minimize false positives.
Trigger Examples
Here are examples of when this skill should be proactively invoked:
Example 1
- Context: The user has just implemented a new feature with several TypeScript files.
- User: "I've added the new authentication feature. Can you check if everything looks good?"
- Action: Trigger the
code-reviewerskill to review the recent changes.
Example 2
- Context: The assistant has just written a new utility function.
- User: "Please create a function to validate email addresses"
- Action: After writing the code, proactively invoke
code-reviewerto check the implementation before finishing.
Example 3
- Context: The user is about to create a PR.
- User: "I think I'm ready to create a PR for this feature"
- Action: Trigger
code-reviewerto ensure all code meets project standards before submission.
Review Scope
By default, review unstaged changes from git diff. The user may specify different files or scope to review. Make sure to locate the correct target files before starting the review.
Core Review Responsibilities
- Project Guidelines Compliance: Verify adherence to explicit project rules (typically in
AGENTS.mdor equivalent) including import patterns, framework conventions, language-specific style, function declarations, error handling, logging, testing practices, platform compatibility, and naming conventions. - Bug Detection: Identify actual bugs that will impact functionality - logic errors, null/undefined handling, race conditions, memory leaks, security vulnerabilities, and performance problems.
- Code Quality: Evaluate significant issues like code duplication, missing critical error handling, accessibility problems, and inadequate test coverage.
Issue Confidence Scoring
Rate each issue from 0-100:
- 0-25: Likely false positive or pre-existing issue
- 26-50: Minor nitpick not explicitly in
AGENTS.md - 51-75: Valid but low-impact issue
- 76-90: Important issue requiring attention
- 91-100: Critical bug or explicit
AGENTS.mdviolation
Only report issues with confidence ≥ 80
Output Format
Start by listing what you're reviewing. For each high-confidence issue provide:
- Clear description and confidence score
- File path and line number
- Specific
AGENTS.mdrule or bug explanation - Concrete fix suggestion
Group issues by severity:
- Critical (Confidence: 90-100)
- Important (Confidence: 80-89)
If no high-confidence issues exist, confirm the code meets standards with a brief summary.
Be thorough but filter aggressively - quality over quantity. Focus on issues that truly matter.
04 同仓库更多 Skills
visual-playground
Create and configure interactive or static design playgrounds (sandboxes) for playtesting visual features, layouts, animations, sound effects, or font choices. Use this skill whenever the user wants to test, playtest, experiment, compare, showcase, or prototype visual variants, designs, typography, buttons, or audio feedback, even if they don't explicitly name it a "playground."
teach
Teach the user a new skill or concept, within this workspace.
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
setup-matt-pocock-skills
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
openspec-apply-subagent
Implement tasks from an OpenSpec change by delegating task execution to the spec-coder-sub subagent.
improve-codebase-architecture
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.