Agent skill · software engineering · aiskillstore
process-code-review
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.
Why this skill is useful
Adds an executable script for processing code review findings interactively, including automated fixes and quality checks that aren't in public docs.
What it needs
Requires bash, todo-write installed locally. About 5k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
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: Example Prompts Basic Usage "Process the wellbeingservicereview.md file and help me fix the issues." "Use your process-code-review skill on optimocore/docs/codereviews/apireview.md" "Go through the code review findings in this file and fix or skip each one." With Arguments /process-code-review:process-review myfilereview.md - Interactive mode (default) /process-code-review:process-review --dry-run myfilereview.md - Preview only, no changes /process-code-review:process-review --auto myfilereview.md - Auto-fix all issues /process-code-review:process-review --auto --severity=NIT myfilereview.md - Auto-fix only NITs /process-code-review:process-review --severity=BLOCKING apireview.md - Process only BLOCKING issues Processing Workflow When this skill is active and you are asked to process a review document: 1. Parse Review Document Read the review file and extract all issues. Look for: Severity tags: [BLOCKING], [SHOULDFIX], [NIT] Issue titles: Following the severity tag Location: File path and line numbers Code snippets: Current problematic code Problem description: Explanation of the issue Proposed fix: Suggested code or approach Common patterns to look for: 2. Create Todo List Use TodoWrite to track all issues: Group by severity: BLOCKING first, then SHOULDFIX, then NIT Mark each as pending initially Update status as you process each issue Example todo list structure: 3. Present Issues One-by-One For each issue, starting with highest severity, display: Then ask: Fix this issue or skip it? Wait for user response before proceeding. 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/process-code-review