---
name: Formax Dev Loop
slug: formax-dev-loop
category: Quality
description: Formax Dev Loop helps you work on Formax changes with a single mainline task, targeted tests, required review before commit, and small reviewable commits. Use it when you need a tight dev loop without scope drift or partial staging.
github: "https://github.com/yusifeng/formax/tree/main/.codex/skills/formax-dev-loop-workflow"
language: TypeScript
stars: 192
forks: 7
install: "npx degit https://github.com/yusifeng/formax/tree/main/.codex/skills/formax-dev-loop-workflow ~/.claude/skills/formax-dev-loop-workflow"
installs_to: ~/.claude/skills/formax-dev-loop-workflow
source_path: .codex/skills/formax-dev-loop-workflow/SKILL.md
collection_size: 22
category_size: 1745
collection_url: "https://dirskills.com/collections/yusifeng/formax"
added: 2026-09-06T05:19:17.914Z
last_synced: 2026-09-06T05:19:17.914Z
canonical_url: "https://dirskills.com/skills/formax-dev-loop"
---

# Formax Dev Loop

Formax Dev Loop helps you work on Formax changes with a single mainline task, targeted tests, required review before commit, and small reviewable commits. Use it when you need a tight dev loop without scope drift or partial staging.

**Install:**

```bash
npx degit https://github.com/yusifeng/formax/tree/main/.codex/skills/formax-dev-loop-workflow ~/.claude/skills/formax-dev-loop-workflow
```

## README

# Formax Dev Loop (Mainline Discipline)

## Default loop (repeat per TODO item)

1) **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.

2) **Write/adjust tests first** to lock behavior (when feasible).

3) **Implement** the smallest change that satisfies the item.

4) **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.

5) **Run only targeted tests** (never `bun run test:coverage` unless 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 -- --all` only when you intentionally want staged + unstaged + untracked.

6) **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.

7) **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

```bash
# 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)"
```