Skip to main content
ZICQ

Skills ZICQ category:Security code-reviewer

Code Reviewer

Analyzes code diffs and files to identify bugs, security vulnerabilities (SQL injection, XSS, insecure deserialization), code smells, N+1 queries, naming issues, and architectural concerns, then produces a structured review report with prioritized, actionable feedback. Use when reviewing pull requests, conducting code quality audits, identifying refactoring opportunities, or checking for security issues. Invoke for PR reviews, code quality checks, refactoring suggestions, review code, code quality. Complements specialized skills (security-reviewer, test-master) by providing broad-scope review across correctness, performance, maintainability, and test coverage in a single pass.

6075 installs

Official URL:skills.sh

What this skill does

Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.

What it does

Analyzes code diffs and files to identify bugs, security vulnerabilities (SQL injection, XSS, insecure deserialization), code smells, N+1 queries, naming issues, and architectural concerns, then produces a structured review report with prioritized, actionable feedback

When to use it

This Skill

How agents load it

Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Code Reviewer; When to Use This Skill; Core Workflow; Reference Guide; Review Patterns (Quick Reference); N+1 Query — Bad vs Good. It includes spec-recommended sections: step-by-step instructions.

File analysis

File analysis: besides SKILL.md, the body references references/review-checklist.md, references/common-issues.md, references/feedback-examples.md, references/report-template.md, references/spec-compliance-review.md, references/receiving-feedback.md. Those resources load on demand.

Code ReviewerWhen to Use This SkillCore WorkflowReference GuideReview Patterns (Quick Reference)N+1 Query — Bad vs GoodBAD: query inside loopGOOD: prefetch in bulkMagic Number — Bad vs GoodBADGOODSecurity: SQL Injection — Bad vs Good

· License:MIT · allowed-tools:Read, Grep, Glob

Source category:skills.sh agent-skill

SKILL.md & Agent activation

Official spec ↗
name
code-reviewer
description
Analyzes code diffs and files to identify bugs, security vulnerabilities (SQL injection, XSS, insecure deserialization), code smells, N+1 queries, naming issues, and architectural concerns, then produces a structured review report with prioritized, actionable feedback. Use when reviewing pull requests, conducting code quality audits, identifying refactoring opportunities, or checking for security issues. Invoke for PR reviews, code quality checks, refactoring suggestions, review code, code quality. Complements specialized skills (security-reviewer, test-master) by providing broad-scope review across correctness, performance, maintainability, and test coverage in a single pass.
allowed-tools
Read, Grep, GlobExperimental field; support depends on the client and does not grant permissions by itself.
License
MIT
  1. DiscoverThe client exposes names and descriptions to the agent.
  2. ActivateYour request or the task context selects the skill and loads its instructions.
  3. Load resourcesReferenced scripts, documentation and assets are used when needed.
Files referenced by the instructions · 6
  • references/review-checklist.md
  • references/common-issues.md
  • references/feedback-examples.md
  • references/report-template.md
  • references/spec-compliance-review.md
  • references/receiving-feedback.md

These paths are extracted from the text. Check the upstream package to verify the files exist.

Invocation syntax and available tools depend on your Agent client. Client integration guide ↗

Install this skill

Skills CLI ↗

Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.

This skill references supporting files. Retrieve the complete directory from the source; copying SKILL.md alone may leave missing dependencies.

Ask your Agent to install

Copy these instructions to a compatible agent and confirm the target directory matches your client.

Install the agent skill "code-reviewer" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-6fb439a352cbc4eb-Code-Reviewer.html
Save it as .cursor/skills/code-reviewer/SKILL.md or .claude/skills/code-reviewer/SKILL.md and keep the frontmatter name and description exactly as-is.
This skill also ships scripts/, references/, or assets/ — fetch the whole folder from https://github.com/jeffallan/claude-skills instead of creating only a SKILL.md.

Full package on GitHub ↗

Install from the terminal · Skills CLI

Requires Node.js and npx. First inspect the repository's skill list to confirm the name.

npx skills add 'https://github.com/jeffallan/claude-skills' --list

npx skills add 'https://github.com/jeffallan/claude-skills' --skill 'code-reviewer'

The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.

