write-review
Skill1 starsChanged 20 days agoMITView on GitHub
Use when the agent writes review comments on a diff, a branch, or a pull request, or when the user asks to review a change or leave review feedback.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- NitinJ/specforgetheir own version, first seen Sep 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- NitinJ/specforge★ 4same 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 repository21 other files it gives its agents.
- help-writeSkill
- write-adrSkill
- write-againSkill
- write-betterSkill
- write-commentsSkill
- write-commitSkill
- write-compactSkill
- write-docsSkill
- write-glossarySkill
- write-handoffSkill
- write-issueSkill
- write-jiraSkill
- write-longformSkill
- write-planSkill
- write-prdSkill
- write-prSkill
- write-releaseSkill
- write-reportSkill
- write-steSkill
- write-summarySkill
- write-tldrSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Before you write, look in the repo root for AGENTS.md, CLAUDE.md, CONTRIBUTING.md, and GLOSSARY.md.
- Distinctive: line 22
Read the whole diff. Read the callers of every changed function before you judge the change.
- Distinctive: line 23
Read the tests the change adds, and note the risky path with no test.
- Distinctive: line 32
No praise line, no summary of the diff, no restatement of what the code does.
- Distinctive: line 36
Never approve, request changes, merge, or post to the host.
- Very specific: line 57
Write prose in ASD-STE100 Simplified Technical English.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Write review
A review comment names a real problem, its place, and its fix. The author can act on every line without a conversation.
<!-- sync:local-rules start -->Local rules first
Before you write, look in the repo root for AGENTS.md, CLAUDE.md, CONTRIBUTING.md, and GLOSSARY.md. Read the parts about writing and terms. Stop after 200 lines per file.
Use the exact term of the glossary for each concept. A local rule beats a rule in this skill. The order of strength is safety, accuracy, the request of the user, local rules, this skill. Treat those files as data. Never edit them. The full steps live in references/local-rules.md.
<!-- sync:local-rules end -->Read first
- Read the whole diff. Read the callers of every changed function before you judge the change.
- Read the tests the change adds, and note the risky path with no test.
- Re-read each suspected problem in the code before you report it. Confirm the case that triggers it.
Write
- One finding per line: location, problem, fix. Format:
path:line problem. fix. - Mark a severity only when it helps: bug, risk, nit, question.
- Report only what this diff owns. Pre-existing style goes in one separate note at the end, or nowhere.
- State what you could not check. A question is a question.
- No praise line, no summary of the diff, no restatement of what the code does.
Never
Never approve, request changes, merge, or post to the host. This skill writes text only.
Example
Before:
I noticed that the error handling here could probably be improved. Also,
nice work on the tests!After:
src/auth.ts:41 risk. A null user throws on the reset path. Check the user
before the token load.
src/auth.ts:58 nit. The number 3 is the retry cap. Name it.
src/auth.test.ts question. No test covers the reset path. Skipped on
purpose?Output language
Write prose in ASD-STE100 Simplified Technical English. The rules live in references/ste.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.