Best for
- Use when the user wants to commit and create a PR, push changes and open a pull request, or ship their current work as a PR.
Source profileQuality 80/100Review permissions
dyoshikawa/rulesync/.rulesync/skills/commit-push-pr/SKILL.md
commit-push-pr
Commit current changes, push to remote, and create or update a pull request. Use when the user wants to commit and create a PR, push changes and open a pull request, or ship their current work as a PR.
- Source repository stars
- 1,263
- Declared platforms
- 0
- Static risk flags
- 1
- Last source update
- 2026-07-28
- Source checked
- 2026-07-28
Decision brief
What it does—and where it fits
Commit current changes, push to remote, and create or update a pull request.
Not for
- Tasks that require unconfirmed production actions or broad system permissions.
- Environments where the pinned source and install steps cannot be inspected.
Compatibility matrix
Platform support, with evidence labels
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
Inspect first. Install second.
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
Source-detected install commandSource
npx skills add https://github.com/dyoshikawa/rulesync --skill ".rulesync/skills/commit-push-pr"Safe inspection promptEditorial
Inspect the Agent Skill "commit-push-pr" from https://github.com/dyoshikawa/rulesync/blob/310b711fbe8cffc14debb276ade8a384c2b89083/.rulesync/skills/commit-push-pr/SKILL.md at commit 310b711fbe8cffc14debb276ade8a384c2b89083. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
What the source asks the agent to do
- 01
Step 1: Check Current Branch
Run git branch --show-current to get the current branch name.
Generate a descriptive branch name based on the staged/unstaged changesCreate and switch to the new branch: git checkout -bRun git branch --show-current to get the current branch name. - 02
Step 2: Stage and Commit Changes
1. Run git status to check for changes 2. If there are unstaged changes, stage them: git add . 3. Analyze the changes and create a meaningful commit message 4. Commit with: git commit -m ""
Run git status to check for changesIf there are unstaged changes, stage them: git add .Analyze the changes and create a meaningful commit message - 03
Step 3: Push to Remote
Push the branch to remote with upstream tracking:
Push the branch to remote with upstream tracking: - 04
Step 4: Handle Pull Request
Check if a PR already exists for this branch:
Summary of changesTest plan (if applicable)Compare the current PR title and description with the actual changes
Permission review
Static risk signals and limitations
Runs scripts
The documentation asks the agent to run terminal commands or scripts.
git push -u origin <branch-name>Evidence record
Why each signal appears
EvidenceSourceComputedTestedEditorial
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 80/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 1,263 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Provenance and original SKILL.md
- Repository
- dyoshikawa/rulesync
- Skill path
- .rulesync/skills/commit-push-pr/SKILL.md
- Commit
- 310b711fbe8cffc14debb276ade8a384c2b89083
- License
- MIT
- Collected
- 2026-07-28
- Default branch
- main
View the original SKILL.md
Commit, Push, and PR Management
Step 1: Check Current Branch
Run git branch --show-current to get the current branch name.
If the current branch is main or master:
- Generate a descriptive branch name based on the staged/unstaged changes
- Create and switch to the new branch:
git checkout -b <new-branch-name>
Step 2: Stage and Commit Changes
- Run
git statusto check for changes - If there are unstaged changes, stage them:
git add . - Analyze the changes and create a meaningful commit message
- Commit with:
git commit -m "<commit-message>"
Step 3: Push to Remote
Push the branch to remote with upstream tracking:
git push -u origin <branch-name>
Step 4: Handle Pull Request
Check if a PR already exists for this branch:
gh pr view --json number,title,body 2>/dev/null
If PR does NOT exist:
Create a new PR:
gh pr create --title "<title>" --body "<description>"
The PR description should include:
- Summary of changes
- Test plan (if applicable)
If PR already exists:
- Compare the current PR title and description with the actual changes
- If updates are needed (e.g., scope of changes has expanded), update the PR using GitHub API:
gh api repos/<owner>/<repo>/pulls/<pr-number> -X PATCH -f title="<new-title>" -f body="<new-description>"
Note: Use gh api instead of gh pr edit to avoid GraphQL deprecation warnings. 3. If no updates are needed, skip this step
Step 5: Report Result
Output the PR URL and a summary of actions taken.
Alternatives
Compare before choosing
Computed 8610,762
Jeffallan/claude-skills
code-reviewer
Analyzes code diffs and files to identify bugs, security vulnerabilities (SQL injection, XSS, insecure deserialization), code smells, N+1 queries, naming issues, and architectural concerns, then produces a structured review report with prioritized, actionable feedback. Use when reviewing pull requests, conducting code quality audits, identifying refactoring opportunities, or checking for security issues. Invoke for PR reviews, code quality checks, refactoring suggestions, review code, code quali
Computed 85234,327
affaan-m/ECC
dmux-workflows
Multi-agent orchestration using dmux (tmux pane manager for AI agents). Patterns for parallel agent workflows across Claude Code, Codex, OpenCode, and other harnesses. Use when running multiple agent sessions in parallel or coordinating multi-agent development workflows.
Computed 84933
dpearson2699/swift-ios-skills
swiftui-performance
Profile, diagnose, and remediate SwiftUI runtime performance using code review, Instruments, and repeatable measurements. Use when a SwiftUI screen renders slowly, scrolling or animations hitch, view bodies update excessively, list identity churns, layout work spikes, or broad Observation dependencies raise CPU cost. Covers evidence-based triage, SwiftUI Instruments lanes, lazy-container guardrails, state lifetime, and before/after verification.
Computed 83234,327
affaan-m/ECC
dmux-workflows
Multi-agent orchestration using dmux (tmux pane manager for AI agents). Patterns for parallel agent workflows across Claude Code, Codex, OpenCode, and other harnesses. Use when running multiple agent sessions in parallel or coordinating multi-agent development workflows.