style-review
Skill71 starsChanged 7 months agoMITView on GitHub
Reviews Markdown prose against the pinned agent-style v0.3.5 rules and optionally writes a polished copy beside the source. Use for specs, ADRs, PR bodies, release notes, and technical docs when prose quality or evidence discipline matters.
- Installs packages
5 other projects use a version of this.
Adopted by
Most recently taken up by
- elastic/docs-buildertheir own version, first seen Nov 4, 2026
- meowdiocre/meowpitheir own version, first seen Oct 27, 2026
- yzhao062/agent-styletheir own version, first seen Oct 23, 2026
- MetaMask/metamask-docstheir own version, first seen Oct 8, 2026
- hsigstad/research-kittheir own version, first seen Jul 5, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- MetaMask/metamask-docs★ 873same name
- yzhao062/agent-style★ 743same name
- elastic/docs-builder★ 26same name
- meowdiocre/meowpi★ 3same name
- hsigstad/research-kit★ 0same name
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 repository117 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-healthSkill
- agent-styleSkill
- angular-best-practicesSkill
- annotateSkill
- api-designSkill
- architecture-decision-recordsSkill
- aws-serverlessSkill
- backend-architectSkill
- backend-patternsSkill
- brainstormSkill
- bug-reportSkill
- changelogSkill
- claude-apiSkill
- cloud-architectSkill
- cloud-run-puppeteerSkill
- code-review-checklistSkill
- code-reviewSkill
- code-simplificationSkill
- codex-sddSkill
- commitSkill
- context-engineeringSkill
- database-architectSkill
- db-reviewSkill
- deep-interviewSkill
- design-reviewSkill
- design-systemSkill
- devops-deploySkill
- diagnoseSkill
- django-patternsSkill
- docker-patternsSkill
- dotnet-backend-patternsSkill
- dreamSkill
- drizzle-orm-expertSkill
- estimateSkill
- event-sourcing-architectSkill
- fastapi-proSkill
- fork-joinSkill
- freezeSkill
- frontend-designSkill
- frontend-patternsSkill
- frontend-ui-dark-tsSkill
- gate-checkSkill
- gemini-api-integrationSkill
- gitlab-ci-patternsSkill
- guardSkill
- handoffSkill
- hotfixSkill
- hybrid-cloud-architectSkill
- kubernetes-architectSkill
- laravel-patternsSkill
- launch-checklistSkill
- learnerSkill
- llm-app-patternsSkill
- localizeSkill
- map-systemsSkill
- map-workflowSkill
- markdown-injection-scannerSkill
- microservices-patternsSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 0 are common, 11 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
11
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 29
Use this skill for English technical prose where clarity, evidence, and review readability matter:
- Distinctive: line 38
Do not use this skill for routine chat, code, generated logs, or prose where the user's requested voice intentionally overrides formal …
- Distinctive: line 43
Before any audit, check whether the CLI is available:
- Distinctive: line 49
If the command is missing, do not claim style review has run.
- Distinctive: line 56
Do not install dependencies unless the user explicitly asks.
- Very specific: line 66
Read FILE.md and confirm it is prose that fits this skill's scope.
- Distinctive: line 67
Run the deterministic audit:
- Very specific: line 73
Add semantic judgment for rules the CLI marks as skipped because they need host-model context: RULE-01, RULE-03, RULE-04, RULE-08, RULE-11, …
- Distinctive: line 78
Ask the user before writing any revised copy:
- Distinctive: line 109
No new facts, metrics, citations, links, code behavior, or claims.
- Very specific: line 113
Write beside the source as FILE.reviewed.md.
- Distinctive: line 114
Never mutate or overwrite the source file.
- Distinctive: line 116
If RULE-H flags unsupported claims, do not invent evidence.
- Distinctive: line 130
When asked "is style-review active?", reply:
“Common” is measured: kept by at least 6 in 10 of the 5 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
Style Review
Opt-in prose review for SDD artifacts using the portable agent-style v0.3.5
skill bundle. This skill is a second-pass review gate, not a global writing
mode. It does not edit AGENTS.md, CLAUDE.md, or any source document in
place.
Source and Scope
- Rule pack:
.claude/skills/agent-style/references/RULES.md - Upstream note:
.claude/skills/agent-style/references/UPSTREAM.md - Attribution:
.claude/skills/agent-style/references/NOTICE.md - Detector reference:
.claude/skills/agent-style/references/rule-detectors.md - Revision prompt:
.claude/skills/agent-style/references/revision-prompt.md
Use this skill for English technical prose where clarity, evidence, and review readability matter:
- Specs and design docs
- ADRs and decision records
- PR titles and descriptions
- Release notes and changelog entries
- Runbooks, postmortems, and technical documentation
Do not use this skill for routine chat, code, generated logs, or prose where the user's requested voice intentionally overrides formal technical style.
Required CLI Check
Before any audit, check whether the CLI is available:
agent-style --versionIf the command is missing, do not claim style review has run. Report this exact fallback:
style-review not run: `agent-style` CLI is not on PATH. Install with `pip install agent-style` or `npm install -g agent-style`, then rerun `/style-review <file>`.Do not install dependencies unless the user explicitly asks.
Single-File Workflow
Invocation:
/style-review FILE.md- Read
FILE.mdand confirm it is prose that fits this skill's scope. Run the deterministic audit:
agent-style review --audit-only FILE.md- Add semantic judgment for rules the CLI marks as skipped because they need
host-model context: RULE-01, RULE-03, RULE-04, RULE-08, RULE-11, RULE-F, and
RULE-H. Use the bundled
agent-stylerules and detector reference as the source of truth. - Report a compact scorecard with per-rule counts and the first few examples.
Ask the user before writing any revised copy:
Produce a polished draft at FILE.reviewed.md?- On yes, compose the revision using the vendored revision prompt and write
only
FILE.reviewed.md. Never modifyFILE.md. - Re-run the audit on
FILE.reviewed.md. - Show before/after scorecard and a diff so the user can merge hunks manually.
A/B Compare Workflow
Invocation:
/style-review BEFORE.md AFTER.mdRun:
agent-style review --mechanical-only --compare BEFORE.md AFTER.mdReport the per-rule delta. Do not ask for polish and do not write files.
Polish Invariants
The polished draft must obey these hard constraints:
- No new facts, metrics, citations, links, code behavior, or claims.
- Preserve Markdown structure unless the structure is the violation.
- Preserve meaning and approximate length budget.
- Resolve only flagged style issues.
- Write beside the source as
FILE.reviewed.md. - Never mutate or overwrite the source file.
If RULE-H flags unsupported claims, do not invent evidence. Keep the claim flagged or ask the user for the missing source.
SDD Integration
- In REVIEW, use this skill when a prose artifact is important enough that clarity or citation discipline affects review quality.
- In SHIP, use this skill before final PR bodies, release notes, or docs when the user asks for polish or when the agent claims prose quality.
- In verification-before-completion, a style-quality claim requires fresh audit evidence from this skill or a clear statement that style review was skipped.
Self-Verification
When asked "is style-review active?", reply:
style-review active: audit 21 rules from agent-style v0.3.5 (deterministic via CLI; semantic via host for RULE-01, 03, 04, 08, 11, F, H); workflow at .claude/skills/style-review/SKILL.md.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.

