oc-committing-changeslisted

# Committing-Changes — standalone semantic commit Standalone commit. Use when you want to commit now without running the full delivery loop. For full delivery (review + security + docs + PR), the `shipper` agent does the git flow — dispatch it via `task` (or let `build` drive it in Phase 5). This skill is the lighter, no-PR path; it conforms to the SAME `AGENTS.md` §4 git rules the shipper does. ## When to use - Intermediate commit during development (WIP you will squash later). - Trivial change on your own branch that needs no formal review. - Commit on a branch that already has an open PR (continuing work). **Do NOT use for:** - A change ready to deliver — use the `shipper` agent (branch + PR). - A commit on `main` — forbidden by default (always branch + PR, per AGENTS.md §4). ## Flow ### 1. Verify state ```bash git status --short git diff --stat git log --oneline -5 ``` If there are no changes, report and exit. ### 2. Sanity check of files Flag as probable junk (same list the `shipper` uses): - `.dev.vars`, `.env*`, `.local.*` - `node_modules/`, `dist/`, `coverage/` - `.DS_Store`, `*.log` - any credential / token file Confirm with the operator (pt-br, product-language) before proceeding if any of these appear. ### 3. Local checks Run the minimum defined in the project's root `CLAUDE.md`/`AGENTS.md` (Commands section). Typical: ```bash npx tsc --noEmit ``` If it fails, stop. Skip `npm test` here (can be costly) — the full `shipper` flow inherits green gates from