commit-and-pr

Original：🇨🇳 Chinese

Translated

Commit changes and create a GitHub Pull Request. Used for requests such as "Commit and create a PR", "Commit my current work and create a pull request", "Push changes and create a PR". Handles a series of workflows including staging, commit message generation, branch creation, pushing, and PR creation. The PR body is written in Japanese.

1installs

Sourcenimiusrd/agent-skills

Added on2026-02-20

NPX Install

npx skill4agent add nimiusrd/agent-skills commit-and-pr

SKILL.md Content (Chinese)

View Translation Comparison →

Commit and PR

Execute the git commit → push → PR creation workflow in one go.

Workflow

1. Check Current Status

Execute the following in parallel:

bash

git status          # Check untracked and changed files
git diff HEAD       # Check all differences
git log --oneline -5  # Understand recent commit styles
git branch -r       # Check for existence of remote branches

2. Branch Strategy

When on a feature branch (other than
```
main
```
/
```
master
```
): use it as is.
When on
```
main
```
/
```
master
```
: create a new branch. Derive the branch name from the changes (e.g.,
```
feat/add-login
```
,
```
fix/null-pointer
```
).

bash

git checkout -b <branch-name>

3. Staging

Prioritize specifying specific files over

git add -A

. Never include the following:

.env files, secrets, authentication information
Untracked large binaries
Build artifacts listed in
```
.gitignore
```

bash

git add <file1> <file2> ...

If all changed files are safe,

git add -A

can be used.

4. Create Commit

Analyze all changes and create a concise commit message (1-2 sentences, imperative mood, focus on why not what). Pass it via heredoc:

bash

git commit -m "$(cat <<'EOF'
<Summary line>

<Additional context (optional)>

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
EOF
)"

If the pre-commit hook fails: fix the issue, restage, and create a new commit (amending is prohibited).

5. Push → Create PR

bash

git push -u origin <branch-name>

Create a PR (the body is written in Japanese). To ensure line breaks are not escaped as

\n

, always pass it via a temporary file:

bash

cat > /tmp/pr_body.md << 'EOF'
## Background/Motivation
<Context on why this change was necessary>

## Overview
- <Change 1>
- <Change 2>

## Review Points
- <Specific areas to review or concerns>

## Test Procedures
- [ ] <Only items that cannot be automatically checked by CI and require manual verification>

🤖 Generated with [Claude Code](https://claude.com/claude-code)
EOF

gh pr create --title "<Concise title (within 70 characters)>" --body-file /tmp/pr_body.md

Directly passing a string to

--body "..."

may cause

\n

to remain escaped, so use

--body-file

instead.

Return the PR URL to the user.

Safety Rules

Force pushing to
```
main
```
/
```
master
```
is prohibited.
Do not use
```
--no-verify
```
unless explicitly requested by the user.
Do not amend pushed commits.
Confirm with the user before pushing to shared/protected branches.
Do not commit if there are no changes (when
```
git status
```
is clean).

commit-and-pr

NPX Install

Tags

SKILL.md Content (Chinese)

Commit and PR

Workflow

1. Check Current Status

2. Branch Strategy

3. Staging

4. Create Commit

5. Push → Create PR

Safety Rules