iw-fix-gateslisted

# Fix Gates — Run Both Gates, Understand Every Failure, Then Fix You will run both the project's gates (quality and tests), gather every failure across every category up-front, and then fix them. The skill exists because most LLM "fix the failing test" loops drift into anti-patterns — weakening assertions, adding `@pytest.mark.skip`, slapping `# type: ignore`, shortcutting to `assert True`. **That is not what this skill is for.** > **Before any fix: understand what the test or gate is guarding. The fix must > preserve that intent. If you cannot articulate the intent, you cannot fix it > — flag it as unresolved.** This is a **developer tool**, not a daemon-driven workflow. No work item is created, no worktree is spawned, no commit is made. The operator reviews `git diff` and the session log, then commits manually. --- ## Phase 0 — Resolve project and pre-flight 1. **Identify project** by walking up from the cwd until finding a parent directory that matches a `repo_root` entry in IW AI Core's `projects.toml`, or by running: ```bash uv run --directory /home/sergiog/dev/iw-doc-plan/main/iw-ai-core \ iw current-project 2>/dev/null ``` If the project is unknown to IW AI Core or `enabled = false`, stop and report. Never proceed against an unregistered project. 2. **Snapshot working tree:** ```bash git -C <repo_root> status --porcelain ``` If the tree is dirty, ask the user to confirm before continuing. Dirty trees make it harder to spo