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
# Trace
Reading code tells you what _should_ happen. Running it tells you what does: the
callback nobody mentioned, the job that enqueues two more, the email that goes out
twice. That's the gap this fills. The output is a record, in order, of what one
scenario did when it ran, with every step marked as seen or only read.
Two ways this fails. You read the code, write it up in the past tense, and it looks
exactly like a run — so the reader trusts a guess as much as an observation. Or you
run a step that can't be undone: a process gets killed, a database gets dropped. The
first is worse, because nothing about it looks wrong.
## 1. Pin the scenario
The scenario is `$ARGUMENTS`, or ask for one. It arrives as a sentence ("user creates
an account"), a route, a command, a job name.
Turn it into three things before running anything:
- **Entry point.** The route and handler, CLI command, or job that starts it — found
in the code, not assumed. Two plausible ones (sign up by form, sign up by invite)?
Take the common one, say which, and name the other as its own trace.
- **Starting state.** Who is acting and what exists already. "A signed-in user who
…
The 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.
GET https://markdownregistry.com/api/v1/artifacts/art_pn6mpbrdiobvgkbl
GET https://markdownregistry.com/api/v1/resolve?ref=thoughtbot/rails-consultant/trace
GET https://markdownregistry.com/api/v1/blob/b164aa71e8d187a31f1762fd39c0f0d32a9d2cca3d16d31c8811d0c6b7d1eed7
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.
thoughtbot/rails-consultant · skills/ask-claude/SKILL.md · Recommend the best way to have Claude do something, checked against Anthropic's current docs, then write the prompt and…
thoughtbot/rails-consultant · skills/commit/SKILL.md · Commit the current changes as atomic commits, recording risks, tradeoffs, and alternatives considered.
thoughtbot/rails-consultant · skills/diff-explainer/SKILL.md · Builds a shareable HTML walkthrough of the current changes, highlighting risks, tradeoffs, and alternatives considered.
thoughtbot/rails-consultant · skills/multi-lens-review/SKILL.md · Review a change for defects, then against its spec, its codebase's conventions, the domains trying to emerge from it…
thoughtbot/rails-consultant · skills/pr/SKILL.md · Open a pull request whose description you write yourself, with a suggested title and a light proofread.
thoughtbot/rails-consultant · skills/preparatory-refactor/SKILL.md · Identify opportunities to introduce a refactor that would make a feature easy to implement.
thoughtbot/rails-consultant · skills/risk-score/SKILL.md · Score how risky a pull request or branch is with fixed rules, and reply with the result as JSON. Use when asked how…
yeachan-heo/oh-my-claudecode · skills/trace/SKILL.md · Evidence-driven tracing lane that orchestrates competing tracer hypotheses in Claude built-in team mode
jeremylongshore/tons-of-skills-marketplace · plugins/ai-agency/hyperflow/skills/trace/SKILL.md · Use when encountering bugs, test failures, runtime errors, broken builds, or "this doesn't work" reports. Systematic…
zereight/gitlab-mcp · .github/skills/trace/SKILL.md · Evidence-driven tracing with competing hypotheses in parallel. Activate when user says: trace this, trace, why did this…
oliver-kriska/claude-elixir-phoenix · plugins/elixir-phoenix/skills/trace/SKILL.md · Use when debugging how a value or request reaches Elixir code, finding who calls a function, or planning a signature…
ai-analyst-lab/ai-analyst · .claude/skills/trace/SKILL.md · Show the provenance trace, linking every reported number to the SQL that produced it with a confidence badge. Use after…
mirkobozzetto/arsenal · plugins/trace/skills/trace/SKILL.md · Save where the session stands before ending it, so next can resume it in a clean context. Also reads or records project…
