- name
SKILL.md
O arquivo da skill permanece no repositório do publicador.
Cole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add CherryHQ/cherry-studio --skill gh-create-pr -a cursor -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add CherryHQ/cherry-studio --skill gh-create-pr -a claude-code -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add CherryHQ/cherry-studio --skill gh-create-pr -a codex -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add CherryHQ/cherry-studio --skill gh-create-pr -a grok -yEnvie a mensagem copiada em um chat do Grok Bot. O Bot busca este SKILL.md no GitHub e o adiciona às skills que todos os seus Bots compartilham.
Install this skill: https://github.com/CherryHQ/cherry-studio/tree/HEAD/.agents/skills/gh-create-prDo publicador
This repository ships .agents/skills/gh-stack/SKILL.md as a public project skill; developers do not install the agent skill separately. Read it before operating on stacked branches or PRs. Agents that consume .agents/skills/ discover it directly. If a Claude checkout is missing .claude/skills/gh-stack, run pnpm skills:sync followed by pnpm skills:check; do not download a separate global copy.
Before the first gh stack command in a task, verify the GitHub CLI and install the official extension if it is missing:
command -v gh >/dev/null 2>&1 || {
echo "GitHub CLI is required: https://cli.github.com/" >&2
exit 1
}
gh auth status
if ! gh stack --help >/dev/null 2>&1; then
gh extension install github/gh-stack
fi
gh stack --help >/dev/null
Stop if authentication, installation, or the final verification fails. Do not infer a stack with ad hoc Git commands. For human-authored Cherry PRs, use gh stack push, create each compliant PR through this skill from bottom to top, then link the existing PRs with gh stack link; gh stack submit --auto creates PRs outside the template-compliant body flow and must not bypass this workflow.
.github/pull_request_template.md before drafting the PR body.pnpm change:scope --base <verified-base-ref>; do not infer scope from the latest commit alone..agents/notes/README.md and classify the change:
Agent Note with the repository path, or N/A — <reason> for a local/mechanical change.Spec PR: This PR and list every AC.APPROVED review whose commit_id equals the current Spec head; a stale approval does not authorize implementation.bug-fix note and use Spec PR: N/A.gh stack view --json. If it exits 2, follow the gh-stack skill's remote-discovery procedure; missing local metadata does not prove the PR is standalone. Inspect every downstack implementation PR and aggregate only ACs backed by actual verification. Keep the note proposed on intermediate layers. If the current PR is the final layer and cumulative evidence covers the complete approved Spec, move the bilingual triplet to implemented/ and run pnpm agent-notes:check-transition --base <verified-spec-ref> before publishing.Verification with commands and scenarios actually run. Never present a planned, pending, skipped, or CI-only check as passed.origin, but ask the user if they want to use a different remote.git push -u <remote> <head-branch>
release/v<version>, stop: never open a pull request from a release branch, especially not to main. Put an isolated fix on a topic branch and target the release branch, or let Post Release create the metadata sync branch.main, inspect its merge base and upstream. A product-code fix that started from release/v<version> must stop and be recreated from main as a hotfix; only a release-only repair or explicit backport recovery topic may target that exact release branch.backport/v<version>/pr-<number> head must target the matching release/v<version> base and its body must contain `` on its own line for the exact source hotfix PR. A release-sync/v<version> head must target main, use the exact title chore(release): sync v<version> metadata, retain the release-metadata-boundary: v<version> body marker, and be squash-merged.origin: default base is main from origin, but allow the user to explicitly indicate a base branch.main is the active development line, including hotfix PRs. Do not target an old maintenance branch unless the user explicitly requests it.hotfix: <description> or hotfix(<kebab-case-scope>): <description> with a lowercase alphanumeric kebab-case scope, exactly one space after the colon, and a non-empty description. The title grammar synchronizes the hotfix label automatically. Merging opens a separate backport PR only when exactly one draft semantic-version release has a matching active release/v<version> branch; otherwise automation stops without guessing a target.release-note fence; do not include bullet prefixes:
[Component] English description.
[组件] 中文说明。
NONE in the template's release-note fence. The code is still backported, but release metadata is unchanged. A provided bilingual block must satisfy the exact structure above.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.cat "$pr_body_file" (the Read
tool can fail on /tmp/... paths on Windows). If the user requests a preview
or confirmation, show the full body and follow that request; otherwise,
proceed with the authorized PR creation.--draft when the user requests a draft:gh pr create --base <base> --head <head> --title "<title>" --body-file "$pr_body_file"
For a release hotfix, use an exact classifier-compatible title so the workflow synchronizes the label and separately validates any provided bilingual note:
gh pr create --base main --head <head> --title "hotfix: <description>" --body-file "$pr_body_file"
After creation, verify that the classifier added hotfix; if it did not, fix the title instead of adding the label manually. Also fix any malformed optional release-note block reported by the workflow.
11. Clean up the temp file: rm -f "$pr_body_file"
12. Report the created PR URL and summarize title/base/head, Agent Note/Spec, AC coverage, actual verification, and any required follow-up.
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 use a hotfix title or label for an ordinary bug fix. It opts the PR into an automatic backport PR after merge when one matching draft release is active.
A release hotfix may use NONE when it has no user-facing release note. Never provide a partial, single-language, or otherwise malformed bilingual note; the backport workflow fails closed on malformed content.
Never default a release/v<version> head to main; a release branch is not a pull request source branch.
Never publish an implementation PR as ready when its current Spec head lacks an exact-head Approval. A Spec may remain unmerged and serve as the stack base.
Every human-authored PR fills Agent Note, Spec PR, and Acceptance criteria; N/A requires a concise reason. Automation-authored PRs (repository workflows and Dependabot) are exempt from this metadata requirement.
Release note & Documentation checkbox — both are driven by whether the change is user-facing. Use the table below:
# read template
cat .github/pull_request_template.md
# prepare and inspect the PR body
pr_body_file="/tmp/gh-pr-body-$(date +%s).md"
cat > "$pr_body_file" <<'EOF'
...filled template body...
EOF
cat "$pr_body_file"
# create the authorized PR; add --draft when requested
gh pr create --base <base> --head <head> --title "<title>" --body-file "$pr_body_file"
rm -f "$pr_body_file"
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
---name: gh-create-prdescription: Create or update GitHub pull requests using the repository-required workflow and template compliance. Use when…---# .agents/skills/gh-create-pr/SKILL.mdVisão geral
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.
Perguntas frequentes
Baixe .agents/skills/gh-create-pr/SKILL.md do publicador ou copie o caminho e abra o repositório. O PlugMCP lista a skill e não hospeda o arquivo.
O publicador o mantém em https://github.com/CherryHQ/cherry-studio.
Claude, Cursor, Codex e Grok Build conseguem ler um SKILL.md que você adiciona a partir do repositório do publicador. O Grok Bot o instala quando você envia em um chat o link da pasta da skill no GitHub.
origingit remote -vupstream/mainNONE |
| ❌ |
| Test-only / code style changes | NONE | ❌ |