Commit push pr

Skill sneg55/agent-starter/skills/commit-push-pr

Full git workflow - creates branch, commits, pushes, and creates or updates a PR with summary and test plan.From its SKILL.md

Install

npx -y skills add sneg55/agent-starter --skill commit-push-pr

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

runs commandsInstructs the agent to run 8 commands, including `git status` and 7 more.

SKILL.md

2.6 KB, 601 tokens by cl100k_base, as published. Nobody here has run it

Commit, Push, and Open PR

Context

Gather this context first:

git status
git diff HEAD
git branch --show-current
git diff main...HEAD (or default branch)
gh pr view --json number 2>/dev/null || true

Git Safety Protocol

NEVER update the git config
NEVER run destructive/irreversible git commands (like push --force, hard reset, etc) unless the user explicitly requests them
NEVER skip hooks (--no-verify, --no-gpg-sign, etc) unless the user explicitly requests it
NEVER run force push to main/master, warn the user if they request it
Do not commit files that likely contain secrets (.env, credentials.json, etc)
Never use git commands with the -i flag (like git rebase -i or git add -i) since they require interactive input which is not supported

Task

Analyze ALL changes that will be included in the pull request - look at ALL commits from git diff main...HEAD, not just the latest commit.

Based on the changes:

1. Create branch (if on main/master)

Use the format username/feature-name:

git checkout -b username/descriptive-feature-name

2. Create a single commit

Use heredoc syntax for the message:

git commit -m "$(cat <<'EOF'
Commit message here.
EOF
)"

Follow the repo's commit message style (check git log --oneline -10)
Focus on "why" not "what"
Keep it concise (1-2 sentences)

3. Push the branch

git push -u origin HEAD

4. Create or update PR

Check if a PR already exists (from the gh pr view output above).

If PR exists - update it:

gh pr edit --title "Short title" --body "$(cat <<'EOF'
## Summary
<1-3 bullet points>

## Test plan
- [ ] Test item 1
- [ ] Test item 2
EOF
)"

If no PR - create one:

gh pr create --title "Short, descriptive title" --body "$(cat <<'EOF'
## Summary
<1-3 bullet points>

## Test plan
- [ ] Test item 1
- [ ] Test item 2
EOF
)"

Rules:

Keep PR titles under 70 characters. Use the body for details.
Summary should be 1-3 bullet points covering WHAT changed and WHY
Test plan should be a checklist of verification steps

5. Return the PR URL

Do all of the above in a single message using multiple tool calls. Return the PR URL when done.

What ships with it

Read from the repository

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

Gives 1 of the 12 instructions most pr commit review skills give in 601 tokens

Counted across 1,055 of the 1,911 authors here whose files we hold, read 2026-09-06

Use conventional commit message formatin 150 of 1055, across 145 files
Announce skill usage at startin 78 of 1055
Use imperative mood for commit descriptionsin 54 of 1055, across 51 files
Add directory to gitignore if not ignoredin 52 of 1055, across 41 files
Use imperative mood for commit subjectin 52 of 1055
Run tests to verify clean baselinein 42 of 1055, across 32 files
Push branch to originhere, and in 40 of 1055, across 38 files
Verify worktree directory is ignored before creationin 39 of 1055, across 32 files
Delete branches after mergingin 38 of 1055, across 30 files
Create worktree with new branchin 37 of 1055, across 32 files
Wrap body text at 72 charactersin 36 of 1055, across 34 files
Auto-detect and run project setupin 35 of 1055, across 27 files

Said here and by no other author read

Keep pull request titles under 70 characters

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.