agentleFS
WenyuChiouWenyuChiou/academic-writing-skills/AGENTS.md

academic-writing-skills

AGENTS.md442 starsChanged 21 days agoMITView on GitHub

These rules guide review of repository changes; they do not authorize editing manuscripts, running paid or live research evaluations, or publishing changes. - Review the actual base-to-head diff and trace affected skill instructions, references, scripts, schemas, tests, and their consumers. Check that routing, declared inputs and outputs, cross-file references, and versioned packaging remain consistent. Scale checks to the changed contract and its impact. - Check that changes preserve source identity, citation and provenance, author intent, and inference limits. Flag instructions…

The file

We split this AGENTS.md into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check that changes preserve source identity, citation and provenance, author intent, and inference limits.

    line 10

≈ “Common” is an estimate: at least 1 in 5 of the 41,581 AGENTS.md 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.

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

Code Review Rules

These rules guide review of repository changes; they do not authorize editing manuscripts, running paid or live research evaluations, or publishing changes.

  • Review the actual base-to-head diff and trace affected skill instructions, references, scripts, schemas, tests, and their consumers. Check that routing, declared inputs and outputs, cross-file references, and versioned packaging remain consistent. Scale checks to the changed contract and its impact.
  • Check that changes preserve source identity, citation and provenance, author intent, and inference limits. Flag instructions that could invent citations, results, or unsupported claims, or present unavailable evidence as verified.
  • Inspect representative regression evidence for the changed behavior and its failure cases. A fixture or static check proves only what it exercises; do not claim live research quality or manuscript acceptance from it.
  • Each finding must identify the exact path and line or symbol, trigger, consequence, and supporting evidence. Separate confirmed defects from untested hypotheses and verification gaps; omit style-only preferences.

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.