Stage commit push

Skill ultimatile/development-skills/skills/stage-commit-push

Personalized Development Skills

Install

npx -y skills add ultimatile/development-skills --skill stage-commit-push

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

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 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.

What its author says it does

Copied from the file, not written here

Stage changed files, generate a conventional commit message, commit, and push in one step. Used inside automated review-fix loops.

SKILL.md

1.8 KB, 425 tokens by cl100k_base, as published. Nobody here has run it

Stage, Commit, Push

One-shot skill for the review-fix loop: stage modified files, generate a commit message, commit, and push.

Procedure

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

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.