prompt-repair-executor

Executes incremental code fixes from review repair prompts using delta discovery and changed-file tests.

5|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/A158Coke/WotbTools --skill prompt-repair-executor-a158coke
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prompt-repair-executor
Source: https://github.com/A158Coke/WotbTools/tree/main/.agents/skills/prompt-repair-executor
Command: npx skills add https://github.com/A158Coke/WotbTools --skill prompt-repair-executor-a158coke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a reviewer hands you a repair prompt listing specific blockers, re-reading the entire repository wastes time and risks scope creep. This Skill enforces a disciplined repair workflow: parse the blockers, map them to real code via symbol search, fix only what is broken, and verify with targeted tests. ## Core Features & Use Cases - Delta Discovery: Uses git diff from the last reviewed SHA and symbol-first search (ripgrep) to locate blocker-related files in 1-3 minutes instead of scanning the whole repository. - Blocker-Scoped Fixing: Repairs only active blockers and their direct dependencies, marks already-resolved items, and protects locked passed areas from regression. - Changed-File Verification: Runs only the minimal test set covering modified files, delegating full repository validation to PR CI. - Use Case: You receive a PR review with 5 blockers (e.g., a dead component prop and a broken leagueMode contract). The Skill maps each blocker to its files, fixes them, runs the related unit tests, and produces a structured repair report. ## Quick Start Apply this repair prompt to the current branch, fix each listed blocker with minimal discovery, and run only the tests covering the files you changed.

Frequently Asked Questions about prompt-repair-executor

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

FAQPage Schema
How do I fix PR review blockers without re-reading the whole codebase?

Use delta discovery: run git diff from the last reviewed SHA, then search blocker symbols with ripgrep to map each issue to specific files. Read only the target file, its direct callers and callees, and related tests before fixing.

What is the difference between a repair executor and a plan executor?

A repair executor handles reviewer-identified blockers with minimal delta discovery, while a plan executor implements new features from a design plan using deep discovery. Use repair mode when blockers are already listed; use plan mode for new multi-module features.

Should I run the full test suite after fixing review comments?

No. Run only the tests covering files you actually modified, then push to the PR branch so CI performs repository-level validation. If CI fails, reproduce only the failing job's minimal test scope and push an additional commit.

When is it acceptable to expand code discovery during a repair?

Expand only when a symbol has multiple implementations, caller contracts are unclear, tests conflict with production behavior, cross-layer contracts cannot be confirmed, or shared infrastructure is affected. Each expansion must state its reason explicitly.

What happens if a repair prompt asks to remove code that no longer exists?

The blocker is marked ALREADY RESOLVED after confirming against the real code and tests. The workflow moves to the next blocker instead of making redundant changes just to satisfy the prompt.