git-add-commit-pushlisted

# Git Add, Commit, and Push Stage, commit, and push the authorized change, preserving existing work and repairing hook failures within that scope. [conventional-commit](../conventional-commit/SKILL.md) owns the subject grammar. ## Workflow 1. **Resolve scope and branch**: inspect `git status --short --branch`, `git diff`, and `git diff --cached`. Direct work on `main` is allowed for `github.com/fmind/*`; follow an explicitly requested PR flow or the repository's branch policy through [feature-branch](../feature-branch/SKILL.md). 1. **Preserve the index**: retain an existing staged selection. When staging is requested, add only the intended files or hunks; a dirty tree or an empty index does not authorize `git add -A`. Stop when there is no authorized change to commit. 1. **Write the subject** with the [conventional-commit](../conventional-commit/SKILL.md) rules, then run `git commit -m "<subject>"` once. 1. **Heal pre-commit**: read the failure, fix its cause, and rerun the affected check through `mise run check`. Format only the intended paths; use an isolated candidate for a whole-tree formatter when unrelated work exists. Review and restage only the authorized fixes before retrying. 1. **Push the candidate**: verify the destination, then `git push -u origin "$(git branch --show-current)"`. A push to another repository or branch needs its own scope. 1. **Heal pre-push**: reproduce the failing `mise run test` case and fix the cause without weakening assertions. Amend only