changes-explain SKILL.md skillA
changes-explain from yarlson/yarstack is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add yarlson/yarstack/changes-explain@git:20261017.2f2e03bPins git:20261017.2f2e03b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- yarlson/yarstack
- Path
plugins/yarstack/skills/changes-explain/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261017.2f2e03b, committed Oct 17, 2026
- First version recorded
- Jul 18, 2026
- Size
- 1,789 bytes
- Repository stars
- 3
- License
- MIT
Explain a pull request, commit range, branch, or local diff from a system-design perspective. Use for practical understanding of changed behavior, boundaries, flow, ownership, operations, risks, and verification rather than defect review.
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 Changes Translate one code comparison into its effects on the system, without inventing intent or exposing sensitive content. ## Workflow 1. Fix the comparison. For a branch or pull request, compare against the merge base (`git diff <base>...<head>`, or `gh pr diff`), not the current tip of the base branch. For local work, include staged, unstaged, and untracked files. If the scope cannot be isolated, say so and qualify the explanation. 2. Read the diff, the full changed files, the surrounding code they depend on, the tests, the configuration, and any linked brief that is in scope. 3. Group the edits by changed behavior or responsibility, not by file. 4. For each group, explain the previous and new behavior, the affected owner or boundary, the data and control flow, the external interactions, and the effects on users, developers, runtime, or operations. 5. Describe changed failure handling, compatibility, rollout, CI, verification, and remaining risk where the change alters them. 6. Mark what you observed in code, what the documentation or pull request says was intended, and what you infer. …
Read the whole file at its exact version.
How to install
mdr add yarlson/yarstack/changes-explain@sha256:6f7fa73fbea71422The line at the top of this page pins the label git:20261017.2f2e03b, 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_c4s5a7xzx6uuqg5m)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Jul 18, 2026 and Oct 17, 2026, about one every 46 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261017.2f2e03b latest | 2026-10-17 | 2f2e03b | 1,789 B | A | view · diff |
| git:20260718.206351f | 2026-07-18 | 206351f | 1,366 B | A | view · diff |
| git:20260718.7cc9d66 | 2026-07-18 | 7cc9d66 | 1,373 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 (1789 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
yarlson/yarstack · 3 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_c4s5a7xzx6uuqg5m GET https://markdownregistry.com/api/v1/resolve?ref=yarlson/yarstack/changes-explain GET https://markdownregistry.com/api/v1/blob/6f7fa73fbea7142226d9c1605e9d8fd38544366b7d6bad14586ba616587bd490
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.