kanso-pr SKILL.md skillA
kanso-pr from blakecyze/kanso is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add blakecyze/kanso/kanso-pr@git:20260527.328da5ePins git:20260527.328da5e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- blakecyze/kanso
- Path
skills/kanso-pr/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260527.328da5e, committed May 27, 2026
- First version recorded
- Apr 23, 2026
- Size
- 8,707 bytes
- Repository stars
- 5
- License
- MIT
Use when the user asks to write a pull request description, open a PR, draft PR notes, or summarise a branch for 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
# kanso-pr Writes PR descriptions that survive Jira migrations, Slack thread rot, and six months of organisational drift. Self-contained by default. Pulls from commit history rather than re-inventing. The principles from `kanso-principles` apply. The description earns its place the same way code does. ## The job A PR description has two readers: the present reviewer and the future archaeologist. The present reviewer needs enough context to approve or push back. The future archaeologist — human or AI — needs enough context to understand *why* without cloning the repo, reading the diff, and reverse-engineering intent. External links rot. The description must stand on its own. Links supplement; they don't substitute. ## Before writing Gather context in this order: 1. **Target branch.** `!git rev-parse --abbrev-ref HEAD` for current, `$ARGUMENTS` or `main` as target. 2. **Commit history on this branch.** `!git log <target>...HEAD --format="%h %s%n%b%n---"`. These commits already contain the *what* and ideally the *why*. Pull from them. 3. **Diff summary.** `!git diff <target>...HEAD --stat` for scope awareness. …
Read the whole file at its exact version.
How to install
mdr add blakecyze/kanso/kanso-pr@sha256:1908bcc380da7313The line at the top of this page pins the label git:20260527.328da5e, 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_e5dox6tlxv536wrz)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Apr 23, 2026 and May 27, 2026, about one every 34 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260527.328da5e latest | 2026-05-27 | 328da5e | 8,707 B | A | view · diff |
| git:20260423.c7a43cc | 2026-04-23 | c7a43cc | 8,437 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 (8707 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
blakecyze/kanso · 5 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_e5dox6tlxv536wrz GET https://markdownregistry.com/api/v1/resolve?ref=blakecyze/kanso/kanso-pr GET https://markdownregistry.com/api/v1/blob/1908bcc380da731392a713425f1082d00a6ea9dedc967d091c89126fb251246f
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.