Process code review findings interactively - fix or skip issues from monty-code-review output. Presents issues in severity order, applies fixes, runs quality checks, and updates review documents with status markers.
Standardmรครig ist der Prompt ausgewรคhlt, der zuerst die Quelle prรผft. Sie kรถnnen zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prรผfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich fรผr eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fรผgen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prรผfen und installieren.
Ein direkter Befehl รผberspringt den Prรผf-Prompt. Prรผfen Sie die Quelle, bevor Sie ihn ausfรผhren.
Process code review findings interactively - fix or skip issues from monty-code-review output. Presents issues in severity order, applies fixes, runs quality checks, and updates review documents with status markers.
allowed-tools
["Bash","Read","Edit","Glob","Grep","TodoWrite"]
Process Code Review Skill
When to Use This Skill
After running /monty-code-review:code-review to generate a review document.
When you have a *_review.md file with severity-tagged issues to process.
When you want systematic, tracked resolution of code review findings.
When reviewing a colleague's code review document and fixing issues one-by-one.
This skill is the second step in the code review workflow:
For each issue, starting with highest severity, display:
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
[SEVERITY] Issue Title (N of M)
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
Location: file.py:L120-L145
Current Code:
<code snippet from review>
Problem:
<description of issue>
Proposed Fix:
<suggested code or approach>
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
Then ask: Fix this issue or skip it?
Wait for user response before proceeding.
4. Handle User Response
If User Says "Fix" / "Yes" / "Proceed"
Read the source file to understand current state
Apply the proposed fix using Edit tool
Run quality checks on the modified file:
.bin/ruff check <file> --fix
.bin/ruff format <file>
Update the review document to mark the issue as FIXED:
ty check <file> - Type check (baseline acceptable)
python manage.py check - Django system checks (if applicable)
If quality checks reveal additional issues, fix them before moving on.
6. Summary After Processing
When all issues are processed, provide a summary:
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
Review Processing Complete
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
Total Issues: 13
โ Fixed: 8
โญ๏ธ Skipped: 3
๐ Deferred: 2
Files Modified:
- optimo_core/services/wellbeing_service.py
- optimo_core/schemas/wellbeing.py
Next Steps:
Run /backend-atomic-commit:pre-commit to run pre-commit checks and fix issues.
Review document remains uncommitted (working documentation).
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
Status Markers
Use these markers when updating review documents:
Status
Marker
Meaning
Open
(no marker)
Issue not yet addressed
Fixed
โ FIXED
Issue has been resolved in code
Ignored
โญ๏ธ IGNORED
Issue intentionally skipped
Won't Fix
๐ซ WON'T FIX
Issue acknowledged but will not be fixed
Deferred
๐ DEFERRED
Issue to be addressed in future work
Always include the date: **Status:** โ FIXED (2025-01-15)
Severity Priority Order
Process issues in this order:
[BLOCKING] - Must fix before merge
Correctness issues
Security flaws
Data integrity problems
Multi-tenant boundary violations
[SHOULD_FIX] - Important but not blocking
Performance issues
Missing tests
Confusing control flow
[NIT] - Minor style/structure issues
Docstring improvements
Variable naming
Code organization
Quality Gates
Before marking a review as complete, verify:
All [BLOCKING] issues are either Fixed or explicitly Ignored with documented reason
All [SHOULD_FIX] issues are addressed or have a documented deferral reason
Linting passes: .bin/ruff check --fix
Formatting is correct: .bin/ruff format
Type checks pass baseline: .bin/ty check
Relevant tests still pass
Handling Arguments
Parse arguments to adjust behavior:
Available Flags
Flag
Description
--dry-run
Show all issues and proposed fixes without modifying any files
--auto
Apply all fixes without prompting (use with caution)
--severity=<LEVEL>
Filter to only process issues of specified severity
(no flags)
Interactive mode - prompt for each issue (default)
Severity Filter Values
--severity=BLOCKING - Only process BLOCKING issues
--severity=SHOULD_FIX - Only process SHOULD_FIX issues
--severity=NIT - Only process NIT issues
Examples
# Preview all issues without making changes
/process-code-review:process-review --dry-run api_review.md
# Auto-fix everything (careful!)
/process-code-review:process-review --auto api_review.md
# Auto-fix only minor issues, prompt for important ones
/process-code-review:process-review --auto --severity=NIT api_review.md
# Focus on critical issues only
/process-code-review:process-review --severity=BLOCKING api_review.md
# Dry-run to see only BLOCKING issues
/process-code-review:process-review --dry-run --severity=BLOCKING api_review.md
Combining Flags
Flags can be combined:
--dry-run --severity=BLOCKING: Preview only BLOCKING issues
--auto --severity=NIT: Auto-fix only NITs (safe for minor style fixes)
File Modification Rules
Source files: Modify to apply fixes
Review document: Update with status markers only
This skill does NOT commit: After processing, run /backend-atomic-commit:pre-commit to run pre-commit checks on staged changes
Strictness Guidelines
For [BLOCKING] issues: Be thorough, verify the fix addresses the root cause
For [SHOULD_FIX] issues: Apply the suggested fix, ensure it doesn't break tests
For [NIT] issues: Apply quickly, these are usually straightforward
Always read the source file before editing to understand context
If a proposed fix seems incomplete or incorrect, suggest improvements before applying
Integration Notes
This skill integrates with:
monty-code-review: Generates the review documents this skill processes
backend-atomic-commit: Runs pre-commit checks and fixes issues after processing
