用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/dyoshikawa/rulesync --skill merge-pr命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
Clear the open issue backlog and then cut a release, in one autonomous run: use the `batch-all-issues` skill to resolve every open issue, then the `goal-release` skill to draft, merge, and see the release through publication. Never asks the user anything — every decision is made autonomously, and blockers are reported at the end instead of interrupting the run.
Maps rulesync feature implementations to upstream coding-agent documentation. Use when evaluating rulesync issues, comparing any coding-agent client with rulesync source capability surfaces, checking support, or planning a client map.
Research recent upstream releases of every rulesync target tool, detect capabilities rulesync has not yet followed, file one GitHub issue per tool for the gaps, and scout popular or promising coding agents rulesync does not target yet.
基于 SOC 职业分类
正在显示 SKILL.md
| name | merge-pr |
| description | Merge a pull request using gh pr merge --admin |
| targets | ["*"] |
Merge a pull request using gh pr merge --admin.
the user's request
Parse the user's request to identify the PR to merge:
123, #123, https://github.com/owner/repo/pull/123gh pr view --json number,title,state
If the PR cannot be determined (e.g., no PR exists for the current branch, or the argument is ambiguous), ask the user to specify which PR to merge.
Before merging, confirm the PR details:
gh pr view <pr_number> --json number,title,state,mergeable,author,baseRefName,headRefName
Check:
OPENIf the PR is not open or not mergeable, inform the user and stop.
Verify that all CI checks have passed before merging:
gh pr checks <pr_number>
Check:
pass statuspending or failIf any checks have failed or are still running, inform the user and ask whether to:
--admin will bypass required checks)Execute the merge command:
gh pr merge <pr_number> --admin --merge
Important: Only merge ONE PR at a time. If multiple PRs are somehow specified, ask the user which single PR to merge.
After the merge succeeds, leave a thank-you comment mentioning the PR author:
gh pr comment <pr_number> --body "@<author_login> Thank you!"
Use the author.login value obtained in Step 2 for the mention.
After merging:
If the local branch exists, please clean up the local branch. Execute:
git checkout main && git pull --prune && git branch -d <branch-name>
Where <branch-name> is the head branch name from Step 2 (e.g., fix/rulesync-import-targets).