Git commit push

Intelligence pack for software engineering based on Ainova Systems best practices

Install

npx -y skills add ainova-systems/intelligence-dev-packs --skill git-commit-push

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

Copied from the file, not written here

Verify, review, and push pending work as one milestone commit

1.8 KB, as published. Nobody here has run it

Land the pending work as one verified, cleanly described commit. Invoke at milestones - one commit = one shippable-for-testing unit.

git branch --show-current - on a protected branch (default/integration), STOP; work happens on feature branches (the orchestrators create them in Phase B).
Run the gates: typecheck + lint always, tests scoped to the change (dev-run-tests). Failure - fix or report, never bypass.
Review the diff: git status --porcelain + git diff. Drop debug leftovers and accidental files. Stage selectively with git add <paths> - never blanket git add -A (it sweeps secrets and parallel-session work).
One logical change per commit; unrelated edits split into separate commits. In spec-driven projects, tick the plan's ## Work steps boxes in the same commit as the code that earns them.
Message: one line, capital first letter, past tense, work-item id when the project uses them (Added export endpoint (FR-042)). An explicit argument overrides.
git commit, then git push (-u origin <branch> on first push). Remote moved - integrate per profile update_strategy, re-run gates, push again. Never force-push.

git log --oneline -1 shows the message; git status reports up to date with origin; gates were green on the pushed tree.

Opening the PR - git-open-pr; CI babysitting and the outcome label - git-finalize-pr (or spec-execute Phase E in spec projects).

No Co-Authored-By: or tool trailers; no feat:-style prefixes unless the profile commit_style requires them.
Never weaken a gate to commit (dev-verification-gates); never --no-verify.