How do I install the Stage Commit Push skill?

Run npx skillmds@latest add ultimatile/stage-commit-push in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Stage Commit Push skill do?

Stage changed files, generate a conventional commit message, commit, and push in one step. It is listed under Coding & Dev Tools on SkillMD.

Is Stage Commit Push safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Stage Commit Push?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Stage Commit Push free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Stage Commit Push?

ultimatile (@ultimatile) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Stage Commit Push by ultimatile — Agent Skill

Name: Stage Commit Push
Author: ultimatile

File contents

Stage, Commit, Push

One-shot skill: stage modified files, generate a commit message, commit, and push.

Procedure

0. Route by working state

Check what there is to do before staging anything:

git status --porcelain                      # non-empty → changes to commit
git log --oneline HEAD --not --remotes      # non-empty → commits no remote has

The second command answers for a branch ahead of its upstream and for one that has no upstream yet, which git log @{upstream}..HEAD cannot. Route on the pair:

Changes to commit — run steps 1 through 5.
Nothing to commit, commits no remote has — skip to step 4 and continue through step 5. Staging nothing and committing nothing fails, and the push is what this invocation is for.
Neither — report that and make no change.

1. Stage

git add <specific files that were modified>

Stage only the files you changed. Do NOT use git add -A or git add . — be explicit about which files are staged. Never stage files that could contain secrets (.env, credentials).

2. Generate commit message

Inspect the staged diff and recent commits to produce a conventional commits message.

git diff --staged
git log --oneline -5

Type selection — based on what changed and why:

Documentation only → docs
Build/CI config → ci or build
Code style/formatting → style
Tests only → test
Deps/cleanup → chore
Restructuring without behavior change → refactor
New functionality that didn't exist before → feat
Existing functionality that was wrong/broken → fix

Size doesn't determine type. API signature changes that correct a mistake are fix, not feat.

Title length — keep the commit title (first line) to 72 characters or fewer. Use the body for details.

Exclusions — the message must NOT contain:

Phase/step numbers ("Phase 1", "Step 2")
Plan or task references ("As part of...", "Following the plan...")
Internal implementation context

3. Commit

git commit -m "$(cat <<'EOF'
<title>
<body>
EOF
)"

Always use HEREDOC for the message to preserve formatting.

4. Push

git push

If the branch has no upstream, use git push -u origin <branch>.

5. Report

After pushing, show the user:

The commit hash and message title
The branch and remote status

---name: stage-commit-pushdescription: Stage changed files, generate a conventional commit message, commit, and push in one step.---# Stage, Commit, PushOne-shot skill: stage modified files, generate a commit message, commit, and push.## Procedure### 0. Route by working stateCheck what there is to do before staging anything:```bashgit status --porcelain # non-empty → changes to commitgit log --oneline HEAD --not --remotes # non-empty → commits no remote has```The second command answers for a branch ahead of its upstream and for one that has no upstream yet, which `git log @{upstream}..HEAD` cannot. Route on the pair:- **Changes to commit** — run steps 1 through 5.- **Nothing to commit, commits no remote has** — skip to step 4 and continue through step 5. Staging nothing and committing nothing fails, and the push is what this invocation is for.- **Neither** — report that and make no change.### 1. Stage```bashgit add <specific files that were modified>```Stage only the files you changed. Do NOT use `git add -A` or `git add .` — be explicit about which files are staged. Never stage files that could contain secrets (.env, credentials).### 2. Generate commit messageInspect the staged diff and recent commits to produce a conventional commits message.```bashgit diff --stagedgit log --oneline -5```**Type selection** — based on what changed and why:- Documentation only → `docs`- Build/CI config → `ci` or `build`- Code style/formatting → `style`- Tests only → `test`- Deps/cleanup → `chore`- Restructuring without behavior change → `refactor`- New functionality that didn't exist before → `feat`- Existing functionality that was wrong/broken → `fix`Size doesn't determine type. API signature changes that correct a mistake are `fix`, not `feat`.**Title length** — keep the commit title (first line) to 72 characters or fewer. Use the body for details.**Exclusions** — the message must NOT contain:- Phase/step numbers ("Phase 1", "Step 2")- Plan or task references ("As part of...", "Following the plan...")- Internal implementation context### 3. Commit```bashgit commit -m "$(cat <<'EOF'<title><body>EOF)"```Always use HEREDOC for the message to preserve formatting.### 4. Push```bashgit push```If the branch has no upstream, use `git push -u origin <branch>`.### 5. ReportAfter pushing, show the user:- The commit hash and message title- The branch and remote status

Frequently asked questions

Stage Commit Push