Project Fix

# project-fix

> Implements corrections found by `/project-audit`. Reads `audit-report.md` as
> a spec and executes each required action.

**Triggers**: `/project-fix`, apply audit corrections, fix claude project, implement audit

---

## Sibling reference file

- `STUB_TEMPLATES.md` — SDD section template, skill stub templates, flag
  markers, changelog entries. Read at execution time when applying handlers.

## Role in the SDD meta-config flow

```
/project-audit  →  audit-report.md  →  /project-fix  →  /project-audit (verify)
     (spec)           (artifact)          (apply)           (verify)
```

`audit-report.md` is the INPUT. Without it this skill cannot operate.

**Absolute rule**: NEVER invent corrections. Only implement what is in
`FIX_MANIFEST`.

---

## Prerequisite

Verify `.claude/audit-report.md` exists.

| Condition           | Action                                                                 |
|---------------------|------------------------------------------------------------------------|
| File absent         | Print `"❌ .claude/audit-report.md not found — run /project-audit first"` and stop. |
| File > 7 days old   | Ask: `"⚠️ Report is [N] days old. (1) use anyway, (2) re-audit first?"` and wait. |

## Execution model

Three stages: **manifest intake** (read + validate + class), **phase execution**
(apply by severity), **final reporting** (changelog + summary).

## Action classes

| Class           | Examples                                                              | Side effects | Confirmation                       |
|-----------------|-----------------------------------------------------------------------|--------------|------------------------------------|
| Automatic       | create missing files, append sections, add markers                    | yes          | inside approved phase flow         |
| Guided          | delete duplicate local skills, optional phase decisions               | yes          | explicit confirmation required     |
| Informational   | `move-to-global`, language violations, deprecated/unknown manifest   | no           | report only                        |

Class beats handler name. Informational items never gain automatic mutation
behavior just because they appear in the manifest.

## Compatibility policy

Explicit. Current rules:
- **Stale-manifest**: older audit reports with deprecated actions → safety first, no speculative edits.
- **Deprecated mechanisms**: any action targeting `.claude/commands/` is skipped (deprecated).
- **Two-tier placement**: `move-to-global` is informational only. No automated writes to `~/.claude/skills/`.
- **Unknown actions**: downgraded to skip-or-recommendation, never automatic mutation.

---

## Process

### Step 1 — Parse the FIX_MANIFEST

Read the `FIX_MANIFEST` block from `audit-report.md`. Extract:

- `required_actions.critical[]`, `.high[]`, `.medium[]`, `.low[]`
- `missing_global_skills[]`
- `orphaned_changes[]`
- `violations[]`
- `skill_quality_actions[]` (Dimension 9 — may be absent)

Classify each item as automatic, guided, or informational per the table above.
Deprecated/unsupported/unknown action types are reported as
`skipped` or `recommendation only`. The rest of the run continues.

Present the summary:

```
📋 Fix Plan — [Project Name]
Based on audit from [date]
Current score: [XX]/100

Actions to execute:
  ❌ Critical : [N] actions
  ⚠️ High     : [N] actions
  ℹ️ Medium   : [N] actions
  💡 Low      : [N] actions (optional)

Execute corrections?
  S → All recommended (critical + high + medium)
  C → Critical only
  R → Review one by one
  N → Cancel
```

Wait for the user.

### Step 2 — Execute by phases

Phases run in severity order. Each phase ends with a checkpoint requiring