skillboardUpdated every 6 hours
skillboardCreate 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.
GitHub PR Creation Workflow 1. Read 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 , but ask the user if they want to use a different remote. 4. Determine the base branch: For official repo(CherryHQ/cherry studio) as : default base is from , but allow the user to explicitly…
Full body not shown for this license – view the source on GitHub →Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/gh-create-pr · pinned to the source commit
git clone https://github.com/CherryHQ/cherry-studio.git
cd cherry-studio
git checkout 18c287b020ff95cc2a12fc389ea4748957fbaf49
mkdir -p ".claude/skills/gh-create-pr"
cp -r ".agents/skills/gh-create-pr" ".claude/skills/gh-create-pr"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit 18c287b020ff. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.