git-add-commit-push

Git Add, Commit, and Push

Stage, commit, and push in one flow, healing lefthook pre-commit and pre-push failures on the way; conventional-commit owns the subject grammar.

Workflow

1. Pick the branch: git branch --show-current. Direct commits to main are the rule for github.com/fmind/*; elsewhere, or for a requested PR flow, branch first with feature-branch.

2. Stage: git diff --cached --name-only shows what is staged; if nothing is, git status --short shows the unstaged changes to add with git add. A clean tree ends the flow: say so and stop.

3. Write the subject with the conventional-commit rules, but do not run its commit step: this skill commits and heals hook failures itself.

4. Commit and heal pre-commit:

   git commit -m "<subject>"
   

   On a hook failure, read its output, run mise run format and mise run check, fix type or compile errors, git add the touched files, and retry with the same subject until it passes or a blocker needs the user.

5. Push and heal pre-push:

   git push -u origin "$(git branch --show-current)"
   

   On a mise run test failure, read the runner output, fix the code or tests, git add the fix, fold it in with git commit --amend --no-edit, and retry until the push passes or a blocker needs the user.

6. Report after a successful push:

   Subject: <subject>
   Commit: <hash>
   Status: Pushed to origin/<branch>
   

Gotchas

• Hooks are the gate: Do not use --no-verify or bypass hooks unless the user explicitly asks; diagnose and fix the failure instead.
• One commit per push: amend hook fixes into the pending commit before pushing; never amend a commit that already reached the remote.
• Rejected push: branch protection on main means the repository wants a PR flow; switch to feature-branch and github-pull-request.