auto-fix

Fix

Diagnose and fix the issue: $ARGUMENTS

Step 0 — Load Extensions

Injected by the override loader ([skill-overrides] block); none shown → none exist.

Project extensions define framework-specific log paths (e.g., Electron logs in %APPDATA%/<app>/logs/, Angular dev server console, etc.).

Codex context: Read {PLUGIN_ROOT}/deep-knowledge/codex-integration.md — this skill auto-invokes Codex on unclear root cause (§2 in that doc). Codex MUST be called via {PLUGIN_ROOT}/scripts/codex-safe.sh (5-min hard timeout, see "Hard Timeout & Failure-Tolerance" section), NEVER via the /codex:rescue Agent tool. Detect Codex availability now so Step 6 can act on it.

Step 1 — Triage: what broke?

If $ARGUMENTS is empty or vague, ask ONE focused question via AskUserQuestion:

• "Was ist passiert?" with options like: "Error in console", "Blank screen", "Crash on startup", "Wrong behavior"
• Do NOT ask multiple questions — get the symptom, then investigate.

Step 2 — Check recent changes first

The most common cause of bugs is recent code changes. Before reading logs:

git log --oneline -5
git diff HEAD~1 --stat

If the symptom appeared after a specific commit, focus investigation there.

Step 3 — Discover and read logs

Search for logs automatically — don't assume fixed paths:

1. Glob for **/*.log and **/logs/** in the project root
2. Check project extension for framework-specific log locations
3. Read the most recent log file first — don't read all unless needed

Step 4 — Locate the failure point

Search for the error string via Grep. Follow the stack trace to the originating file and line.

Step 5 — Root cause analysis

Find the actual broken invariant — not just the symptom. Ask:

• What assumption is violated?
• What changed that broke this assumption?
• Is this a data issue, a logic issue, or a configuration issue?

Step 6 — Decision: fix or propose?

Situation	Action
Trivial fix (typo, missing import, off-by-one)	Fix immediately, report what was wrong
Clear root cause, low risk (single file)	Fix immediately, explain root cause
Clear root cause, medium risk (multiple files)	Propose fix via AskUserQuestion
Unclear root cause	Present findings, propose 2-3 hypotheses, ask user. Automatically invoke Codex via Bash: bash "{PLUGIN_ROOT}/scripts/codex-safe.sh" "<investigation prompt>" for parallel independent investigation. Handle exit codes per codex-integration.md "Hard Timeout" section: rc=124 → continue without Codex findings, note "Codex timed out"; rc=75 → usage limit (stored until reset), continue without Codex, note it; rc=126/127 → skip silently. Never use the /codex:rescue Agent tool.
Architectural issue	Report root cause, do NOT fix — recommend planned approach