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
Use this template for writing the PR body:
```markdown
## Summary
<diagram, diff-sketch, or tree>
## Evidence
- **Before:** <screenshot/output/failing test run>
**After:** <screenshot/output/passing test run>
## Merge Danger
**Door:** <one-way or two-way>
<optional: description>
**Blast Radius:** <one-word description>
<optional: potential ramifications of merge>
```
## Sections
Skip all preambles and keep prose brief. Use the user's domain language from `GLOSSARY.md`.
### Summary
Pick the smallest view that makes the key point clear.
- Show logic or an algorithm as pseudocode:
```text
on(save)
if content is unchanged
return cached result
write new content
return fresh result
```
- Show runtime control flow as a call tree:
```text
submitForm
createSession
persistPrompt
launchAgent
navigateToSession
```
- Show UI structure as a component tree, including state and module boundaries that matter:
```text
<SessionPage> (apps/example/src/routes/session.tsx)
useSessionEvents()
<SessionToolbar>
<RunSkillButton> (packages/ui)
```
- Show file responsibility or a broad refactor as a shallow file tree:
```text
src/
…
The line at the top of this page pins the label git:20261012.178eb1e, 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.
A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (4186 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
GitHub
shaderera/shaderera · 7 stars · license MIT · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_obzsogm4osi65zrv
GET https://markdownregistry.com/api/v1/resolve?ref=shaderera/shaderera/pr
GET https://markdownregistry.com/api/v1/blob/d3a3300c6ea1dc852c5647333e7fdb340fcaa113597db8fc6708693df7705fb0
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.
shaderera/shaderera · .claude/skills/code-review/SKILL.md · Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code…
shaderera/shaderera · .claude/skills/codebase-design/SKILL.md · Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find…
shaderera/shaderera · .claude/skills/diagnosing-bugs/SKILL.md · Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports…
shaderera/shaderera · .claude/skills/domain-modeling/SKILL.md · Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md…
shaderera/shaderera · .claude/skills/grill-with-docs/SKILL.md · A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
shaderera/shaderera · .claude/skills/grilling/SKILL.md · Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or…
shaderera/shaderera · .claude/skills/improve-codebase-architecture/SKILL.md · Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you…
yeachan-heo/oh-my-claudecode · skills/pr/SKILL.md · Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify…
jeremylongshore/tons-of-skills-marketplace · plugins/ai-agency/hyperflow/skills/pr/SKILL.md · Use when reviewing an incoming GitHub pull request — runs the multi-level (L1-L5) audit against the PR's real diff…
reactive/data-client · .agents/skills/pr/SKILL.md · Create a GitHub pull request from current working changes. Handles all git states - uncommitted changes, no branch…
vinta/hal-9000 · skills/pr/SKILL.md · Use when the user explicitly asks to push the current branch and open a PR, rewrite an open PR's body from its commits…
jellydn/my-ai-tools · configs/amp/plugins/my-ai-tools-skills/skills/pr/SKILL.md · Write a fast-to-review pull request body with a visual summary, before/after evidence, and merge-risk analysis.
jellydn/my-ai-tools · skills/pr/SKILL.md · Write a fast-to-review pull request body with a visual summary, before/after evidence, and merge-risk analysis.