Commit push pr
Agent skills for AI coders
npx -y skills add dceoy/ai-coding-agent-skills --skill commit-push-prAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 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
Commit staged and unstaged changes, push the branch to origin, and open a pull request using the GitHub CLI. Use when the user asks to commit, push, and create a PR in one workflow.
SKILL.md
2.3 KB, as published. Nobody here has run it
Commit, Push, and PR Skill
Create a commit from current changes, push to a remote branch, and open a pull request in a single workflow.
When to Use
- After completing a feature or fix and wanting to open a PR in one step.
- When all changes are ready to commit, push, and submit for review.
Agent Compatibility
This skill is tool-agnostic and can be executed by Claude Code, Codex CLI, or Cursor CLI.
Inputs
- Current repository with uncommitted changes (staged or unstaged).
If there are no changes to commit, report that and stop.
Do not include unrelated user changes unless the user explicitly asked to include them.
Workflow
-
Gather context by running these commands in parallel:
git status git diff HEAD git branch --show-current -
Create a new branch if currently on
main(or the repository's default branch). Use an appropriate prefixed branch name based on the changes, following repository guidance such asfeature/...,bugfix/...,refactor/...,docs/..., orchore/.... -
Stage and commit all relevant changes with a concise, descriptive commit message summarizing the changes. Prefer explicit paths over
git add .when unrelated changes are present. -
Push the branch to origin:
git push -u origin <branch-name> -
Create a pull request using the GitHub CLI:
gh pr create --title "<title>" --body "<description>"Include a clear title and summary of changes in the PR body. If repository guidelines request draft PRs or labels, apply them by default.
All steps should be executed efficiently once scope is clear. Do not perform unrelated cleanup or broad refactors while preparing the PR.
Outputs
- A new git commit on the current or newly created branch.
- The branch pushed to origin.
- A pull request created on GitHub (URL printed to console).