changelog-digest SKILL.md skillA

changelog-digest from silykat/silykat is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add silykat/silykat/changelog-digest@git:20261014.c638277

Pins git:20261014.c638277 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
silykat/silykat
Path
.claude/skills/changelog-digest/SKILL.md
Versions recorded
3
Latest version
git:20261014.c638277, committed Oct 14, 2026
First version recorded
Sep 30, 2026
Size
2,772 bytes
Repository stars
3
License
MIT

Write the CHANGELOG digest of an epic pull request (epic/* into main) - one line per change visible to users, in the BEGIN_COMMIT_OVERRIDE block that release-please reads. Use when opening or updating the pull request of an epic branch, or when asked for the changelog of an epic.

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

# Changelog digest of an epic

An epic branch (`epic/<slug>`) gathers several user stories and reaches `main` as **one squashed commit**. release-please builds the CHANGELOG from the commits of `main`, but it reads a `BEGIN_COMMIT_OVERRIDE` … `END_COMMIT_OVERRIDE` block in the pull request description instead of the commit message, when there is one. Each line of that block becomes one CHANGELOG entry.

## 1. Gather what the epic changed

From the repository, with the epic branch fetched:

```bash
git log --no-merges --format='%s%n%b%n---' origin/main..origin/epic/<slug>
gh pr list --base epic/<slug> --state merged --json number,title,body --limit 100
```

The pull requests merged into the epic branch (one per user story) say what changed for the user and why; the commits give the details.

## 2. Write one line per change a user can see

- Conventional Commits, one change per line: `feat(<scope>): <description>`, `fix(<scope>): <description>`, `perf(<scope>): …`. Scopes: `core`, `cli`, `vscode-extension`, `claude-code`, or none.
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint
mdr add silykat/silykat/changelog-digest@sha256:b3d4a8abb2dcf816

The line at the top of this page pins the label git:20261014.c638277, 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.

Badge

mdr badge

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

1 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 3 versions of this file, between Sep 30, 2026 and Oct 14, 2026, about one every 7 days.

versioncommittedcommitsizeaudit
git:20261014.c638277 latest2026-10-14 c638277 2,772 BA view · diff
git:20260930.53491fb2026-09-30 53491fb 2,768 BA view · diff
git:20260930.97b907c2026-09-30 97b907c 2,451 BA view

Audit of the latest version

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 (2772 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

silykat/silykat · 3 stars · license MIT · pushed 2026-11-04 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_b473q3ppyw77c7np
GET https://markdownregistry.com/api/v1/resolve?ref=silykat/silykat/changelog-digest
GET https://markdownregistry.com/api/v1/blob/b3d4a8abb2dcf816d9b8567d3b2980f123ca051bbb470fad3c9b827a207d74eb

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.

More from silykat/silykat

retro SKILL.md skill
silykat/silykat · adapters/claude-code/plugin/skills/retro/SKILL.md · Run a retro with the user on their work with you since the last retro (the review threads they left in silykat in VS…
git:20261014.c638277 · audit A · 3 stars
review SKILL.md skill
silykat/silykat · adapters/claude-code/plugin/skills/review/SKILL.md · Address the user's silykat comments, i.e. the code review threads they left in VS Code with the silykat extension. Read…
git:20261014.c638277 · audit A · 3 stars

Every file in silykat/silykat

Browse by kind, by grade A, or by owner.