pr-writing skillA
pr-writing is agent-read markdown (skill) from tjcages/skills: Write or review clear commit messages, PR titles, and PR descriptions that explain what changed and why. Use before writing git history or when asked to improve it. Not for code comments, chat replies, or docs pages..
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
# PR writing Full rules: [METHODOLOGY.md](./METHODOLOGY.md). Before/after: [EXAMPLES.md](./EXAMPLES.md). Chat shape: [RESPONSE.md](./RESPONSE.md). **These are requirements, not preferences.** A message that breaks one gets rewritten, not shipped. ## Operating order ### 1. Read the diff first `git diff main...HEAD --stat` then the real hunks. You cannot state *why* from a file list. ### 2. Write the subject (§1) Under 50 characters. Capitalized. No period. Imperative mood. Test every subject: **"If applied, this commit will ___."** If the sentence breaks, the subject is wrong. ``` Add retry guard to the token refresh path ``` Banned first words: `Added`, `Adding`, `Adds`, `Fixed`, `Fixes`, `Updated`, `Changes`, `WIP`, `Misc`, `Various`. Banned anywhere in a subject: emoji, ticket IDs, `[tags]`, trailing `.`. ### 3. Blank line, then body wrapped at 72 (§1) No exceptions — `rebase`, `format-patch`, and `git log` all break without the blank line, and the default pager does not wrap. ### 4. Body says what and why, never how (§2) The diff already says how. The body says: the problem that existed, why this solution, what you rejected, what it costs. …
Read the whole file at its exact version.
How to install
mdr add tjcages/skills/pr-writing@v1.0.0mdr add tjcages/skills/pr-writing@sha256:651c14290bc99236Pin 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.
[](https://markdownregistry.com/a/art_tm6dug5vpaqqo3pg)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-08-25 | 4659652 | 3,674 B | A | view · diff |
| v0.1.0 | 2026-08-25 | 2d46752 | 3,661 B | A | view · diff |
| v0.1.0 | 2026-08-12 | 989bbf2 | 3,857 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 (3674 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
tjcages/skills · 4 stars · license none · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_tm6dug5vpaqqo3pg GET https://markdownregistry.com/api/v1/resolve?ref=tjcages/skills/pr-writing GET https://markdownregistry.com/api/v1/blob/651c14290bc99236e1cbec82d69c7b3d7ec26311f21a27f9cb453f045acb7d0f
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.