rnd-formattinglisted

# Code Formatting ## Overview After a pipeline run produces code, run the project's formatter before doc-polish and committing. This ensures pipeline-written code matches the project's style without manual intervention. **Core principle:** Detect, don't assume. Every project has its own formatter (or none). Check config files first, then run the detected formatter on changed files only. ## Automatic Formatting (v2.1.90+) The `format-on-save.sh` PostToolUse hook automatically formats code files after every Write/Edit operation during an active RND session. It uses the same formatter detection logic described below, cached at session level. In the main checkout, auto-format runs on every write, so manual formatting of orchestrator-written files is typically redundant. Use this skill's manual process when: - You need to format files changed outside the pipeline (e.g., manual edits, git merge) - You want to format the entire project, not just individual files - The auto-format hook is not available (Claude Code < v2.1.90) ## When to Use (Manual) - In `/rnd-framework:rnd-start` Phase 6, before `rnd-doc-polish` ## Process ### 1. Get Changed Files Run `git diff --name-only` to get files changed by the pipeline. Filter to code files only. ### 2. Detect Formatter Check the project root for formatter config files. Stop at the **first match**: | Config File | Formatter | Command | |---|---|---| | `biome.json`, `biome.jsonc` | Biome | `biome format --write <files>` | | `.p