changes-report SKILL.md skillA
changes-report 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-report@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-report/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261017.2f2e03b, committed Oct 17, 2026
- First version recorded
- Jul 18, 2026
- Size
- 5,371 bytes
- Repository stars
- 3
- License
- MIT
Report all repository changes that entered a target branch during one required date or period, grouped by product change and written as plain English for a broad audience. Use for daily, weekly, date-range, or relative-period change summaries rather than explaining one known diff.
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
# Report Changes for a Period Produce one evidence-based account of what changed and why it matters, independent of commit and pull request boundaries. ## Required Input Require a date or period. Accept a single `YYYY-MM-DD` date, an explicit start and end date, or a clear relative period such as `today`, `this week`, or `last week`. If the user did not specify one, ask which date or period to report and stop. If it cannot be resolved to exact bounds, ask for a precise date or period and stop. Use the local system timezone unless the user specifies another timezone. Treat a single date as the half-open period from 00:00 on that date to 00:00 on the next date. Treat an explicit end date as inclusive by ending at 00:00 on the following date. Resolve calendar weeks from Monday at 00:00. End a relative period that includes the present, such as `today` or `this week`, at the current time; use full calendar bounds for completed periods such as `yesterday` or `last week`. Before inspecting changes, record the resolved start, exclusive end, timezone, and human-readable period label. Use those exact bounds throughout the report. ## Workflow …
Read the whole file at its exact version.
How to install
mdr add yarlson/yarstack/changes-report@sha256:ad31ee17c03e1e9eThe 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_25bo6ppjdl2blfvy)
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 | 5,371 B | A | view · diff |
| git:20260828.116b669 | 2026-08-28 | 116b669 | 4,750 B | A | view · diff |
| git:20260718.7f6888b | 2026-07-18 | 7f6888b | 4,759 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 (5371 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_25bo6ppjdl2blfvy GET https://markdownregistry.com/api/v1/resolve?ref=yarlson/yarstack/changes-report GET https://markdownregistry.com/api/v1/blob/ad31ee17c03e1e9ea39fcafb68177c1b88c44754902416496d58869125d1b5d2
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.