Readable layout
--- name: code-reviewer description: Analyzes code diffs and files to identify bugs, security vulnerabilities (SQL injection, XSS, insecure deserialization), code smells, N+1 queries, naming issues, and architectural concerns, then produces a structured review report with prioritized, actionable feedback. Use when reviewing pull requests, conducting code quality audits, identifying refactoring opportunities, or checking for security issues. Invoke for PR reviews, code quality checks, refactoring suggestions, review code, code quality. Complements specialized skills (security-reviewer, test-master) by providing broad-scope review across correctness, performance, maintainability, and test coverage in a single pass. license: MIT allowed-tools: Read, Grep, Glob metadata: author: https://github.com/Jeffallan version: "1.1.0" domain: quality triggers: code review, PR review, pull request, review code, code quality role: specialist scope: review output-format: report related-skills: security-reviewer, test-master, architecture-designer --- # Code Reviewer Senior engineer conducting thorough, constructive code reviews that improve quality and share knowledge. ## When to Use This Skill - Reviewing pull requests - Conducting code quality audits - Identifying refactoring opportunities - Checking for security vulnerabilities - Validating architectural decisions ## Core Workflow 1. **Context** — Read PR description, understand the problem being solved. **Checkpoint:** Summarize the PR's intent in one sentence before proceeding. If you cannot, ask the author to clarify. 2. **Structure** — Review architecture and design decisions. Ask: Does this follow existing patterns in the codebase? Are new abstractions justified? 3. **Details** — Check code quality, security, and performance. Apply the checks in the Reference Guide below. Ask: Are there N+1 queries, hardcoded secrets, or injection risks? 4. **Tests** — Validate test coverage and quality. Ask: Are edge cases covered? Do tests assert behavior, not implementation? 5. **Feedback** — Produce a categorized report using the Output Template. If critical issues are found in step 3, note them immediately and do not wait until the end. > **Disagreement handling:** If the author has left comments explaining a non-obvious choice, acknowledge their reasoning before suggesting an alternative. Never block on style preferences when a linter or formatter is configured. ## Reference Guide Load detailed guidance based on context: | Topic | Reference | Load When | |-------|-----------|-----------| | Review Checklist | `references/review-checklist.md` | Starting a review, categories | | Common Issues | `references/common-issues.md` | N+1 queries, magic numbers, patterns | | Feedback Examples | `references/feedback-examples.md` | Writing good feedback | | Report Template | `references/report-template.md` | Writing final review report | | Spec Compliance | `references/spec-compliance-review.md` | Reviewing implementations, PR review, spec verification | | Receiving Feedback | `references/receiving-feedback.md` | Responding to review comments, handling feedback | ## Review Patterns (Quick Reference) ### N+1 Query — Bad vs Good ```python # BAD: query inside loop for user in users: orders = Order.objects.filter(user=user) # N+1 # GOOD: prefetch in bulk users = User.objects.prefetch_related('orders').all() ``` ### Magic Number — Bad vs Good ```python # BAD if status == 3: ... # GOOD ORDER_STATUS_SHIPPED = 3 if status == ORDER_STATUS_SHIPPED: ... ``` ### Security: SQL Injection — Bad vs Good ```python # BAD: string interpolation in query cursor.execute(f"SELECT * FROM users WHERE id = {user_id}") # GOOD: parameterized query cursor.execute("SELECT * FROM users WHERE id = %s", [user_id]) ``` ## Constraints ### MUST DO - Summarize PR intent before reviewing (see Workflow step 1) - Provide specific, actionable feedback - Include code examples in suggestions - Praise good patterns - Prioritize feedback (critical → minor) - Review tests as thoroughly as code - Check for security issues (OWASP Top 10 as baseline) ### MUST NOT DO - Be condescending or rude - Nitpick style when linters exist - Block on personal preferences - Demand perfection - Review without understanding the why - Skip praising good work ## Output Template Code review report must include: 1. **Summary** — One-sentence intent recap + overall assessment 2. **Critical issues** — Must fix before merge (bugs, security, data loss) 3. **Major issues** — Should fix (performance, design, maintainability) 4. **Minor issues** — Nice to have (naming, readability) 5. **Positive feedback** — Specific patterns done well 6. **Questions for author** — Clarifications needed 7. **Verdict** — Approve / Request Changes / Comment ## Knowledge Reference SOLID, DRY, KISS, YAGNI, design patterns, OWASP Top 10, language idioms, testing patterns [Documentation](https://jeffallan.github.io/claude-skills/skills/quality/code-reviewer/)

Related skills

Security

Skill Vetter

Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, p…

Security

Moltguard

MoltGuard — OpenClaw security guard by OpenGuardrails. Install MoltGuard to protect you and your human from prompt injection, data exfiltrat…

Security

Security Auditor

Use when reviewing code for security vulnerabilities, implementing authentication flows, auditing OWASP Top 10, configuring CORS/CSP headers…

Security

Skill Vetter

Security vetting protocol before installing any AI agent skill. Red flag detection for credential theft, obfuscated code, exfiltration. Risk…