On-demand preparation of working-tree changes for commit by selectively formatting affected components. Use when explicitly requested outside the routine dough-execute-plan wrap-up; stop when a formatter result needs semantic or design judgment.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
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.
From the repository root, record git status --short so the final report can
identify the changed paths present before formatting.
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.
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.
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.
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.
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
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Backend Java — Spring Boot controllers/services, JUnit controller tests, MakeMe. Read this first for any backend work. Use when working on the Java Spring backend.
The English summary is being prepared. Showing the original description.
Backend Java production code, Spring Boot controllers/services/repositories, controller return values, imports, schema ERD pointer. Use when editing backend production Java.
The English summary is being prepared. Showing the original description.
Backend Java tests, controller-level stable-boundary tests, JUnit, @Nested, MakeMe builders, @Transactional, parameterized tests. Use when writing or changing backend JUnit tests.
The English summary is being prepared. Showing the original description.
related to donut CLI. Use when working on donut-cli.
The English summary is being prepared. Showing the original description.
Set up and run the Donut dev environment on Cursor Cloud VM (no Nix). Use when working on Cloud VM, running tests on Cloud VM, or encountering command errors related to missing nix. Triggers on: cloud VM, cloud agent, no nix available, /workspace path.
The English summary is being prepared. Showing the original description.
Regenerate docs/database-erd.md from MySQL information_schema (Mermaid ERD: foreign keys and key columns). Use after Flyway schema changes, new migrations, or when the diagram is stale. Triggers on: database ERD, database-erd.md, export_database_erd, schema diagram, ER diagram after migration.
The English summary is being prepared. Showing the original description.