Format Changed

Format the current working-tree changes without taking ownership of Git state. The repository command owns changed-component detection; do not reproduce its path-to-component mapping in this skill or in ad hoc shell logic.

This is an explicitly on-demand skill. Routine dough-execute-plan wrap-up runs the same repository command directly and does not invoke this skill or spawn a formatting agent.

Workflow

1. From the repository root, record git status --short so the final report can identify the changed paths present before formatting.

2. Run the selective formatter through the repository runner:

   ./scripts/run.sh pnpm format:changed
   

   The command considers staged, unstaged, and nonignored untracked paths and formats only their affected components.

3. If the command reports a mechanically determined correction that it could not apply, make only that mechanical correction and rerun the command. Examples include formatter-prescribed whitespace, import ordering, or another result with one unambiguous non-behavioral fix.

4. If resolving a result could change behavior, public types, architecture, or design intent, stop without guessing. Preserve any formatting already applied and report the diagnostic and the judgment needed.

5. Record git status --short again and report every changed path remaining, including paths added or modified during formatting.

Never stage, commit, push, revert, restore, stash, or hide changes. Do not run format:all, duplicate component detection, or broaden the task beyond mechanical formatting results.

Handoff

On success, end the response with:

## FORMAT CHANGED COMPLETE

Include the command result and changed-path list immediately before the marker.

When judgment is required, include the failing diagnostic, changed-path list, and the decision needed, then end with:

## FORMAT CHANGED JIDOKA STOP