Borrowing it
Nothing to install: this file belongs to phase-rs/phase. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/phase-rs/phase/main/.claude/skills/ship-commits/SKILL.mdgit clone --depth 1 https://github.com/phase-rs/phaseWrote 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/phase-rs/phase/ship-commits)<a href="https://agentmods.dev/skills/phase-rs/phase/ship-commits"><img src="https://agentmods.dev/badge/skills/phase-rs/phase/ship-commits/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/phase-rs/phase/ship-commits"><img src="https://agentmods.dev/badge/skills/phase-rs/phase/ship-commits.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to high
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 →
- high Tool Misuse · line 64 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 82 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high YARA Match · line 64 YARA rule matched a known malware signature (reverse shell, backdoor, ransomware, C2 framework, or info stealer).Fix: Remove the malware payload or compromised file entirely. Investigate how it entered the skill and audit all other artifacts for additional indicators of compromise.
- high Agent Snooping · line 147 Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
- high Tool Misuse · line 211 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00093 | $0.05283 |
| Opus 5.5 | $0.00037 | $0.02113 |
| Sonnet 5.5 | $0.00019 | $0.01057 |
| Haiku 4.5 | $0.00009 | $0.00528 |
Grade C, and why
ship-commits scanned grade C with 1 finding 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 1mo 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
# rm -rf "$run" How it starts
The opening of the file, as written. The whole thing — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship Commits
Take local commits and land them on main through the merge queue, using an isolated worktree to avoid carrying other agents' concurrent work into the PR.
Goal
Get the PR fully enqueued — not merely auto-merge enabled — and address every actionable PR review comment. A PR is enqueued only when GitHub reports a non-null mergeQueueEntry; gh pr merge --auto merely expresses intent and is not a terminal condition.
Why a worktree
The main working dir is assumed to contain other unrelated changes from concurrent agents — unstaged work, other branches, in-progress commits on main that aren't yet shipped. Branching in place risks:
- Carrying unrelated commits into the PR (if local
mainis ahead oforigin/mainwith multiple agents' work). - Disturbing other agents' branch state with
git checkoutoperations. - Leaving the user on a topic branch they didn't expect to be on.
A worktree based on origin/main gives a clean branch we cherry-pick into, isolated from everything else.
When to use
- User has finished a discrete chunk of work and wants it shipped.
- One or more commits exist locally (named explicitly, or "the last N commits on main", or "this commit").
- Goal: branch → push → PR → review/CI → confirmed queue admission, with the queue handling rebase + merge in the background.
When NOT to use
- Work is uncommitted. Run
/commitfirst (commit by pathspec — your memory'sfeedback_shared_index_commit_pathspec). Uncommitted work being shipped must not be left dirty on localmain. - A PR for these commits already exists. Use
gh pr merge <N> --autodirectly to enqueue. - The commits are already on
origin/main. Nothing to do. - Repo isn't
phase-rs/phase. This skill encodes phase.rs-specific conventions.
Phase.rs-specific conventions
| Convention | Why |
|---|---|
The merge queue owns the merge strategy — do NOT pass --squash. gh pr merge --squash --auto is rejected with The merge strategy for main is set by the merge queue. Pass --auto alone. The queue still produces a squash commit, which is why Step 0's reconciliation must stay squash-aware. |
Repo keeps main as one-commit-per-feature, enforced queue-side rather than client-side. |
--auto is mandatory on gh pr merge. |
Without it, the merge bypasses the queue and tries to merge immediately — fails on protected main. |
--no-verify on push. |
Pre-push hooks duplicate validation that Tilt/CI has already done locally. CI/queue will re-validate. |
Branch protection on main blocks direct push for non-admins. |
Queue handles serialization for parallel PRs. |
| Worktree-based shipping. | Main working dir has concurrent changes from other agents — don't disturb them. |
| No dollar-digit tokens in this file's snippets (awk fields, shell positionals). | Claude Code replaces them with the skill's arguments when it loads, so /ship-commits <args> silently rewrites them. |
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.
- 1mo ago Changed · +50 lines · -22 tokens per session scan A → C 0da26b07aa1c
- 2mo ago First seen · 285 lines · 115 tokens per session scan A 0858189f42bd
ship-commits is a skill published in the GitHub repository phase-rs/phase (312 stars, last pushed today), licensed Apache-2.0. It adds 93 tokens to every session and 5,283 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
deployment-rules
Release/deployment standards — semantic-release, commitlint, version sync, the updater. Load for /prepare-release and changes to release.config.mjs / commitlint / workflows / version files. Owned by project-steward.
coding-standards
General repo rules enforced by ESLint/TypeScript/CI — PRs-only, never bypass lint, import ordering, type imports, path privacy, commit format. Load for any code change.
anarlog
Query Anarlog meetings, notes, summaries, transcripts, participants, action items, and recurring history, or import a local recording. Use when a user asks about their Anarlog meeting data or needs meeting context for another task.
app-release
Use when the user asks to release a new version, ship a build, or publish a Skill Zoo release. Also use when a tag push results in Homebrew 404 errors or missing artifact failures.
graphify-windows
Turn any folder of files into a navigable knowledge graph with community detection, an honest audit trail, and three outputs: interactive HTML, GraphRAG-ready JSON, and a plain-language GRAPHREPORT.md.
lessons
How to propose and query distilled lessons (the experiential memory). Only project-steward persists; every other agent proposes/queries. Use when you discover a durable lesson or need prior experience for the current task.