jp-codereview-fix

Name: jp-codereview-fix
Availability: InStock
Author: JingleManSweep

Generate scoped patches for CRITICAL and MAJOR code review issues.

Updated Feb 26, 2026

Search Tags:#automation #git #workflow #planning #code-fix #codereview

Ready to run

npx skills add https://github.com/jinglemansweep/agent-resources --skill jp-codereview-fix

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: jp-codereview-fix
Source: https://github.com/jinglemansweep/agent-resources/tree/main/plugins/jplan/skills/jp-codereview-fix
Command: npx skills add https://github.com/jinglemansweep/agent-resources --skill jp-codereview-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It provides targeted, context-aware corrections for CRITICAL and MAJOR issues identified during code reviews, ensuring changes are scoped and auditable.

Core Features & Use Cases

Focused fixes: applies only the issues listed in the latest review cycle.
Safe edits: avoids architectural changes and preserves surrounding logic.
Audit trail: records fixes in a round ledger for traceability and rollback.

Quick Start

Run /jp-codereview-fix <phase-path> to apply targeted fixes from the latest review cycle.

Frequently Asked Questions about jp-codereview-fix

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

FAQPage Schema

How do I automate targeted fixes for critical code review issues?▼

Targeted fixes for critical code review issues are automated by generating scoped patches that address specific CRITICAL and MAJOR findings without triggering broader refactoring or architectural drift.

What is the best way to apply code review fixes without breaking surrounding logic?▼

Applying code review fixes without breaking surrounding logic requires enforcing disciplined, safe edits that strictly preserve existing architecture and only modify the code scoped to the latest review cycle.

How do code review fix ledgers work for traceability?▼

Code review fix ledgers work for traceability by recording each applied patch and its outcome in a centralized log, ensuring every automated correction can be audited and rolled back if necessary.

Can I apply code fixes only to the latest review cycle inputs?▼

Yes, you can apply code fixes only to the latest review cycle inputs by running the targeted fix workflow against the specific phase-path, ensuring corrections are focused and do not touch unrelated code.

When should I avoid automated code fix workflows?▼

You should avoid automated code fix workflows when your issues require broad architectural changes, as this process enforces disciplined scoped patches and intentionally prevents structural drift.