菜单
Use when you need fast, interactive code review of a PR with detailed explanations. Triggers on exploratory reviews, learning-focused feedback, or when you want to discuss findings before any action.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Restate the last message in plain human language, with no jargon.
Give a capable engineer a concise briefing on the critical facts and implications of an effort before it is built or after it is completed. Use when the human explicitly invokes $facts, and never otherwise; do not invoke this skill automatically.
Vendor skills from a GitHub repository into this repo. Use when asked to import, vendor, list, add, or update skills from another skills repository while preserving provenance and detecting local edits.
Use when given a well-scoped bug fix or small feature ticket from Jira. Investigates the ticket, researches the codebase, proposes a fix, then plans and implements on approval. Lighter alternative to the full deep-work pipeline for tickets that don't need multi-session design discussion.
Use when starting work on a ticket that needs refinement before entering the deep-work pipeline. Reads from Jira, pasted text, or a file, then interactively refines it into a structured ticket.md.
Use when a session is ending and you want to analyze process efficiency. Triggers on requests to review how a session went, evaluate context usage, or identify workflow improvements.
| name | quick-review |
| description | Use when you need fast, interactive code review of a PR with detailed explanations. Triggers on exploratory reviews, learning-focused feedback, or when you want to discuss findings before any action. |
Single-pass expert code review for fast, interactive feedback with detailed explanations of every issue found.
A direct, conversational code review that explains the reasoning behind every finding.
/quick-review <owner/repo> <pr-number>
Examples:
/quick-review anthropics/claude-code 123/quick-review myorg/myrepo 456Apply these in priority order:
| Priority | Focus | What to Look For |
|---|---|---|
| 0 | Correctness | Bugs, spec violations, logic errors, edge cases |
| 1 | Security | Injection, auth flaws, data exposure, insecure defaults |
| 2 | Performance | Algorithmic complexity, memory, queries, bottlenecks |
| 3 | Code Quality | Readability, naming, structure, organization |
| 4 | Best Practices | Language idioms, design patterns, standards |
| 5 | Error Handling | Exceptions, validation, failure recovery |
| 6 | Testing | Testability, missing test cases, test strategies |
gh pr view -R <owner/repo> <pr-number>
gh pr diff -R <owner/repo> <pr-number>
Once you have consumed the diff, performing the code review using the following guidance:
REVIEW PRIORITIES (in order):
When reviewing code, you will:
Analysis Framework in priority order: 0. Correctness - Evaluate code behavior for inconsistencies with requirements/specifications and comments; look for obvious bugs
Review Process:
Communication Style:
Output Structure:
Always consider the project's specific context, coding standards, and constraints. If you need additional context about the codebase, requirements, or constraints, ask specific questions to provide more targeted feedback.