A merge workflow for pull requests that waits for every required check to pass before merging. A pull request is a proposed code change reviewed before it is added to the main codebase.

Use it to merge a pull request or land a branch after its checks finish. It can start GitHub's automatic merge, report pending or failed checks, and clean up the local branch after merging.

It prevents changes from being merged while tests or other required checks are still running or failing. It also avoids bypassing safeguards or merging without knowing the result.

How SpillwaveSolutions/wiki_ticket_sdd configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to SpillwaveSolutions/wiki_ticket_sdd. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/SpillwaveSolutions/wiki_ticket_sdd/main/.claude/skills/merge-green/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/SpillwaveSolutions/wiki_ticket_sdd

Made for: Claude Code.

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

README.md

[![agentmods](https://agentmods.dev/badge/skills/spillwavesolutions/wiki_ticket_sdd/merge-green/github.svg)](https://agentmods.dev/skills/spillwavesolutions/wiki_ticket_sdd/merge-green)

Your own site

<a href="https://agentmods.dev/skills/spillwavesolutions/wiki_ticket_sdd/merge-green"><img src="https://agentmods.dev/badge/skills/spillwavesolutions/wiki_ticket_sdd/merge-green/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/spillwavesolutions/wiki_ticket_sdd/merge-green"><img src="https://agentmods.dev/badge/skills/spillwavesolutions/wiki_ticket_sdd/merge-green.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 562 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00049	$0.00562
Opus 5	$0.00024	$0.00281
Sonnet 5	$0.00010	$0.00112
Haiku 4.5	$0.00005	$0.00056

Measured 6d ago against content hash 9010518d50ce, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

merge-green 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 6d 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.

.claude/skills/merge-green/SKILL.md · 38 lines

What it actually says

Merge when green

The default, always: a PR merges only when every check is green. Pending means wait; failing means fix. There is no third option.

GitHub: run plugin/scripts/merge-when-green.sh <pr> [interval] [max] (defaults: 60 s × 120). The script arms gh pr merge --auto --merge up front so GitHub merges server-side the moment required checks pass; the poll loop is the fallback reporter, not the merge mechanism. Run it in the background so work continues. In this repo the script lives at plugin/scripts/; in plugin-installed sessions use "${CLAUDE_PLUGIN_ROOT}/scripts/merge-when-green.sh".
Other platforms: same rule via their CLI; prefer native merge-when-green (glab mr merge --when-pipeline-succeeds, ADO auto-complete).
After a merge: pull the base branch, delete the merged local branch. Roadmap/index regeneration and worklog sync --report run in CI on main (worklog-post-merge); do not wait on them locally. Ticket-sync on closed items can still run locally if the post-merge report is not enough.
On red gates: report which checks failed and fix them. Never merge with --admin, never skip a gate, never retry-until-flaky-passes without understanding the failure, never squash (ADR-0008).
Auto-merge flag: features.auto_merge_on_green in .work/config.yml (default true). False = advisory mode: the script polls, reports green, does NOT merge — a human runs gh pr merge <pr> --merge. Overrides, strongest first: --auto/--advisory as the script's first argument (one run), then WORKLOG_AUTO_MERGE=1|0, then the config. Red/pending/timeout behavior is unchanged either way.
For --auto to actually queue, the host repo must allow auto-merge and require status checks on the base branch (ADR-0010). Without those, GitHub rejects the arm and the poll loop merges once green.

Changes

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.

6d ago Changed 9010518d50ce
10d ago First seen · 38 lines · 49 tokens per session scan A 0c22517f98e0

Subscribe to this mod's changes

merge-green is a skill published in the GitHub repository SpillwaveSolutions/wiki_ticket_sdd (11 stars, last pushed 8d ago), licensed MIT. It adds 49 tokens to every session and 562 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-31.

Git and workflow

prowler-commit

Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.

prowler-cloud/prowler · 33 tokens

gh-auth-isolation

Safely manage multiple GitHub identities (EMU + personal) in agent workflows.

github/gh-aw · 20 tokens

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.

rpamis/comet · 72 tokens

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.

zeenie-ai/OpenCompany · 51 tokens

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…

LilMGenius/paperthin · 70 tokens

nvca-chart-release

Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.

NVIDIA/nvcf · 61 tokens

wiki_ticket_sdd: Skill for Claude Code