菜单
This skill should be used when the user asks to "review this code", "check for bugs", "code review", "find issues", "review my changes", "look for problems", or when evaluating code quality, finding bugs, or identifying improvements.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
This skill should be used when the user asks to "housekeep", "sweep stray transition dirs", "clean up agent-infra debris", "find misplaced .workspace or .claude dirs", or when auditing project trees for the class of debris caused by hooks writing to the wrong project root (nested repos, worker-pool worktrees, stub-only session files, doubled path prefixes). Do NOT use for general project cleanup (see `/system:cleanup`) or for memory garbage collection (see `/memory-gc`).
Write clear, impactful website content for scanners. Use when writing landing pages, service descriptions, CTAs, or above-the-fold content. Covers the 50% test, sentence surgery, power words, page-type guidelines, mobile-first brevity, and techniques for reducing wordiness while maintaining impact.
Match content to what users actually want when they search. Use when creating website pages, blog posts, or any content for search engines. Covers 4 intent types (informational, navigational, transactional, commercial investigation), SERP analysis, query modifiers, and buyer journey mapping.
Technical SEO writing techniques for web content. Use when writing website pages, landing pages, service descriptions, or blog posts for organic search traffic. Covers keyword placement, meta descriptions, heading hierarchy, E-E-A-T principles, internal linking, long-tail keywords, schema markup, and measuring SEO success.
Complete D2 language reference for creating diagrams. Covers shapes, connections, containers, special types (SQL tables, sequences), icons, styling, and advanced features. Use for all D2 diagram generation tasks.
Clarity and simplicity principles for effective diagrams. Focus on essential elements, minimize visual noise, maintain consistency, and use single abstraction levels. Ensures diagrams communicate clearly without clutter.
| name | review |
| description | This skill should be used when the user asks to "review this code", "check for bugs", "code review", "find issues", "review my changes", "look for problems", or when evaluating code quality, finding bugs, or identifying improvements. |
| allowed-tools | ["Read","Write","Task","Bash","Grep","Glob","mcp__sequential-thinking__sequentialthinking","mcp__serena__find_symbol","mcp__serena__search_for_pattern","mcp__serena__get_symbols_overview","mcp__serena__find_referencing_symbols"] |
Practical code review focused on bugs, design issues, and maintainability.
--systematic: Structured reasoning for complex code--semantic: Use Serena (70-90% token reduction)--spec requirements.md: Validate against requirements/audit# Code Review Results
## Summary
Brief overview of findings.
## Critical Issues (Fix Immediately)
- **Issue**: [description]
- **Location**: file:line
- **Impact**: [why it matters]
- **Fix**: [specific steps]
## Important Issues (Fix Soon)
[same format]
## Minor Issues (Fix When Convenient)
[same format]
## Positive Observations
- Well-implemented patterns
- Good practices found
## Action Plan
1. Immediate: [critical fixes]
2. This Sprint: [important improvements]
3. Backlog: [minor cleanups]
## Estimated Effort
- Critical: X hours
- Important: Y hours
- Minor: Z hours
After review: /fix review to apply recommended fixes