Write a fast-to-review pull request body with a visual summary, before/after evidence, and merge-risk analysis.
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
# Reviewable Pull Request
Prepare a pull request body that lets a human understand the change quickly, verify that it works, and spend review time where risk is highest. This skill improves the review narrative; it does not replace code review or validation.
## When to Use
Use when:
- A branch has a meaningful diff and needs a new or updated PR body.
- The reviewer needs the shape of a refactor, flow, or integration explained.
- The change has evidence and rollback implications worth making explicit.
Load `draft-pull-request` for repository preflight, branch handling, and `gh` publication rules. Reuse an existing PR instead of opening a duplicate.
## Required Inputs
Before writing, gather:
- The authoritative spec, issue, plan, or ticket graph.
- The complete diff against the PR base.
- The actual commands run and their output.
- Any screenshots, logs, or before/after behavior available.
- If a skill or workflow changed, the original input plus the pre-edit and post-edit outputs.
- The current PR template and existing reviewer notes.
Never claim a test, screenshot, or manual check that was not actually run.
## Body Template
…
The line at the top of this page pins the label v1.0.0, 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 (5750 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
jellydn/my-ai-tools · 123 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_illtrqlydys2r4bn
GET https://markdownregistry.com/api/v1/resolve?ref=jellydn/my-ai-tools/pr
GET https://markdownregistry.com/api/v1/blob/d173b3d1a61bfe3115fd66214b36a1a492530135bf8bf4264f0e7db8e3aa20fe
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.
jellydn/my-ai-tools · configs/amp/plugins/my-ai-tools-skills/skills/accountable-engineering/SKILL.md · Use explicit human checkpoints for architecture, security, rollout, or operational decisions.
jellydn/my-ai-tools · configs/amp/plugins/my-ai-tools-skills/skills/babysit-pr/SKILL.md · Use when monitoring an open GitHub PR for CI failures, review feedback, mergeability, and safe retries or fixes.
jellydn/my-ai-tools · configs/amp/plugins/my-ai-tools-skills/skills/blindspot-pass/SKILL.md · Inspect history and architecture for hidden constraints before risky cross-cutting changes.
jellydn/my-ai-tools · configs/amp/plugins/my-ai-tools-skills/skills/capability-experiments/SKILL.md · Build an interactive report or experiment when the user asks to explore model capabilities.
jellydn/my-ai-tools · configs/amp/plugins/my-ai-tools-skills/skills/code-quality-review/SKILL.md · Audit a diff for structural maintainability and unnecessary complexity.
jellydn/my-ai-tools · configs/amp/plugins/my-ai-tools-skills/skills/code-review/SKILL.md · Review a branch, PR, or worktree diff for repository conventions and stated intent.
jellydn/my-ai-tools · configs/amp/plugins/my-ai-tools-skills/skills/codemap/SKILL.md · Create a seven-document architecture map when the user asks to map a codebase.
jellydn/my-ai-tools · configs/amp/plugins/my-ai-tools-skills/skills/commit-atomic/SKILL.md · Group staged changes into atomic commits with commitizen convention
jellydn/my-ai-tools · configs/amp/plugins/my-ai-tools-skills/skills/context-discovery/SKILL.md · Use MCP tools to trace behavior that spans multiple modules or history sources.
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…
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 · skills/pr/SKILL.md · Write a fast-to-review pull request body with a visual summary, before/after evidence, and merge-risk analysis.
oprogramadorreal/optimus-claude · skills/pr/SKILL.md · Creates or updates a pull request (GitHub) or merge request (GitLab) for the current branch in the Conventional PR…
