Claude-skill-registry github-pr-flow

manage branches and full pull request lifecycle, from creation to merge

install

source · Clone the upstream repo

git clone https://github.com/majiayu000/claude-skill-registry

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/github-pr-flow" ~/.claude/skills/majiayu000-claude-skill-registry-github-pr-flow && rm -rf "$T"

manifest: skills/data/github-pr-flow/SKILL.md

What is it?

The PR Flow Skill handles the logistics of code contribution: creating branches, opening Pull Requests, synchronizing branches, and merging.

Success Criteria

Branch exists before PR creation.
PR titles follow Conventional Commits.
PR description clearly states the changes.
Syncing (updating) branches is performed when conflicts occur or before merge.
Merges are performed only after approvals and passing checks.

When to use this skill

"Create a new branch for feature X."
"Open a PR for my current changes."
"Update this PR branch with the latest main."
"Merge PR #50."

What this skill can do

Branch Management: Create feature branches from specific bases.
PR Creation: Open Draft or Ready-for-review PRs.
Maintenance: Update PR branches (sync with base) using
```
update_pull_request_branch
```
.
Conclusion: Merge PRs (squash, merge, rebase).

What this skill will NOT do

Review code (use
```
github-review-cycle
```
).
Modify file contents (use
```
github-kernel
```
tools like
```
create_or_update_file
```
).
Run CI/CD checks (it only views status).

How to use this skill

Branch: Always start by ensuring a branch exists (
```
create_branch
```
).
Commit: (Performed via file editing tools, not this skill).
PR: Create the PR (
```
create_pull_request
```
).
Sync: If CI fails due to conflicts or age, use
```
update_pull_request_branch
```
.
Merge: When approved and green, use
```
merge_pull_request
```
.

Tool usage rules

Conventions: PR Titles should follow Conventional Commits (e.g.,
```
feat: new login flow
```
).
Creation:
```
create_branch
```
->
```
create_pull_request
```
.

Updates:

update_pull_request

(metadata) or

update_pull_request_branch

(git sync).

Merge:
```
merge_pull_request
```
(Prefer
```
squash
```
for features,
```
merge
```
for long-lived branches).

Examples

See references/examples.md for compliant PR flow examples.

Limitations

Cannot resolve merge conflicts automatically (requires manual or file-edit intervention).
Cannot bypass branch protection rules.