Home / reidemeister94 / development-skills · skills/explain-diff/SKILL.md · GitHub

explain-diff skillA

Name: explain-diff
Author: reidemeister94

explain-diff is agent-read markdown (skill) from reidemeister94/development-skills: Explain a code change, its reasons, effects, trade-offs, and verification limits..

Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.

What the file says

# Explain diff

Explain the change so the user can understand its behavior and maintain it.
Manual mode is repository-read-only; `--visual` may write only to system temp.

Use the requested worktree, branch, range, pull request, patch, or packet. Default to the current worktree.
Inspect the implementation, request, relevant decisions, verification, review verdict, and evidence limits.
Use runtime data and logs when they settle a material claim. Label absent or stale evidence **Unverified change**.
For `--visual`, read [visual mode](references/visual-mode.md).

Explain the result, prior behavior, reasons, important failure cases, operational effects, and trade-offs.
The explanation must stand alone without requiring the user to open the repository.
Explain public or operational names before using them. Include implementation detail only when it helps the user's purpose.
Use a diagram or concrete example when it makes the behavior clearer.

## Optional dialogue

When the user wants an interactive explanation, ask applied questions one at a time.
Ask the user to predict behavior, make a decision, or diagnose an observable result.
…

Read the whole file at its exact version.

How to install

Latest version

mdr add reidemeister94/development-skills/explain-diff@git:20260919.a9f7da5

Exact content

mdr add reidemeister94/development-skills/explain-diff@sha256:d59211e668f237e7

Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.

Badge

[![mdr](https://markdownregistry.com/badge/art_jrk33ur3xnpuabs4.svg)](https://markdownregistry.com/a/art_jrk33ur3xnpuabs4)

1 badge views in 30 days

Versions

version	committed	commit	size	audit
git:20260919.a9f7da5 latest	2026-09-19	a9f7da5	1,992 B	A	view · diff
git:20260724.ba2c70f	2026-07-24	ba2c70f	4,541 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Deterministic, no model, 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 (1992 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

reidemeister94/development-skills · 12 stars · license MIT · pushed 2026-09-20 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_jrk33ur3xnpuabs4
GET https://markdownregistry.com/api/v1/resolve?ref=reidemeister94/development-skills/explain-diff
GET https://markdownregistry.com/api/v1/blob/d59211e668f237e76e7f545c2e557791ef44401cdd75f664c3605fb1e71191ed

Your agent 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.