Agent skill
formax-dev-loop-workflow
Use when working on Formax code changes and you need a disciplined dev loop: keep a single mainline task, avoid scope drift, run only targeted tests (no coverage), avoid partial staging (MM), run mandatory review before commit, include an incremental optimization check, and keep commits small and reviewable.
Install this agent skill to your Project
npx add-skill https://github.com/yusifeng/formax/tree/main/.codex/skills/formax-dev-loop-workflow
SKILL.md
Formax Dev Loop (Mainline Discipline)
Default loop (repeat per TODO item)
-
Pick one mainline item and finish it end-to-end before starting another.
- If a new idea appears mid-flight, write it down in a backlog note and continue the mainline.
-
Write/adjust tests first to lock behavior (when feasible).
-
Implement the smallest change that satisfies the item.
-
Incremental optimization check (required)
- After implementation, do a quick pass:
- Is there newly-dead/unused logic introduced by this increment?
- Is there a low-risk simplification that reduces branching/duplication?
- If yes, include a small optimization in the same item (no scope drift, no behavior change).
- If no, explicitly proceed without optimization.
- After implementation, do a quick pass:
-
Run only targeted tests (never
bun run test:coverageunless explicitly asked).- Preferred:
bun run test -- <changed-test-files...> - Helper (repo):
bun run test:changed- Use default (staged only) for the commit you are about to make.
- Use
bun run test:changed -- --allonly when you intentionally want staged + unstaged + untracked.
- Preferred:
-
Pre-commit hygiene
- Avoid partial staging (“MM” state). If needed, check with:
bun run check:partial-stage
- Run review before every commit using
AGENTS.md->Review Profile (Single Source of Truth). - If review returns findings: fix -> re-run targeted tests -> re-run review.
- Avoid partial staging (“MM” state). If needed, check with:
-
Commit
- Keep it small (2–4 files ideally, unless refactor forces more).
- Prefer one concern per commit (tests + implementation together for that concern).
Guardrails (Formax-specific)
- Do not fix unrelated failures mid-loop unless they block the mainline.
- If a command would usually be run with pipes/redirections for convenience, prefer running it plain and rely on Formax’s own output truncation/Expand UI.
- Don’t “clean up” formatting/copy/colors/spacing unless explicitly requested or required for parity.
Quick commands
# Detect partial staging (“MM”)
bun run check:partial-stage
# Run related tests for staged changes
bun run test:changed -- --dry-run
bun run test:changed
# Include unstaged + untracked (when explicitly intended)
bun run test:changed -- --all
# Required before commit (review profile)
# See AGENTS.md -> "Review Profile (Single Source of Truth)"
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
formax-rework-convergence-workflow
Use when code has gone through repeated rework and may contain redundant logic, style drift, or tangled structure. Trigger when user asks for "返工收敛", "cleanup-pass", or requests a focused cleanup pass that reduces churn without changing behavior.
formax-tool-ui-blocks-workflow
Implement or refactor Formax tool transcript UI using the Tool UI Blocks (C-lite) pattern (ToolUiBlocks renderer + blocks presenters) to avoid touching many tool presenter files; use when adjusting ⏺/⎿ spacing, indent rules, or migrating additional tools to blocks presenters with targeted Ink/Vitest tests and Codex review before commit.
formax-web-css-convergence-workflow
Use when changing web CSS/UI styling so requirements, state ownership, and acceptance checks are locked before edits to prevent rework churn.
formax-config-settings-workflow
Use when implementing or extending /config (storage, prompt injection, request params, UI-only toggles) with tests and strict UI parity.
formax-semantics-parity-workflow
Use when implementing or modifying behavior that must stay consistent across TUI and Web (mode/input/tool/replay/order). Require canonical semantics first, then TUI/Web adapters, then renderer-specific UI.
formax-rolling-plan-loop-workflow
Use when the user wants a reusable rolling execution pattern (README + TODO-INDEX) like plans/web-reference-react-refactor, and wants to run delivery in small validated loops.
Didn't find tool you were looking for?