Agent skill

gh-create-pr

Create or update GitHub pull requests using the repository-required workflow and template compliance. Use when asked to create/open/update a PR so the assistant reads `.github/pull_request_template.md`, fills every template section, preserves markdown structure exactly, and marks missing data as N/A or None instead of skipping sections.

View SKILL.md on GitHub Repository
Stars 43,310
Forks 4,066

Install this agent skill to your Project

npx add-skill https://github.com/CherryHQ/cherry-studio/tree/main/.agents/skills/gh-create-pr

SKILL.md

GitHub PR Creation

Workflow

  1. Read .github/pull_request_template.md before drafting the PR body.
  2. Collect PR context from the current branch (base/head, scope, linked issues, testing status, breaking changes, release note content).
  3. Check if the current branch has been pushed to remote. If not, push it first:
    • Default remote is origin, but ask the user if they want to use a different remote.
    bash
    git push -u <remote> <head-branch>
  4. Determine the base branch:
    • For official repo(CherryHQ/cherry-studio) as origin: default base is main from origin, but allow the user to explicitly indicate a base branch.
    • For fork repo as origin: check available remotes with git remote -v, default base may be upstream/main or another remote. Always assume that user wants to merge head to CherryHQ/cherry-studio/main, unless the user explicitly indicates a base branch.
    • Ask the user to confirm the base branch if it's not the default.
  5. Create a temp file and write the PR body:
    • Use pr_body_file="$(mktemp /tmp/gh-pr-body-XXXXXX).md"
    • Fill content using the template structure exactly (keep section order, headings, checkbox formatting).
    • If not applicable, write N/A or None.
  6. Preview the temp file content. Show the file path (e.g., /tmp/gh-pr-body-XXXXXX.md) and ask for explicit confirmation before creating. Skip this step if the user explicitly indicates no preview/confirmation is needed (for example, automation workflows).
  7. After confirmation, create the PR:
    bash
    gh pr create --base <base> --head <head> --title "<title>" --body-file "$pr_body_file"
  8. Clean up the temp file: rm -f "$pr_body_file"
  9. Report the created PR URL and summarize title/base/head and any required follow-up.

Constraints

  • Never skip template sections.

  • Never rewrite the template format.

  • Keep content concise and specific to the current change set.

  • PR title and body must be written in English.

  • Never create the PR before showing the full final body to the user, unless they explicitly waive the preview or confirmation.

  • Never rely on command permission prompts as PR body preview.

  • Release note & Documentation checkbox — both are driven by whether the change is user-facing. Use the table below:

    Change type Release note Docs [x]
    New user-facing feature / setting / UI Describe the change ✅
    Bug fix visible to users Describe the fix ✅ if behavior changed
    Behavior change / default value change Describe + action required ✅
    Security fix in a user-facing dependency Describe the fix ✅ if usage changed
    CI / GitHub Actions changes NONE ❌
    Internal refactoring (user cannot tell) NONE ❌
    Dev / build tooling changes NONE ❌
    Dev-only dependency bump NONE ❌
    Test-only / code style changes NONE ❌

Command Pattern

bash
# read template
cat .github/pull_request_template.md

# show this full Markdown body in chat first
pr_body_file="$(mktemp /tmp/gh-pr-body-XXXXXX).md"
cat > "$pr_body_file" <<'EOF'
...filled template body...
EOF

# run only after explicit user confirmation
gh pr create --base <base> --head <head> --title "<title>" --body-file "$pr_body_file"
rm -f "$pr_body_file"

Recommended Agent Skills

Expand your agent's capabilities with these related and highly-rated skills.

CherryHQ/cherry-studio

vercel-react-best-practices

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

43,310 4,066
Explore
CherryHQ/cherry-studio

create-skill

Create a new skill in the current repository. Use when the user wants to create/add a new skill, or mentions creating a skill from scratch. This skill follows the workflow defined in .agents/skills/README.md and helps scaffold, validate, and sync new skills.

43,310 4,066
Explore
CherryHQ/cherry-studio

cherry-pr-test

Test Cherry Studio PRs by checking out the branch, launching the Electron app in debug mode, and running interactive UI tests via CDP.

43,310 4,066
Explore
CherryHQ/cherry-studio

gh-create-issue

Use when user wants to create a GitHub issue for the current repository. Must read and follow the repository's issue template format.

43,310 4,066
Explore
CherryHQ/cherry-studio

gh-pr-review

Automated code review for local branches, PRs, commits, and files. Supports single-agent review with interactive fix selection, or multi-agent deep review with reviewer-verifier adversarial mechanism and risk-based auto-fix.

43,310 4,066
Explore
CherryHQ/cherry-studio

prepare-release

Prepare a new release by collecting commits, generating bilingual release notes, updating version files, and creating a release branch with PR. Use when asked to prepare/create a release, bump version, or run `/prepare-release`.

43,310 4,066
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results