How do I install the Github Pr Flow skill?

Run npx skillmds@latest add majiayu000/github-pr-flow 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 Github Pr Flow skill do?

manage branches and full pull request lifecycle, from creation to merge It is listed under Coding & Dev Tools on SkillMD.

Is Github Pr Flow safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Github Pr Flow?

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 Github Pr Flow free to use?

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

Who published Github Pr Flow?

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

Github Pr Flow by majiayu000 — Agent Skill

Name: Github Pr Flow
Rating: 4.5 (4 reviews)
Author: majiayu000

File contents

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.

---name: github-pr-flowdescription: manage branches and full pull request lifecycle, from creation to merge--- ## 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](../github-kernel/references/CONVENTIONAL_COMMITS.md). - 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 1. **Branch**: Always start by ensuring a branch exists (`create_branch`). 2. **Commit**: (Performed via file editing tools, not this skill). 3. **PR**: Create the PR (`create_pull_request`). 4. **Sync**: If CI fails due to conflicts or age, use `update_pull_request_branch`. 5. **Merge**: When approved and green, use `merge_pull_request`. ## Tool usage rules - **Conventions**: PR Titles should follow [Conventional Commits](../github-kernel/references/CONVENTIONAL_COMMITS.md) (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](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.

Frequently asked questions

Github Pr Flow