process-reviews

Processes code review feedback files and implements accepted changes with documented reasoning.

2|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/SkinnnyJay/simpill-utils --skill process-reviews-skinnnyjay
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: process-reviews
Source: https://github.com/SkinnnyJay/simpill-utils/tree/main/.claude/skills/process-reviews
Command: npx skills add https://github.com/SkinnnyJay/simpill-utils --skill process-reviews-skinnnyjay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code review feedback often arrives as scattered markdown files, and deciding which comments to act on, tracking what was changed, and recording why items were rejected is tedious and error-prone. This Skill turns review feedback into a structured, auditable implementation workflow. ## Core Features & Use Cases - Feedback Triage: Reads review files matching ./scratchpad/review-*.md and evaluates each item for validity, security impact, and code quality. - Prioritized Implementation: Addresses security issues first, then low-risk quality improvements, deferring style preferences unless trivial. - Audit Trail: Writes results to ./scratchpad/review-<X>_fixed.md including processing date, source file hash, and per-item accept/reject reasoning. - Use Case: After a pull request review generates a review-42.md file, use this Skill to work through every comment, apply the accepted fixes, and produce a documented record of decisions for the reviewer. ## Quick Start Process the code review feedback files in the scratchpad directory and implement the accepted changes with documented reasoning.

Frequently Asked Questions about process-reviews

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I process code review feedback automatically?▼

Place review comments in markdown files named review-*.md inside a scratchpad directory, then run this Skill. It reads each file, evaluates every feedback item, implements accepted changes, and documents decisions in a corresponding review-fixed file.

How are code review comments prioritized for implementation?▼

Security issues are always addressed first, followed by low-risk code quality improvements. Best practices are implemented when scope allows, and style preferences are deferred unless the change is trivial.

What file format does the review feedback need to be in?▼

Feedback must be stored as markdown files matching the pattern review-*.md in the ./scratchpad/ directory. The Skill reads all matching files and processes each piece of feedback individually.

What happens to rejected code review feedback?▼

Rejected items are not silently dropped. Each one is recorded in the review-<X>_fixed.md output file with explicit reasoning for the rejection, alongside the processing date and the hash of the source review file.

When should I not use automated review feedback processing?▼

Avoid it when feedback requires broad architectural discussion or ambiguous business decisions that need human judgment. The Skill works best for concrete, actionable comments on security, quality, and best practices.