agentleFS
gwpicardgwpicard/ai-loop-kit/.agents/maintainer-skills/writing-review/SKILL.md

writing-review

Skill0 starsChanged yesterdayMITView on GitHub

Review public-facing writing for artificial simplicity, vagueness, awkward phrasing and lost precision, and propose rewrites that keep the meaning. For pull request descriptions, issue text, release notes, documentation and kit guidance. Load it by its path.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Every text a reader outside this session will read: pull request descriptions and comments, issue text, release notes, CHANGELOG.md, …

    line 14
  2. Distinctive:

    Leave clear, natural and accurate sentences alone.

    line 24
  3. Distinctive:

    Check each rewrite against the original: the same scope, conditions and certainty, and no new fact.

    line 25

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Writing review

references/framework.md is the standard. Read it in full before you review. It names twelve writing problems, how to fix each one, and when a rewrite is an improvement.

What it covers

Every text a reader outside this session will read: pull request descriptions and comments, issue text, release notes, CHANGELOG.md, README.md, docs/DESIGN.md, CONTRIBUTING.md, and the Markdown guidance under kit/.

How to run it

  1. Establish the meaning first: the actors, operations, conditions and reader. For a claim about the kit, read the code or the diff that supports it.
  2. Review the text against the twelve criteria. Report each problem with the original sentence, the criterion, the reason and a rewrite.
  3. Leave clear, natural and accurate sentences alone.
  4. Check each rewrite against the original: the same scope, conditions and certainty, and no new fact.
  5. Then run .agents/maintainer-skills/humanizer/SKILL.md in its embedded mode.

For a release, a long document or a text you wrote yourself, ask a fresh reviewer to review the text: a subagent, or Codex in a read-only subprocess. Make the recommended changes yourself, after checking each finding against the evidence.

Fixed constraints

These override the framework where the two conflict: British spelling, no contractions in release notes, no em or en dashes, no issue or pull request numbers in a tracked file, and every command, setting and name kept exactly as written.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.