How do I install the Commit Push Pr skill?

Run npx skillmds add majiayu000/commit-push-pr in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Commit Push Pr skill do?

Validate code, commit, push, and create PR if needed It is listed under Coding & Dev Tools on SkillMD.

Is Commit Push Pr safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Commit Push Pr?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Commit Push Pr free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Commit Push Pr?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Commit Push Pr by majiayu000 — Agent Skill

Name: Commit Push Pr
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

Validated Commit, Push, and PR

This skill ensures code quality, commits, pushes, and creates a PR if one doesn't exist.

Process

Step 1: Run Formatting Check

cd backend && cargo fmt --check

If this fails, run cargo fmt to auto-fix, then re-check.

Step 2: Run Clippy Lints

cd backend && cargo clippy --workspace --all-targets --all-features -- -D warnings

If clippy fails, fix the issues before proceeding. Do NOT commit code with clippy warnings.

Step 3: Run Tests

cd backend && cargo test --workspace

If tests fail, fix the failing tests before proceeding. Do NOT commit code with failing tests.

Step 4: Check for Changes

git status

Review what will be committed. If there are no changes to commit, skip to Step 8 (PR creation).

Step 5: Stage Changes

git add -A

Step 6: Create Commit

Ask the user for a commit message, or generate one based on the changes.

IMPORTANT: Never include:

"Generated with Claude Code"
"Co-Authored-By: Claude"
Any AI/Claude attribution

Step 7: Push to Remote

git push origin HEAD

If push fails due to upstream changes:

git pull --rebase origin HEAD && git push origin HEAD

Step 8: Check for Existing PR

gh pr list --head $(git branch --show-current) --state open

If a PR already exists for this branch, inform the user and provide the PR URL. Done.

Step 9: Create PR (if none exists)

Get the current branch and base branch:

CURRENT_BRANCH=$(git branch --show-current)

Create the PR:

gh pr create --title "PR title here" --body "$(cat <<'EOF'
## Summary
- Brief description of changes

## Test plan
- [ ] Tests pass
- [ ] Lints pass

EOF
)"

PR Title: Generate from the commit message or ask user.

PR Body: Include:

Summary of changes (2-3 bullet points)
Test plan checklist

Do NOT include "Generated with Claude Code" or similar.

Step 10: Report Success

Provide the PR URL to the user.

Failure Handling

If ANY step fails (fmt, clippy, or tests):

Stop immediately
Report the failure to the user
Do NOT proceed to commit
Help fix the issues if requested

Quick Reference

# Full validation
cd backend && cargo fmt --check && cargo clippy --workspace --all-targets --all-features -- -D warnings && cargo test --workspace

# Check for existing PR
gh pr list --head $(git branch --show-current) --state open

# Create PR
gh pr create --title "Title" --body "Body"

---name: commit-push-prdescription: Validate code, commit, push, and create PR if needed--- # Validated Commit, Push, and PR This skill ensures code quality, commits, pushes, and creates a PR if one doesn't exist. ## Process ### Step 1: Run Formatting Check ```bash cd backend && cargo fmt --check ``` If this fails, run `cargo fmt` to auto-fix, then re-check. ### Step 2: Run Clippy Lints ```bash cd backend && cargo clippy --workspace --all-targets --all-features -- -D warnings ``` If clippy fails, fix the issues before proceeding. Do NOT commit code with clippy warnings. ### Step 3: Run Tests ```bash cd backend && cargo test --workspace ``` If tests fail, fix the failing tests before proceeding. Do NOT commit code with failing tests. ### Step 4: Check for Changes ```bash git status ``` Review what will be committed. If there are no changes to commit, skip to Step 8 (PR creation). ### Step 5: Stage Changes ```bash git add -A ``` ### Step 6: Create Commit Ask the user for a commit message, or generate one based on the changes. **IMPORTANT**: Never include: - "Generated with Claude Code" - "Co-Authored-By: Claude" - Any AI/Claude attribution ### Step 7: Push to Remote ```bash git push origin HEAD ``` If push fails due to upstream changes: ```bash git pull --rebase origin HEAD && git push origin HEAD ``` ### Step 8: Check for Existing PR ```bash gh pr list --head $(git branch --show-current) --state open ``` If a PR already exists for this branch, inform the user and provide the PR URL. Done. ### Step 9: Create PR (if none exists) Get the current branch and base branch: ```bash CURRENT_BRANCH=$(git branch --show-current) ``` Create the PR: ```bash gh pr create --title "PR title here" --body "$(cat <<'EOF' ## Summary - Brief description of changes ## Test plan - [ ] Tests pass - [ ] Lints pass EOF )" ``` **PR Title**: Generate from the commit message or ask user. **PR Body**: Include: - Summary of changes (2-3 bullet points) - Test plan checklist Do NOT include "Generated with Claude Code" or similar. ### Step 10: Report Success Provide the PR URL to the user. ## Failure Handling If ANY step fails (fmt, clippy, or tests): 1. Stop immediately 2. Report the failure to the user 3. Do NOT proceed to commit 4. Help fix the issues if requested ## Quick Reference ```bash # Full validation cd backend && cargo fmt --check && cargo clippy --workspace --all-targets --all-features -- -D warnings && cargo test --workspace # Check for existing PR gh pr list --head $(git branch --show-current) --state open # Create PR gh pr create --title "Title" --body "Body" ```

Frequently asked questions