Commit Push Pr
Git workflow: commit, push, and create/update a draft PR. If a PR exists for the current branch, update its body. Trigger: 'commit push pr', 'ship it', 'send a PR', or /commit-push-pr.
Install
$ agentstack add skill-lightbridge-ks-agent-skills-commit-push-pr ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ● Environment & secrets Used
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-lightbridge-ks-agent-skills-commit-push-pr) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Commit → Push → PR
Step 1: Gather Context
Run in parallel:
git status,git diff,git diff --staged,git log --oneline -10git branch --show-current,git rev-parse --abbrev-ref @{upstream} 2>/dev/nullgh auth statusgh pr list --head $(git branch --show-current) --json number,title,isDraft,url --limit 1
Hard stops:
- Stop if
gh auth statusfails. Report a clear fix (e.g., rungh auth login). - Stop if branch is
mainormaster.
Skip steps that aren't needed (e.g., nothing to commit → skip to push).
Step 2: Commit
- Stage files by name (never
git add -Aorgit add .) - Never commit files that likely contain secrets (
.env, credentials, tokens) - Follow project's commit conventions; default to Conventional Commits
- Use HEREDOC for multi-line messages
- Co-author trailer should be runtime-appropriate and configurable (do not hardcode Claude-specific identity)
Step 3: Push
- If no upstream exists:
git push -u origin HEAD; otherwisegit push. - If branch is high-risk or protected (e.g.,
release/*, protected remote branches), ask for explicit confirmation before pushing.
Step 4: Create or Update PR
- Get diff/log against base branch:
git log --oneline BASE..HEADandgit diff BASE...HEAD --stat - Draft PR body in a temp markdown file and use
--body-file(avoid inline multi-line shell quoting) - No existing PR →
gh pr create --draftwith title (<70 chars) and body summarizing all commits since base - Existing PR → Update body via
gh pr edit --body-fileincorporating new changes; keep title unless outdated - PR body:
## Summary+ bullet points +## Test planchecklist. Scale detail to change size.
Step 5: Optional Quality Checks (recommended)
Before push/PR, run project checks when available (e.g., test/lint/typecheck). If checks fail, report and ask whether to proceed.
Step 6: Report
Show: commit hash/message (if any), clickable PR URL, whether PR was created or updated, and whether checks passed/skipped.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Lightbridge-KS
- Source: Lightbridge-KS/agent-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.