菜单
Fix all issues from a cross-validation review summary. Use when the user says fix issues, fix these, fix the review findings, address the issues, or after /implement produces a cross-validation summary.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Run a cross-model code review using both opus and sonnet in parallel, then merge and deduplicate findings into a combined summary. Use when the user says cross review, dual review, cross-model review, review with both models, or wants a thorough second-opinion review of changes.
Quick codebase exploration to understand how something works. Use when the user says how does X work, explain the flow, where is X handled, show me how, walk me through, or needs to understand code before making changes.
Implement a validated feature plan task-by-task using Backend Architect and Frontend Developer agents, with progress tracking and user confirmation between tasks. After all tasks complete, automatically runs cross-model review (opus + sonnet). Use when the user says implement, build this, implement the plan, start implementation, or after /plan-feature produces a validated plan.
Deep investigation and root cause analysis using the DeepDive agent workflow. Use when the user says investigate, why does this break, what is causing, debug this, find the root cause, or any request to analyze a bug or issue without immediately writing a fix.
Run the three-phase Feature Planner validation before implementing a feature. Use when the user says plan feature, plan a new feature, I want to add, or any request for structured feature planning with edge case and risk analysis.
Code review using Clean Code Architect principles. Reviews staged changes, recent commits, or specific files for quality, security, and maintainability. Use when the user says review, review my code, check this, code review, or before committing significant changes.
基于 SOC 职业分类
| name | fix-issues |
| description | Fix all issues from a cross-validation review summary. Use when the user says fix issues, fix these, fix the review findings, address the issues, or after /implement produces a cross-validation summary. |
git branch --show-currentgit status --shortgit diff --cached --statFix all issues identified in the most recent cross-validation summary or code review.
Specific issues to fix: $ARGUMENTS
If no arguments provided, find the most recent cross-validation summary or /review output in this conversation and address all Must Fix and Should Fix items.
Step 1: Parse the issues
Extract all issues from the review summary. Categorize by file and type:
Step 2: Fix in order
For each issue:
Agent Assignment:
Fix Rules:
Step 3: Verify
After all fixes are applied:
Step 4: Report
## Fix Summary
### Issues Fixed
- [X/Y] Must Fix items resolved
- [X/Y] Should Fix items resolved
- [X/Y] Consider items addressed (if any)
### Changes Made
- `file:line` — [what was fixed]
### Issues Not Fixed (if any)
- [Issue] — [reason: needs human decision / out of scope / blocked by X]
### Verification
- Tests: [passed/failed/no tests]
- Regression check: [clean/issues found]