apply-fixes

Apply Fixes

Role: implementation. This skill modifies code — it receives correction prompts and applies minimal fixes.

You have been invoked with the /apply-fixes skill. Load correction prompt JSON files and apply each fix.

Implementation constraints

1. Apply the minimal fix. Do not refactor, reorganize, or improve beyond what the correction prompt instructs.
2. Validate after each fix. Run lint/build/tests unless skipped. If validation fails, report and move on — do not attempt cascading fixes.
3. Follow repository rules. Read CLAUDE.md, .clinerules, CONTRIBUTING.md before applying fixes.
4. One concern per fix. Each correction prompt addresses one issue. Do not combine or reorder fixes.
5. Be concise. Report results in the summary table format. No narration of each step — just the outcome.

Parse Arguments

Arguments: $ARGUMENTS

Required: path to directory containing correction prompt JSON files ($0)

Optional:

• --repo <path>: Target repository path (default: current working directory)
• --skip-tests: Skip running tests after each fix
• --skip-build: Skip running build after each fix
• --skip-lint: Skip running lint after each fix
• --dry: Preview what would be applied without making changes
• --verbose: Show detailed output

Steps

1. Load repository rules

Detect and read rules from the target repository:

• CLAUDE.md
• .clinerules
• .claude/rules/index.md
• CONTRIBUTING.md

These rules inform how fixes should be applied.

2. Load correction prompts

Read all .json files from the specified directory, sorted alphabetically. Each file contains:

{
  "priority": "high|medium|low",
  "confidence": "high|medium",
  "category": "<agent-name>",
  "instruction": "<what to fix>",
  "context": "<where>",
  "affectedFiles": ["<path>"]
}

Note: correction prompts are only generated for issues with confidence: high or confidence: medium. Issues with confidence: none are surfaced in the review report only and do not produce correction prompt files.