ship-it-now
Skill3 starsChanged 15 days agoMITView on GitHub
[Adam''s Skills] [skips confirmation] The unattended form of /ship-it. Gets this conversation''s work merged and deployed to every environment the repo has, production included — and does NOT stop to confirm when the release also carries unreleased work by other developers or other agent sessions. Identical to /ship-it in every other respect: same grounding in branches, PRs and environments, same verification, same merge-conflict policy. Takes no arguments by default; an optional scope override such as "only staging" limits which environments it deploys to. Invoke with /ship-it-now when you already know what is on the target branch and do not want to be asked.
In this repository19 other files it gives its agents.
- are-we-doneSkill
- assumption-inventorySkill
- brief-meSkill
- build-itSkill
- check-skill-updatesSkill
- context-auditSkill
- debriefSkill
- fresh-eyesSkill
- goal-workflowSkill
- memory-auditSkill
- raise-issueSkill
- regroundSkill
- report-issueSkill
- seatbeltSkill
- seatbeltsSkill
- ship-itSkill
- to-the-pointSkill
- ttpSkill
- where-are-weSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Section 4 does not gate: Do not call AskUserQuestion about other people's changes and do not wait for an answer.
- Very specific: line 28
If ../ship-it/SKILL.md is not readable from here, stop and tell the user to install /ship-it alongside this one.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Ship It Now
Same skill as /ship-it, with the ride-along confirmation gate turned off.
Read ../ship-it/SKILL.md, relative to this file, and follow it in full — with exactly
these two changes:
- Section 4 does not gate. Do not call AskUserQuestion about other people's changes and do not wait for an answer. Still print the short summary of whose work is riding along, before the deploy, so it is on the record — then continue straight through to production.
- Say so up front. The first line of your output names what this is: shipping to production
without confirmation. The user typed
-now; they should still see what that bought them.
Everything else is unchanged, and deliberately so. Grounding in section 1 still happens in full —
skipping confirmation is not permission to skip knowing. The merge-conflict policy in section 6
still stops for a genuine divergence of intent; that gate protects the code, not the user's
attention, and -now does not lift it. Verification in section 5 is still required: an unattended
ship is exactly the case where nobody else is watching whether it landed.
If ../ship-it/SKILL.md is not readable from here, stop and tell the user to install /ship-it
alongside this one. Do not improvise the workflow from this file: everything that makes shipping
unattended safe — the grounding, the verification, the conflict policy — lives over there.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.