explain-this-pr SKILL.md skillA
explain-this-pr from varnan-tech/opendirectory is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add varnan-tech/opendirectory/explain-this-pr@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- varnan-tech/opendirectory
- Path
skills/explain-this-pr/SKILL.md- Versions recorded
- 2
- Latest version
- v1.0.0, committed Sep 16, 2026
- First version recorded
- Apr 14, 2026
- Size
- 4,584 bytes
- Repository stars
- 699
- License
- MIT
Takes a GitHub PR URL or the current branch and writes a plain-English explanation of what it does and why, then posts it as a PR comment. Use when asked to explain a PR, summarize a pull request, write a plain-English description of a PR, add a summary comment to a PR, or understand what a PR changes. Trigger when a user says "explain this PR", "summarize this pull request", "what does this PR do", "add a comment explaining the PR", or shares a GitHub PR URL and asks what it does.
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
# Explain This PR Read a GitHub pull request, understand what it changes, and write a plain-English explanation. Post it as a PR comment so reviewers have instant context. --- ## Step 1: Check Setup Confirm `gh` is authenticated: ```bash gh auth status ``` If not authenticated: `gh auth login` and follow the prompts. Confirm input. The user must provide one of: - A GitHub PR URL (e.g. `https://github.com/owner/repo/pull/123`) - A PR number in the current repo (e.g. `#123`) - The keyword "current" to use the PR for the current branch If no input, ask: "Which PR should I explain? Share the URL, PR number, or say 'current' for the active branch." --- ## Step 2: Fetch PR Context **Get PR metadata:** ```bash gh pr view PR_URL_OR_NUMBER --json number,url,title,body,author,baseRefName,headRefName,additions,deletions,changedFiles,commits,labels,state,isDraft ``` If `isDraft` is `true`, note this to the user: "This PR is still in draft. The explanation is based on its current state." **Get the diff:** ```bash gh pr diff PR_URL_OR_NUMBER ``` If the diff is over 400 lines, read the `--stat` summary and the first 200 lines of the diff: ```bash …
Read the whole file at its exact version.
How to install
mdr add varnan-tech/opendirectory/explain-this-pr@sha256:eee76cb7ca0a3db6The 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.
[](https://markdownregistry.com/a/art_mwys5pabeadoqxcp)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Apr 14, 2026 and Sep 16, 2026, about one every 155 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-09-16 | a03d635 | 4,584 B | A | view · diff |
| v1.0.0 | 2026-04-14 | cf4acb6 | 4,641 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 (4584 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
varnan-tech/opendirectory · 699 stars · license MIT · pushed 2026-10-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_mwys5pabeadoqxcp GET https://markdownregistry.com/api/v1/resolve?ref=varnan-tech/opendirectory/explain-this-pr GET https://markdownregistry.com/api/v1/blob/eee76cb7ca0a3db6cf76b966f1efd0a7f530f0a4a11eddd0ec4578d5714408fa
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.