code-review-general
Provides a framework for performing high-quality code reviews with a priority-based focus.
Install
mkdir -p .claude/skills/code-review-general && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11711" && unzip -o skill.zip -d .claude/skills/code-review-general && rm skill.zipInstalls to .claude/skills/code-review-general
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
General code review process: priority ordering, what to block on, how to give actionable feedbackKey capabilities
- →Prioritize code review feedback by correctness, security, performance, readability, and style.
- →Identify red flags like hardcoded secrets or missing input validation that require blocking.
- →Suggest structural improvements such as extracting duplicated logic or simplifying implementations.
- →Formulate non-blocking suggestions for better variable names or additional test cases.
- →Distinguish between "must fix", "should fix", and "consider" feedback.
- →Approve reviews with minor comments, blocking only for critical issues.
How it works
This skill provides a structured approach to code review by defining a priority order for issues and categorizing feedback into blocking, structural, and suggestive types. It guides reviewers on how to phrase comments and when to block a code change.
Inputs & outputs
When to use code-review-general
- →Perform code review
- →Define review criteria
- →Give constructive feedback
- →Identify code red flags
About this skill
Code Review — General
Review Priority Order
- Correctness — does it do what it should? Are edge cases handled?
- Security — does it introduce vulnerabilities? (See security skill for checklist.)
- Performance — N+1 queries, unnecessary allocations in hot paths, missing indexes.
- Readability — will the next engineer understand this without context?
- Style — does it match project conventions? (Never block on style alone.)
Red Flags (always block)
- Hardcoded secrets, API keys, or credentials.
- Missing input validation at API/service boundaries.
- Unhandled error paths that leave state corrupted.
- Race conditions in concurrent code.
- Silent exception swallowing (
catch (e) {}).
Structural Issues (should fix)
- Functions doing more than one thing.
- Deep nesting — suggest early returns / guard clauses.
- Duplicated logic that should be extracted.
- Magic numbers or strings without named constants.
Suggestions (non-blocking)
- Better variable/function names.
- Simpler implementations.
- Additional test cases for uncovered paths.
Tone
- Quote the specific line. Explain the problem. Offer a concrete alternative.
- Distinguish: "must fix", "should fix", "consider".
- Approve with comments for minor issues — block only for correctness, security, or missing tests.
- Separate your opinion from objective issues.
When not to use it
- →When the review only concerns style issues, as these should not block approval.
- →When a specific security checklist is needed, as this skill refers to a separate security skill for that.
Limitations
- →This skill does not provide a specific checklist for security vulnerabilities, deferring to a separate security skill.
- →It does not cover specific project conventions for style, only noting that style should match them.
How it compares
This workflow provides a structured, prioritized method for code review, unlike an ad-hoc or unguided review process.
Compared to similar skills
code-review-general side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| code-review-general (this skill) | 0 | 4mo | No flags | Beginner |
| effective-go | 323 | 9mo | No flags | Beginner |
| architect-review | 109 | 4mo | No flags | Advanced |
| resolve-conflicts | 81 | 8mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
effective-go
openshift
Apply Go best practices, idioms, and conventions from golang.org/doc/effective_go. Use when writing, reviewing, or refactoring Go code to ensure idiomatic, clean, and efficient implementations.
architect-review
sickn33
Master software architect specializing in modern architecture patterns, clean architecture, microservices, event-driven systems, and DDD. Reviews system designs and code changes for architectural integrity, scalability, and maintainability. Use PROACTIVELY for architectural decisions.
resolve-conflicts
antinomyhq
Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling deleted-but-modified files with backup and analysis.
solid-principles
SmidigStorm
Enforce SOLID principles (Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion) in object-oriented design. Use when writing or reviewing classes and modules.
python-testing-patterns
wshobson
Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.
codex
Lucklyric
Invoke Codex CLI for complex coding tasks requiring high reasoning capabilities. This skill should be invoked when users explicitly mention "Codex", request complex implementation challenges, advanced reasoning, or need high-reasoning model assistance. Automatically triggers on codex-related requests and supports session continuation for iterative development.