pr SKILL.md skillA
pr 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/pr@git:20261106.7724c75Pins git:20261106.7724c75 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/pr/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261106.7724c75, committed Nov 6, 2026
- First version recorded
- Nov 6, 2026
- Size
- 15,304 bytes
- Repository stars
- 29
- License
- MIT
Open a pull request whose description you write yourself, with a suggested title and a light proofread.
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
# PR
The LLM wrote the commits. The user owns the feature, so the user writes the
description. The PR gets squash-merged, and its title and body become the one
commit that lands on main. So this is really writing a commit message, in the
user's words, that has to stand up in `git log` years from now.
Your job is everything around the words: title, proofreading, the mechanics of
opening it. The failure to avoid is drafting the description yourself. Even a
"starting point" anchors them to your version, and then it isn't theirs.
```
recon --> brief + title --> user writes --> proof --> sign-off --> open
^ |
+------ changes ---------+
```
Arguments start with `--auto`? Nobody will write or approve the description.
Read [Autonomous mode](#autonomous-mode) first; it replaces steps 2 through 6.
## 1. Recon
Base branch is `$ARGUMENTS` (minus `--auto` and `--screenshots`), or the repo default (`gh repo view --json
defaultBranchRef`, falling back to `main`).
Read, don't ask:
- `git status`. Uncommitted changes or sitting on the base branch: stop and say
so. Committing and branching are other jobs.
…Read the whole file at its exact version.
How to install
mdr add thoughtbot/rails-consultant/pr@sha256:40a13cc93615f710The line at the top of this page pins the label git:20261106.7724c75, 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_kwehw7bazhjudchq)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Nov 6, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261106.7724c75 latest | 2026-11-06 | 7724c75 | 15,304 B | A | view · diff |
| git:20261106.ce8ab68 | 2026-11-06 | ce8ab68 | 14,882 B | A | view |
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 (15304 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_kwehw7bazhjudchq GET https://markdownregistry.com/api/v1/resolve?ref=thoughtbot/rails-consultant/pr GET https://markdownregistry.com/api/v1/blob/40a13cc93615f710ca733796deb27724e7401c95f3c6bbc910e5a16634a3b267
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