This skill should be used when the user requests a code review, security audit, or pre-merge inspection of a change. Trigger phrases include "review 代码", "代码审查", "安全审计", "审查这个 PR", "review this PR", "security audit", "code review". It applies a five-axis review framework (correctness, readability, architecture, security, performance) with severity classification and a standardized output template.
Scanned 9/6/2026
Install to Claude Code
npx -y skills add whaojie797-design/Novera-AI-skills --skill code-review-security --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Code Review Security?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/whaojie797-design-code-review-security)More formats (shields.io, HTML) on the badges page.
---
name: code-review-security
description: This skill should be used when the user requests a code review, security audit, or pre-merge inspection of a change. Trigger phrases include "review 代码", "代码审查", "安全审计", "审查这个 PR", "review this PR", "security audit", "code review". It applies a five-axis review framework (correctness, readability, architecture, security, performance) with severity classification and a standardized output template.
---
# Code Review & Security
## Overview
Perform thorough, opinionated pre-merge reviews and security audits. Apply a
five-axis framework, classify findings by severity, and produce a consistent
report so issues are actionable.
## When to Use
- "review 代码", "代码审查", "审查这个 PR", "review this PR", "安全审计", "security audit", "code review".
- Before merging a feature, bugfix, or refactor.
- When the user wants a focused security pass.
## Five-Axis Framework
1. **Correctness** — Does it do what the spec says? Edge cases, off-by-one, null/empty, concurrency.
2. **Readability** — Can another engineer understand it without explanation? Naming, structure, comments.
3. **Architecture** — Follows existing patterns? Right abstraction level? No leaky boundaries.
4. **Security** — Input validation, authz checks, secrets, injection, XSS, rate limiting, IDOR.
5. **Performance** — N+1 queries, unbounded loops, missing pagination, needless allocations.
## Severity Classification
- **Critical** — data loss, security vulnerability, broken functionality. Must fix before merge.
- **Important** — missing test, wrong abstraction, poor error handling. Should fix before merge.
- **Suggestion** — naming, style, optional optimization. Consider.
## Procedure
1. Read the diff / changed files fully; do not skim.
2. Run each axis against the change; note `file:line — description + recommended fix`.
3. Always note at least one thing done well.
4. Emit the report using `references/review-template.md`.
5. Include a verification story (tests run? build verified? security checked?).
## Bundled Resources
- `references/review-template.md` — copy-paste report skeleton.
- `references/security-checklist.md` — common vulnerability checks (OWASP-aligned).
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!