Menu
Review current uncommitted git changes with full file context and produce a structured report with severity levels, actionable fixes, and an approval verdict.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Execute an approved implementation plan exactly and safely. Use for ExecPlan-style plan execution, resumable phase checklists, multi-hour implementation work, migrations, significant refactors, and plans that require verification checkpoints, status tracking, and final reporting.
Collaborative discovery and design framing for ambiguous or high-risk work. Use when requirements are unclear, multiple approaches are possible, or you need to turn an idea into a validated design brief before planning or coding.
Create detailed, execution-ready implementation plans for complex or high-risk changes without coding. Use for ExecPlan-style work, multi-hour changes, significant refactors, migrations, resumable phase checklists, and work that should be handed off to execute-plan with clear validation.
Create source-adjacent HTML visualizations for /visualize requests, docs, markdown, standardized plans, process flows, charts, Mermaid diagrams, context maps, and recommendation diagrams.
Structured clarification and requirements gathering through focused dialogue or with dry code. Use when a task is ambiguous, underspecified, or requires user input before any action can be taken. Do not plan or implement anything—only ask questions to collect the information needed.
Create or refresh project documentation in `docs/`. Use when a project needs docs initialized or existing docs synced to the current codebase.
| name | review |
| description | Review current uncommitted git changes with full file context and produce a structured report with severity levels, actionable fixes, and an approval verdict. |
| license | MIT |
Use this skill to review uncommitted changes in the current git workspace.
Focus on correctness, safety, maintainability, and alignment with project standards.
The review must produce:
Approve or Request Changes)git diffgit diff --cached (if staged changes exist)docs/SUMMARY.md exists, read it first.Code Standard docs for implementation conventions.Evaluate each change across these dimensions:
Assign one severity per finding using this rubric:
S0 - Critical
S1 - High
S2 - Medium
S3 - Low
Use the report format below in this exact section order.
For each finding, use this template:
R-001 (incrementing)S0 | S1 | S2 | S3Correctness | Security | Reliability | Style | Performance | Testing | Maintainabilitypath/to/file.ext#Lx-Ly (or function/class name)High | Medium | LowIf no findings exist, explicitly write: No actionable findings.
List good practices observed, such as:
Include only S0 and S1 findings:
R-00X short fix descriptionR-00Y short fix descriptionIf none, state: No must-fix items.
Use one of:
S0/S1) remain.S0/S1) found.Optionally include:
Before finalizing, confirm: