A release checklist for moving reviewed Fallow work onto the main branch and confirming that the merged code is healthy. It covers checks, commits, protected-branch merging, CI, generated files, and repository cleanup.

It is for shipping or merging approved work, rerunning quality gates, monitoring merged-commit CI, checking the final tree, and leaving local repositories synchronized and clean.

It reduces the risk of shipping unreviewed changes, missing companion files, unnoticed merge problems, or code whose required checks are still running.

How fallow-rs/fallow configures Claude Code and Codex

About the project

Fallow is a command-line static-analysis tool that builds a dependency graph of TypeScript and JavaScript code to identify unused code, duplication, circular dependencies, complexity hotspots, boundary violations, and styling drift. It is for developers reviewing codebases and verifying changes, with catalogue entries that add agent, editor, and workflow integrations.

fallow-rs/fallow · 5,139 stars · on GitHub · docs.fallow.tools

Reuse

Borrowing it

Nothing to install: this file belongs to fallow-rs/fallow. 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/fallow-rs/fallow/main/.agents/skills/ship/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/fallow-rs/fallow

Made for: Claude Code, Codex.

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/fallow-rs/fallow/ship/github.svg)](https://agentmods.dev/skills/fallow-rs/fallow/ship)

Your own site

<a href="https://agentmods.dev/skills/fallow-rs/fallow/ship"><img src="https://agentmods.dev/badge/skills/fallow-rs/fallow/ship/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/fallow-rs/fallow/ship"><img src="https://agentmods.dev/badge/skills/fallow-rs/fallow/ship.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 2,004 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.00042	$0.02004
Opus 5.5	$0.00017	$0.00802
Sonnet 5.5	$0.00008	$0.00401
Haiku 4.5	$0.00004	$0.00200

Measured today against content hash 0d30a826a20c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ship 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 today.

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.

.agents/skills/ship/SKILL.md · 145 lines

How it starts

The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Ship

Confirm the branch and diff exactly match the reviewed scope. To put the branch on the current base, run node scripts/ship-rebase.mjs --pr <number> --push, also for one pull request. Do not rebase by hand. The script compares the result with a merge and checks each version constant. A failed manual rebase --continue leaves commits on a detached HEAD.
Re-run the required checks from docs/development/quality-gates.md.
Verify that public contracts and generated files are pushed. Merge each companion change into the default branch of its repository (for example fallow-docs main). A pushed feature branch is not enough: the release then must merge it. When the merged change touches npm/fallow/skills, run node scripts/sync-skills-companion.mjs and push the fallow-skills commit that it prepares.
Create signed conventional commits only.
Merge through the repository's current protected-main workflow.
Monitor the merged commit until required CI completes. Use node scripts/ship-wait-checks.mjs --commit <full sha> --min-checks <count> --follow-main, with the run count of a recent push to main. A newer push to main cancels the runs of the merged commit. With --follow-main, the script then waits for the newest commit of origin/main that contains the merged commit, and prints one line for each move. On a busy main, new pushes can cancel each long run, and the wait can time out with pending runs. Then do not start the same wait again. For each workflow without a pass, watch its newest in-progress run on a commit that contains the merged commit (gh run watch <run id> --exit-status). Before you retry a failed job, confirm that the branch contains the current base (git merge-base --is-ancestor origin/main HEAD). A second identical failure is a defect, not a flake: diagnose it instead of a third retry.
Inspect the merged tree for conflict markers and generated drift. Then run git diff <reviewed head> <merge commit>. A pull request that merged after your last rebase shows there, also when it did not conflict. Read each hunk in a file that your pull request changed. Such a merge can make your code, a comment or a doc wrong without a text conflict. Fix that in a follow-up pull request.
Return every touched checkout to a clean, synchronized state.

Do not call work complete while required merged-commit workflows are still running.

Read the full file on GitHub · 145 lines

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.

today Changed · +17 lines 0d30a826a20c
yesterday Changed · +5 lines 16850a70403d
3d ago Changed · +5 lines bbb89c39d845
14d ago Changed · +16 lines dfa6c1abaa38
15d ago Changed · +7 lines a0ab9c5693e4
16d ago Changed · +2 lines 3d5342143976
17d ago Changed · +68 lines 3418f46d4dc4
19d ago Changed · +3 lines b04cbe0f51c1
23d ago Changed · +3 lines 706de2695bd4
1mo ago First seen · 19 lines · 42 tokens per session scan A 6459a67d1b01

Subscribe to this mod's changes

ship is a skill published in the GitHub repository fallow-rs/fallow (5,139 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 2,004 once invoked, about $0.0002 per session on Opus 5.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.

Git and workflow Releases cli code-quality dead-code developer-tools javascript oxc

cli-forge-github

Audit and fix GitHub repository health: rulesets vs CI alignment, branch hygiene, PR lifecycle, release automation flow, permission issues, and transient CI failures. Detects misconfigurations that cause PRs to hang, CI to fail silently, branches to accumulate, and releases to stall. Use when the user says 'PR stuck'…

Destynova2/cli-code-skills · 165 tokens

cli-git-conventional

Enforce Conventional Commits v1.0.0, SemVer 2.0.0, branch naming, commit guard, full-directory AI marker audits, and human ghostwriter style on all git/jj operations. Zero AI markers. Use on 'commit', 'branch', 'tag', 'release', 'changelog', 'semver', 'bump version', 'next version', 'CHANGELOG.md', 'audit markers'…

Destynova2/cli-code-skills · 128 tokens

publish-npm-version

Cuts the next release of Prisma 8: bumps the root package.json version (on the v8 RC line: 8.0.0-rc.N → rc.N+1), propagates it to every workspace package, and opens a PR titled "chore(release): bump to ". When the maintainer merges the PR, the Publish to npm workflow runs automatically and ships the new version to npm…

prisma/orm · 182 tokens

codew-release-qa-sweep

Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.

Hmbown/CodeWhale · 31 tokens

skillshare-changelog

Generate CHANGELOG.md entry from recent commits in conventional format. Also syncs the website changelog page. Use this skill whenever the user asks to: generate a changelog, document what changed between tags, or create a new CHANGELOG entry. If you see requests like "write the changelog for v0.17", "what changed…

runkids/skillshare · 134 tokens

release

Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…

hyhmrright/brooks-lint · 135 tokens

fallow: Skill for Claude Code