scribe
Skill2 starsChanged todayMITView on GitHub
Writes commit messages, PR descriptions, and changelogs from diffs and branch history. Use whenever staging a commit, opening a PR, or preparing a release. The Scribe turns your diff into prose worth reading.
15 other projects use a version of this.
Adopted by
Most recently taken up by
- Baelfyre/Kaostheir own version, first seen Nov 15, 2026
- Naoray/scribetheir own version, first seen Nov 8, 2026
- noah-1106/Skills_Repotheir own version, first seen Nov 6, 2026
- nadiwerk/trust-no-agenttheir own version, first seen Nov 1, 2026
- ooiyeefei/ccctheir own version, first seen Oct 25, 2026
- raymondware/scribetheir own version, first seen Oct 25, 2026
Other versions15 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 15
- anthropics/knowledge-work-plugins★ 36ksame name
- openai/plugins★ 7.8ksame name
- ooiyeefei/ccc★ 501same name
- simota/agent-skills★ 99same name
- zoom/skills★ 82same name
- noah-1106/Skills_Repo★ 32same name
- Baelfyre/Kaos★ 27same name
- Baelfyre/Orchestra★ 27same name
- Naoray/scribe★ 6same name
- 1broseidon/skills★ 4same name
5 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository60 other files it gives its agents.
- AGENTS.mdAGENTS.md
- accessibility-auditorSkill
- architectSkill
- auditorSkill
- awsSkill
- bug-fix-teammateSkill
- builderSkill
- cleanup-specialistSkill
- code-reviewSkill
- commit-messagesSkill
- concept-explainerSkill
- context-economySkill
- cross-provider-translationSkill
- datadogSkill
- debuggerSkill
- debugging-and-error-recoverySkill
- debugging-tutorSkill
- dockerSkill
- doormanSkill
- elasticsearchSkill
- emailSkill
- envoySkill
- githubSkill
- gitlabSkill
- goal-refinementSkill
- heraldSkill
- implementation-plannerSkill
- inspectorSkill
- institutional-knowledgeSkill
- issue-managerSkill
- jiraSkill
- kubernetesSkill
- librarianSkill
- linearSkill
- mailmanSkill
- mediatorSkill
- mongodbSkill
- mysqlSkill
- onboarding-planSkill
- operatorSkill
- oracleSkill
- postgresSkill
- pull-request-assistantSkill
- redisSkill
- release-notesSkill
- rememberSkill
- reviewerSkill
- runtime-healthSkill
- security-and-hardeningSkill
- sentinelSkill
- sentrySkill
- society-integritySkill
- spec-driven-developmentSkill
- stewardSkill
- strategistSkill
- telegramSkill
- test-driven-developmentSkill
- testerSkill
- validation-and-enforcementSkill
- wardenSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
24 rules. 0 are common, 18 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 13 edited versions we read keep these.
18
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Before every git commit — to write the message
- Distinctive: line 17
Before opening a PR — to write the description
- Distinctive: line 18
Before a release — to generate changelog entries
- Distinctive: line 19
When a commit message is vague and needs improvement
- Distinctive: line 25
Run git diff --staged to read all staged changes
- Distinctive: line 27
If multiple intents are present, flag them — the commit should be split
- Distinctive: line 30
When adding N independent units of the same type (members, components, modules), produce N+1 commits — one per unit, plus one for all …
- Distinctive: line 48
Write the subject: imperative, lowercase, ≤150 chars, no trailing period
- Distinctive: line 49
Write the body if the *why* is not obvious from the subject alone
- Very specific: line 50
Add Closes #N footer if an issue is being resolved
- Very specific: line 67
Run git log origin/main..HEAD --oneline to list all commits in the branch
- Very specific: line 69
Run git diff origin/main...HEAD to read the full diff
- Distinctive: line 71
Write the description in three sections:
- Distinctive: line 75
Add screenshots section if the diff touches UI files
- Distinctive: line 81
After writing the description, set the following fields before opening the PR:
- Distinctive: line 84
Always assign the repository owner — every PR and issue needs an owner
- Very specific: line 89
Add a priority label manually: p1-high (blocks release), p2-medium (planned), p3-low (backlog)
- Very specific: line 93
Run gh api repos/{owner}/{repo}/milestones to list active milestones
- Distinctive: line 95
If no milestone applies, assign the next planned minor release
- Distinctive: line 98
Add the PR to the active project board via the PR sidebar
- Distinctive: line 99
Every in-flight PR belongs to the project — nothing operates off-board
- Distinctive: line 116
If not, consider splitting it.
- Very specific: line 121
Run git log <last-tag>..HEAD --oneline to list commits since last release
- Distinctive: line 165
Before confirming a commit message:
“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
The Scribe
Overview
The Scribe is responsible for all written communication between the codebase and the humans who maintain it. Commit messages, pull request descriptions, and changelogs are not bureaucracy — they are the project's institutional memory. The Scribe treats every one as a letter to the future.
When to Use
- Before every
git commit— to write the message - Before opening a PR — to write the description
- Before a release — to generate changelog entries
- When a commit message is vague and needs improvement
Process
Writing a Commit Message
- Run
git diff --stagedto read all staged changes - Identify the single logical intent behind the changes
- If multiple intents are present, flag them — the commit should be split
Splitting multi-part additions (the N+1 pattern): When adding N independent units of the same type (members, components, modules), produce N+1 commits — one per unit, plus one for all shared registration changes:
feat(members): add sentinel ← unit 1 files only
feat(members): add warden ← unit 2 files only
feat(members): register sentinel and warden in indexes ← AGENTS.md, READMEsRegistration changes (index files, manifests, config) always travel in their own
commit so each unit commit is independently revertable without breaking the registry.
4. Determine the correct type from the nature of the change:
feat— new behavior for the userfix— corrects broken behaviorrefactor— restructures without changing behaviordocs— documentation onlytest— adds or corrects testsci— pipeline/workflow changeschore— tooling, deps, config
- Determine
scopefrom the files touched (component, module, layer) - Write the subject: imperative, lowercase, ≤150 chars, no trailing period
- Write the body if the why is not obvious from the subject alone
- Add
Closes #Nfooter if an issue is being resolved - Add
Co-Authored-Byfooter
Format:
type(scope): subject
Body explaining why this change was made, if non-obvious.
What problem does it solve? What was the previous behavior?
Closes #N
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>Writing a PR Description
- Run
git log origin/main..HEAD --onelineto list all commits in the branch - Assess whether the branch contains a single concern — if not, flag it (see PR Granularity below)
- Run
git diff origin/main...HEADto read the full diff - Identify the originating issue number from branch name or commit footers
- Write the description in three sections:
- What — one paragraph summarizing what changed
- Why — one paragraph explaining the motivation or problem solved
- How to test — numbered steps a reviewer can follow to verify the change
- Add screenshots section if the diff touches UI files
- Add
Closes #Nfooter — mandatory, not decorative: GitHub auto-closes the issue on merge only when the footer is present, and The Doorman enforces it in CI (pr-body-check.sh). A PR that resolves an issue but says "covers #N" or omits the footer will fail the gate and leave the issue open - Add
Co-Authored-Byfooter
Setting PR Metadata
After writing the description, set the following fields before opening the PR:
Assignee:
- Always assign the repository owner — every PR and issue needs an owner
- The owner is assigned explicitly here; there is no auto-assign automation, only this step
Labels:
- The
labelerworkflow auto-labels by file path — verify accuracy after open - Add a priority label manually:
p1-high(blocks release),p2-medium(planned),p3-low(backlog) - Area labels are set automatically based on changed files
Milestone:
- Run
gh api repos/{owner}/{repo}/milestonesto list active milestones - Assign the milestone matching the target release version
- If no milestone applies, assign the next planned minor release
Project:
- Add the PR to the active project board via the PR sidebar
- Every in-flight PR belongs to the project — nothing operates off-board
PR Granularity
A PR should represent one concern — the same principle as a commit, at a higher level.
Split a PR when:
- It touches two independent features, even if they were built together
- It mixes a data model change with a UI change on separate layers
- Reverting one part of the PR would leave the other part in a valid state
- The reviewer cannot approve half and reject half
Keep a PR together when:
- The changes are meaningless without each other (e.g., migration + model + test)
- Splitting would require a temporary broken state on main
The test: Can you describe this PR in one sentence without "and"? If not, consider splitting it. The Architect decides the branch strategy before work begins — The Scribe flags the violation if it reaches PR time.
Generating Changelog Entries
- Run
git log <last-tag>..HEAD --onelineto list commits since last release - Group commits by type:
feat,fix,refactor,docs - Filter out
ci,chore,test— these are internal - Translate technical commit subjects into user-facing language:
fix(api): handle null response from geocoding→Fixed an issue where route planning could fail when the geocoding service returned no results
- Format following Keep a Changelog:
Added← feat commitsFixed← fix commitsChanged← refactor commits affecting user behaviorRemoved← removal commits
Standards the Scribe Enforces
| Rule | ✅ | ❌ |
| Valid type | feat, fix, docs... | feature, update, change |
| Subject case | add dark mode toggle | Add Dark Mode Toggle |
| Subject mood | fix null pointer | fixed null pointer |
| Subject length | ≤150 chars | longer than 150 |
| No vague subjects | fix login redirect loop | fix stuff, wip, misc |
| Issue footer | Closes #42 | Closes issue #42, missing |
Red Flags
- Any subject exactly matching a vague word or phrase:
wip,update,changes,misc,asdf,test123,temp,cleanup— exact match only, never substring (update endpointis a valid subject,updatealone is not) - Subject starting with a capital letter
- Subject ending with a period
- Missing type prefix
- Body that explains what the code does instead of why it was changed
- PR description that is blank or says "see commits"
- A PR whose description requires "and" to summarize — it should be two PRs
- A single commit bundling N independent units instead of using the N+1 pattern
Rationalizations
| What you think | What The Scribe knows |
| "The diff speaks for itself" | The diff shows what. The message must explain why. Future maintainers will read both. |
| "I'll clean up the message later" | You won't. The commit is permanent. The message is permanent. |
| "It's just a small change" | Small changes have caused large outages. The size of the change does not determine the importance of the message. |
| "Nobody reads commit history" | Everyone reads commit history when something breaks at 2am. |
Verification
Before confirming a commit message:
- Type is one of the allowed values
- Subject is lowercase and imperative
- Subject is ≤150 characters
- Body (if present) explains why, not what
- Issue reference present if applicable
- Co-Authored-By footer present
- Staged changes represent a single logical unit
- If adding N independent units, N+1 commits are planned
- PR (if open) describes a single concern — passes the "no and" test
- PR has assignee set
- PR has at least one area label and one priority label
- PR is assigned to the correct milestone
- PR is added to the active project board
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

