ddw-commitlisted

# Skill: /ddw-commit ## Description Creates a commit following Gitmoji + Conventional Commits, with mandatory AI attribution. ## Inputs - The staged changes in git. - `.ddw-state.json` for the ticket and tier. - `.ddw/rules/commits.instructions.md` for the format and the gitmoji reference table. ## Execution Protocol 1. Run `git status` and `git diff --staged`. 2. If nothing is staged, look at the working tree: - **Dirty** → ask the user which files to include. - **Clean, in CLOSEOUT** → there is nothing left to commit, because the earlier phases already committed their own artifacts. Do NOT manufacture an empty commit: run `git log <base>..HEAD --oneline`, show the branch's commits, and report the gate as satisfied by them. - **Clean, in any other phase** → this phase produced nothing to commit. Say so and stop. 3. Check there are no files carrying secrets (.env, credentials). 4. Check the gates **this phase's commit depends on**, and note that CODE commits twice for different reasons: - **A block commit in CODE** — code plus its tests, as each block passes its reviews and its tests, which is what `.ddw/rules/commits.instructions.md` mandates — depends on **that block's** reviews and tests, not on the phase gates. `tests` and `sast` are earned over the whole phase and are still false while the blocks are being committed one at a time; demanding them here forbade the very commit the rules require. - **The phase's closin