engineering-fix

Engineering Fix

Input: $ARGUMENTS

Applies the remediation plan produced by /engineering-audit. Operates exclusively on an isolated branch. Never modifies files directly on the current branch. Always requires explicit user confirmation before starting.

---

Pre-conditions

Before running any fix:

1. Confirm audit exists:

ls .egc/audits/engineering-audit-*.md 2>/dev/null | sort | tail -1

If no audit report exists, stop: "Run /engineering-audit first."

1. Confirm working tree is clean:

git status --porcelain

If uncommitted changes exist, stop: "Stash or commit your changes before running engineering-fix."

1. Confirm user intent: print the scope and ask explicitly:

Ready to apply engineering fixes.

Scope: <CRITICAL only | CRITICAL + HIGH | etc. based on $ARGUMENTS>
Branch: engineering-fix/<date>
Files to modify: N

This will:
  1. Create branch engineering-fix/<date>
  2. Apply each fix incrementally
  3. Run lint + typecheck + tests after each file
  4. Revert and stop if any check fails

Confirm? (yes / no)

Do NOT proceed without a "yes" response.

---

Argument Handling

Argument	Behavior
--severity critical	Apply CRITICAL fixes only (default)
--severity high	Apply CRITICAL + HIGH fixes
--severity medium	Apply CRITICAL + HIGH + MEDIUM fixes
--severity all	Apply all findings
--file <path>	Apply fixes to one specific file only
blank	CRITICAL fixes only

---

Execution

Step 1: Create Isolated Branch

git checkout -b engineering-fix/$(date +%Y-%m-%d)

Step 2: Load Remediation Plan

Read the most recent audit report:

cat .egc/audits/engineering-audit-$(ls .egc/audits/ | grep engineering-audit | sort | tail -1 | sed 's/engineering-audit-//' | sed 's/\.md//')

Extract the list of files and fixes matching the requested severity.

Step 3: Apply Fixes Incrementally

For each file in the plan (CRITICAL first, then HIGH, etc.):