← ClaudeAtlas

gm-fixgaplisted

Fix gaps identified by the Evaluator. Generates GAP.md from evaluation.json, dispatches workers to address critical/major issues, then runs one final verify+review pass. Unlike gm-build (PLAN.md-driven), gm-fixgap is GAP.md-driven. Explicit invocation only — use /gm-fixgap.
RandallLiuXin/GodotMaker · ★ 219 · AI & Automation · score 82
Install: claude install-skill RandallLiuXin/GodotMaker
# GodotMaker Fix Gap $ARGUMENTS You are fixing specific issues identified by the Evaluator. You read the evaluation report, generate a GAP.md task list, dispatch workers to address each gap, then run one final verify+review pass. **Loop position:** `/gm-fixgap` is never terminal. The cycle is `/gm-fixgap → /gm-verify → /gm-evaluate`. Evaluate either approves (→ `/gm-accept`) or surfaces new gaps (→ another `/gm-fixgap`). ## Session Setup **FIRST ACTION — before anything else:** Write `fixgap` to `.godotmaker/current_role`. ## Resume Check Read `.godotmaker/stage.jsonl` (treat as empty if missing) — each line is `{"role": X, "ts": Y}`. - If **no event with `role == "evaluate"`** exists anywhere in the file OR `.godotmaker/evaluation.json` does not exist → STOP. Tell user to run `/gm-evaluate` first. - If `evaluation.json` `result` is `"approve"` → STOP. Tell the user: > "The latest evaluation was already approved. Recommended next: /gm-accept. > If you need to redo this step or have other plans, just tell me." - If the **last event** has `role == "fixgap"` AND `GAP.md` is not at project root (already archived) → STOP. Tell the user: > "Fixgap already completed for the latest evaluation at {timestamp}. Recommended next: /gm-verify. > If you need to redo this step or have other plans, just tell me." - Otherwise → proceed (fresh fixgap or repeat fixgap is both valid). Then read context: - `GAP.md` (if present) → existing fix progress; find tasks not yet `verified