squash-message SKILL.md skillB
squash-message from vzakharov/muthur is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add vzakharov/muthur/squash-message@git:20261028.0345136Pins git:20261028.0345136 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- vzakharov/muthur
- Path
.claude/skills/squash-message/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261028.0345136, committed Oct 28, 2026
- First version recorded
- Oct 14, 2026
- Size
- 19,152 bytes
- Repository stars
- 22
- License
- MIT
Produce a PR's squash record — the copy-ready body, posted as the `Proposed squash body:` comment, and the title, kept as the PR's own title. Owns the format, the draft→tighten discipline, where the draft is tracked, and when it must be re-synced. Invoke as `/squash-message [update-only]`.
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
**The squash title is the PR title.** GitHub's squash box prefills `<PR title> (#<n>)`, so the record's title is kept on the PR itself, re-composed on every run alongside the body, and the comment carries one block to copy: the body. The exception is a PR of one commit, which the box titles by that commit's subject under GitHub's default `COMMIT_OR_PR_TITLE` setting — Step 2 says when that earns the comment a title block. The operator copy-pastes this body verbatim into GitHub's squash box, so it becomes the permanent `git log` record — and it has two readers. The operator, at merge time; and, for as long as this code lives, agents reconstructing how the codebase got this way, who read squash messages **first** and open diffs only when the log doesn't answer them. So the body is a durable, high-level record: what a reader should remember about this change without having to dig into the diff. That makes the target **altitude, not brevity**. It carries every substantive change and the reason behind it; it doesn't carry the mechanics of getting there. **A first draft reliably lands below that altitude** — too many words per …
Read the whole file at its exact version.
How to install
mdr add vzakharov/muthur/squash-message@sha256:babef8bd06ea7a50The line at the top of this page pins the label git:20261028.0345136, 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_3wiilm2ynvjmu7kh)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 14, 2026 and Oct 28, 2026, about one every 3 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261028.0345136 latest | 2026-10-28 | 0345136 | 19,152 B | B | view · diff |
| git:20261027.cd6cecf | 2026-10-27 | cd6cecf | 19,020 B | B | view · diff |
| git:20261027.c9ec8c5 | 2026-10-27 | c9ec8c5 | 18,986 B | B | view · diff |
| git:20261026.2b8bffd | 2026-10-26 | 2b8bffd | 19,109 B | B | view · diff |
| git:20261014.0f16275 | 2026-10-14 | 0f16275 | 19,542 B | B | view |
Audit of the latest version
- fail: Frontmatter declares a name
- pass: Frontmatter block present
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (19152 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
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
vzakharov/muthur · 22 stars · license MIT · pushed 2026-10-30 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3wiilm2ynvjmu7kh GET https://markdownregistry.com/api/v1/resolve?ref=vzakharov/muthur/squash-message GET https://markdownregistry.com/api/v1/blob/babef8bd06ea7a506369d0f7f27cb789038eb8828113482f2f9c9729677b4a3d
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.