Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

GitHub PR Creation — measured AI agent skill | DecimalAI

cherryhq/gh-create-pr

SkillScore59Maintained

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.

by cherryhq

Links this skill to your agents and keeps it current with the author’s updates.

Automatic

Coding pack

decimalai skills pull cherryhq-gh-create-pr

Get this skill — curl · raw file

curl -fsSL https://app.decimal.ai/s/cherryhq-gh-create-pr/SKILL.md

Raw file: /s/cherryhq-gh-create-pr/SKILL.md ↗ · machine-readable summary at /s/cherryhq-gh-create-pr.json ↗

In productionGlobal

how this skill behaves on real traffic · last 30 days

No production data for this skill yet — usage numbers appear here once agents start running it.

Anonymized aggregate across every org using this skill — proof from real production use, not a demo.

Does this skill help? · Benchmark: with vs. withoutsign in to run this on your agents

22 test cases from the publisher’s eval.yaml · each run twice on gemini-3.6-flash — with the skill injected, then without · last run 3d ago

—+12% tokens0% turns59% of whole cases pass with skill (13/22)

Test case	Without → With	Effect	Δ tokens	Δ turns
case-08	✗→✓	▲ Improved	-6%	0%
case-11	✗→✓	▲ Improved	-17%	0%
case-19	✗→✓	▲ Improved	-21%	0%
case-21	✗→✓	▲ Improved	23%	0%
case-05	✓→✗	▼ Worse	-17%	0%

Showing 5 of 22 cases

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v4 — 8/3/2026

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

cherryhq / cherry-studio

.agents/skills/gh-create-pr/SKILL.md

View on GitHub ↗

License AGPL-3.0Imported 8/3/2026Version v1

Skill contents

SKILL.md

GitHub PR Creation

Workflow

Read .github/pull_request_template.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:

Default remote is origin, but ask the user if they want to use a different remote.

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

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.

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

(avoids mktemp + Write tool path-mismatch on Windows): bash 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.

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).

After confirmation, create the PR:

bash gh pr create --base <base> --head <head> --title "<title>" --body-file "$pr_body_file"

Clean up the temp file: rm -f "$pr_body_file"
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="/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"

Want to see if cherryhq/gh-create-pr would activate on your phrasing? Try it before you install — no LLM call, no signup.

Other measured skills in the registry, with their headline benchmark lift.