Source profileQuality 73/100Review permissions

CherryHQ/cherry-studio/.agents/skills/gh-create-pr/SKILL.md

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.

Source repository stars
49,062
Declared platforms
0
Static risk flags
2
Last source update
2026-07-28
Source checked
2026-07-28
DecisionCompatibilityInstallWorkflowPermissionsEvidenceSource

Decision brief

What it does—and where it fits

Create or update GitHub pull requests using the repository-required workflow and template compliance. github/pull_request_template.

Best for

  • Use when asked to create/open/update a PR so the assistant reads `.

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/CherryHQ/cherry-studio --skill ".agents/skills/gh-create-pr"
Safe inspection promptEditorial

Inspect the Agent Skill "gh-create-pr" from https://github.com/CherryHQ/cherry-studio/blob/dda7cc99d730c36bde685bec586dafe458722a4d/.agents/skills/gh-create-pr/SKILL.md at commit dda7cc99d730c36bde685bec586dafe458722a4d. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    Workflow

    1. Read .github/pullrequesttemplate.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…

    Read .github/pullrequesttemplate.md before drafting the PR body.Collect PR context from the current branch (base/head, scope, linked issues, testing status, breaking changes, release note content).Check if the current branch has been pushed to remote. If not, push it first:
  2. 02

    Constraints

    Never skip template sections.

    Never skip template sections.Never rewrite the template format.Keep content concise and specific to the current change set.
  3. 03

    Command Pattern

    Review the “Command Pattern” section in the pinned source before continuing.

    Review and apply the “Command Pattern” source section.
  4. 04

    read template

    cat .github/pullrequesttemplate.md

    cat .github/pullrequesttemplate.md
  5. 05

    show this full Markdown body in chat first

    prbodyfile="/tmp/gh-pr-body-$(date +%s).md" cat "$prbodyfile" <<'EOF' ...filled template body... EOF cat "$prbodyfile"

    prbodyfile="/tmp/gh-pr-body-$(date +%s).md" cat "$prbodyfile" <<'EOF' ...filled template body... EOF cat "$prbodyfile"

Permission review

Static risk signals and limitations

Runs scripts

medium · line 10

The documentation asks the agent to run terminal commands or scripts.

git push -u <remote> <head-branch>

Writes files

medium · line 17

The documentation asks the agent to create, modify, or delete local files.

Create a temp file and write the PR body using a single Bash heredoc

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score73/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars49,062SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
CherryHQ/cherry-studio
Skill path
.agents/skills/gh-create-pr/SKILL.md
Commit
dda7cc99d730c36bde685bec586dafe458722a4d
License
AGPL-3.0
Collected
2026-07-28
Default branch
main
View the original 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.
    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.
    • main is the active v2 development line. v1 maintenance fixes (head branch hotfix/*, critical user-facing bug fixes only) must target v1, not main — set the base to v1 for these.
    • 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 using a single Bash heredoc (avoids mktemp + Write tool path-mismatch on Windows): 
    pr_body_file="/tmp/gh-pr-body-$(date +%s).md"
cat > "$pr_body_file" <<'EOF'
...filled template body...
EOF
    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 via Bash cat "$pr_body_file" (the Read tool can fail on /tmp/... paths on Windows). Show the file path and ask for explicit confirmation before creating. Skip if the user explicitly waives preview (automation workflows).
  7. After confirmation, create the PR: 
    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 typeRelease noteDocs [x]
    New user-facing feature / setting / UIDescribe the change✅
    Bug fix visible to usersDescribe the fix✅ if behavior changed
    Behavior change / default value changeDescribe + action required✅
    Security fix in a user-facing dependencyDescribe the fix✅ if usage changed
    CI / GitHub Actions changesNONE❌
    Internal refactoring (user cannot tell)NONE❌
    Dev / build tooling changesNONE❌
    Dev-only dependency bumpNONE❌
    Test-only / code style changesNONE❌

Command Pattern

# read template
cat .github/pull_request_template.md

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

# 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"

Alternatives

Compare before choosing

Computed 997

event4u-app/agent-config

design-review

Use when the user says "review the design", "check the UI", or wants a comprehensive UI/UX review. Uses a 7-phase methodology covering interaction, responsiveness, accessibility, and more.

2026-07-280 platforms
Computed 9831,966

K-Dense-AI/scientific-agent-skills

dask

Distributed computing for larger-than-RAM pandas/NumPy workflows. Use when you need to scale existing pandas/NumPy code beyond memory or across clusters. Best for parallel file processing, distributed ML, integration with existing pandas code. For out-of-core analytics on single machine use vaex; for in-memory speed use polars.

2026-07-280 platforms
Computed 9831,966

K-Dense-AI/scientific-agent-skills

medchem

Medicinal chemistry filters for compound triage. Apply drug-likeness rules (Lipinski, Veber, CNS), structural alert catalogs (PAINS, NIBR, ChEMBL), complexity metrics, and the medchem query language for library filtering.

2026-07-280 platforms
Computed 9831,966

K-Dense-AI/scientific-agent-skills

neurokit2

Use NeuroKit2 to build or audit reproducible research workflows for physiological time-series preprocessing, event/interval analysis, multimodal alignment, variability, and complexity. Trigger when code imports neurokit2 or needs its current APIs, schemas, and method-aware validation—not for diagnosis or device validation.

2026-07-280 platforms