git-commit-all

Stage all working-tree changes and create a conventional commit with optional push and CI monitoring.

10|1|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/catalystctl/catcode --skill git-commit-all-catalystctl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit-all
Source: https://github.com/catalystctl/catcode/tree/main/.catalyst-code/skills/git-commit-all
Command: npx skills add https://github.com/catalystctl/catcode --skill git-commit-all-catalystctl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Committing a multi-file change involves many error-prone steps: verifying the build, staging the right files, writing a descriptive message, updating the changelog, pushing, and watching CI. This Skill automates that entire flow so a coherent set of changes lands as a clean, well-described commit without sweeping in unrelated work. ## Core Features & Use Cases - Full commit pipeline: Shows git status/git diff --stat, runs the project's build and CI gates (cargo fmt/clippy/test, gofmt/go vet/go test -race, tsc), stages everything with git add --all, and commits with a conventional-commits message derived from the diff. - Changelog and push handling: Adds a dated CHANGELOG.md bullet referencing the commit SHA as a separate docs(changelog) commit, then pushes with upstream detection, rebase-on-reject, and optional gh run watch CI monitoring until green. - Concurrent-session safety: Detects other agents' in-flight edits in the shared working tree and uses hunk-level staging via git apply --cached to commit only your own changes. - Use Case: After finishing a refactor spanning core, tui, and web, say "commit all and push" to get verified, grouped commits, an updated changelog, and a watched green CI run. ## Quick Start Ask the agent to commit all current git changes with a descriptive message and push to the remote.

Frequently Asked Questions about git-commit-all

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I commit all changes in git with one command?

Use git add --all to stage modified, new, and deleted files, then git commit with a message built from the diff. This Skill automates that flow, including showing git status first and verifying the project compiles before committing.

How to write a good git commit message from a diff?

For small diffs, git diff --cached --stat is enough; for large multi-feature diffs, read the full diff to enumerate each change. Follow conventional commits: type(scope): subject under 72 characters, with bullet points grouped by module.

Can I commit and push when the branch has no upstream?

Yes. Check the current branch with git rev-parse --abbrev-ref HEAD, then run git push -u origin <branch> to set the upstream on first push. On non-fast-forward rejection, run git pull --rebase before pushing again.

Why does git add --all cause problems with multiple agents?

In a shared working tree, git add --all stages other sessions' unfinished edits into your commit. Instead stage only your files explicitly, or use git apply --cached with a filtered patch for hunk-level staging of entangled shared files.

When should I not use git add --all to commit everything?

Avoid it when the tree contains unrelated logical changes, merge conflicts, or another agent's in-progress work. Commit each logical change separately with explicit git add <paths>, and abort entirely if unmerged conflict paths exist.