Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add zhuanggenhua/BoardGame --skill merge-pr-workflowgit clone --depth 1 https://github.com/zhuanggenhua/BoardGameWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/zhuanggenhua/boardgame/merge-pr-workflow)<a href="https://agentmods.dev/skills/zhuanggenhua/boardgame/merge-pr-workflow"><img src="https://agentmods.dev/badge/skills/zhuanggenhua/boardgame/merge-pr-workflow/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/zhuanggenhua/boardgame/merge-pr-workflow"><img src="https://agentmods.dev/badge/skills/zhuanggenhua/boardgame/merge-pr-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 60 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 61 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00034 | $0.01170 |
| Opus 5 | $0.00017 | $0.00585 |
| Sonnet 5 | $0.00007 | $0.00234 |
| Haiku 4.5 | $0.00003 | $0.00117 |
Grade A, and why
merge-pr-workflow scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR 合并工作流
职责边界
- 本 skill 是 PR / 分支合并的执行入口。
- 日常提交、推送、pre-push 阻塞和普通 Git 操作走
git-operations。 - 分支 / worktree 目标锁定以上位标准
worktree-branch-target-lock为准。 - 用户需要判断“保留哪边 / 是否都保留”时，转
merge-decision-package；本 skill 不复制用户决策包。 - 合并命令、统计阈值、冲突裁决和审计细节只维护在
references/git-merge-checklist.md。
开始前
先锁定：
- 目标 PR / 分支。
- 目标基线分支和当前所在工作区。
- 当前工作树是否干净，是否存在合并中状态。
- 是否已获得创建 / 切换 / 删除分支或 worktree 的明确授权。
- 当前身份是否能 push 到目标远端；跨仓库 PR 不得只凭页面字段推断权限。
前提未锁定时，只能读取、统计和汇报，不得开始合并、切分支、创建 worktree 或 push。
默认目标
- 用户给出 PR 号 / 分支名：只处理该 PR。
- 用户未指定：默认扫描
pr-*未合并分支，按编号升序处理。 - 默认合并到当前分支；需要切到
main或其它分支时，先说明目标、影响和脏工作区风险，等用户明确授权。
主工作区不干净时，优先复用当前已授权、已存在且目标匹配的合并 worktree；没有可用现场时，向用户请求创建隔离 worktree / 清理当前工作区 / 暂停的明确授权。
合并顺序
- 读
references/git-merge-checklist.md。 - 执行预检查：共同祖先、真实删除、旧分支漂移、冲突预测、权限和停止阈值。
- 阈值未触发且权限已锁定后，执行
git fetch --all --prune和git merge <branch> --no-commit --no-ff。 - 有冲突时逐文件、逐块裁决；不得整份接受 ours / theirs 替代语义判断。
- 冲突解决后写
evidence/merge-conflict-<pr-or-branch>-<YYYY-MM-DD>.md。 - 运行合并审计：
npm run merge:audit -- HEAD与npm run merge:audit:strict -- HEAD。 - 按改动范围运行验证：类型、lint、相关测试、E2E、spec lint、资源发布与远端回查。
- push 后关闭或确认 PR 状态；PR 未关闭时不得说合并完成。
关键裁决
git diff main...branch显示的删除不等于 PR 作者删除；必须先看共同祖先到 PR head 的真实改动。- 旧分支缺少主线后来新增的测试、规范、证据和资源时，默认保留主线内容。
- 共享文件大范围差异时，从最新主线出发，只提取 PR 从共同祖先以来真实新增或有意修改的块。
- 游戏规则、公开信息、交互权限、结算时机或资源发布冲突，必须回查规则源、OpenSpec、用户故事或 evidence；代码版本新旧不能单独裁决业务语义。
- 两边都可能有效且真相源不能裁定时，停止自动合并，转用户决策包。
验证口径
默认至少验证：
npx tsc --noEmit
npx eslint src/ --ext .ts,.tsx
追加规则：
- 规则 / 引擎 / 游戏逻辑：跑相关单测、集成测试或 E2E。
- 规范 / skill / knowledge：跑
npm run spec:lint并扫过期入口和第二套规范。 - 运行时资源：按
asset-pipeline发布和远端回查。 - 冲突合并：合并审计必须通过，且没有未解释的单边覆盖。
任一验证失败，只能称为“合并候选处理到某阶段”，不能宣告 PR 完成。
最终汇报
必须包含：
- 目标 PR / 分支和合并目标。
- 预检查结果：真实删除、旧分支漂移、权限和是否触发阈值。
- 冲突处理摘要和 evidence 路径。
- 合并审计结果。
- 验证命令与结果。
- push / PR close 真实结果。
- 仍阻塞的现实影响和最小补救动作。
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 84 lines · 34 tokens per session scan A 9e9f56a03ad5
merge-pr-workflow is a skill published in the GitHub repository zhuanggenhua/BoardGame (23 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 1,170 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…