Commit staged or unstaged changes, push the branch, and open a pull request in one shot. Archived pending consolidation with the canonical commit workflow.
Penalty-box skill. Do not keep this in active discovery until its boundary is rewritten relative to git-commit.
git status --short and git diff HEADmain/master, create a feature branch: git checkout -b <type/short-desc>git add -A unless all changes are in scope.feat|fix|refactor|...)../scripts/committer if present; else git commit -m "...".git push -u origin <branch>bd issue id).bd close <id> --reason "shipped in PR #N".gh pr create --title "..." --body "..." with the structure below.Always use this order:
## Impact
- <1-3 bullets: concrete effect on the user or system — not what changed, but why it matters>
## Summary
- <what changed, per tracker item>
## Test plan
- [ ] <how to verify>
The Impact section answers "so what?" — e.g. "Calibration no longer promotes correlated signals" or "Users see a 40% faster load time." Avoid restating the summary bullets. If the change is purely mechanical (rename, doc-only), one brief bullet is fine.
--no-verify.main/master.