ship SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
ship from thoughtbot/rails-consultant is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add thoughtbot/rails-consultant/ship@git:20261106.ce8ab68Pins git:20261106.ce8ab68 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- thoughtbot/rails-consultant
- Path
skills/ship/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261106.ce8ab68, committed Nov 6, 2026
- Size
- 7,709 bytes
- Repository stars
- 29
- License
- MIT
Implement, verify and review a feature based on its SPEC, then open a draft PR.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Ship
`/slice` gives you a SPEC. This runs the rest of the chain against it:
```
Prepare --> Implement --> Review --> Verify --> Open
prep tdd 5 lenses real app draft PR
refactor + fix + shots + check
```
Nobody has to be watching. A person can run it, or something in the cloud can,
and either way the draft PR is what you come back to.
Each step runs in a context that never saw the one before it. That's the whole
point — a session that just wrote the code is the worst possible reviewer of it,
and a session that watched the review happen writes a description that defends
the review instead of the change.
## Run it
Hand `assets/workflow.js` to the Workflow tool, with the SPEC path as `args`:
```
Workflow({
scriptPath: "<this skill's directory>/assets/workflow.js",
args: { spec: "docs/specs/<the-slug>.md" }
})
```
If `scriptPath` is refused, read the file and pass its contents as `script`
instead. Don't rewrite it inline from memory.
No SPEC path? Ask for one. The script throws without it, and every step after
`Prepare` measures itself against those acceptance criteria — the chain has
nothing to aim at otherwise.
…Read the whole file at its exact version.
How to install
mdr add thoughtbot/rails-consultant/ship@sha256:aee6eb7e51d8d9b7The line at the top of this page pins the label git:20261106.ce8ab68, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_say3oifnykmte3u6)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Nov 6, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7709 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
thoughtbot/rails-consultant · 29 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_say3oifnykmte3u6 GET https://markdownregistry.com/api/v1/resolve?ref=thoughtbot/rails-consultant/ship GET https://markdownregistry.com/api/v1/blob/aee6eb7e51d8d9b7ca4fcabce00e9576bcf3bc1a0ac7c5af6508452988699a5d
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from thoughtbot/rails-consultant
Every file in thoughtbot/rails-consultant