agentleFS
Sign inStart free
pbakauspbakaus/agent-reviews/CLAUDE.md

agent-reviews

CLAUDE.md299 starsChanged 30 days agoMITView on GitHub

CLI + Agent Skills for managing GitHub PR review comments. See README.md for full details.

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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. Distinctive:

    No em dashes: Use commas, periods, or parentheses instead.

    line 29
  2. Distinctive:

    Keep CLI output minimal. No status messages, only results.

    line 33
  3. Very specific:

    Changelog: when shipping a new version, add an entry to both README.md (under ## Changelog) and website/src/lib/components/Changelog.svelte …

    line 34

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

CLAUDE.md

Project

CLI + Agent Skills for managing GitHub PR review comments. See README.md for full details.

Structure

bin/agent-reviews.js             CLI entry point (npm -g users)
lib/                             Core modules (github, comments, format)
skills/resolve-reviews/          Skill: all reviews (human + bot)
skills/resolve-agent-reviews/    Skill: bot reviews only
skills/resolve-human-reviews/    Skill: human reviews only
.claude-plugin/                  Plugin manifest + marketplace catalog

Key Commands

TaskCommand
Install skills locallynpm run install-skills (also runs on npm install)
Publish to npmnpm publish
Test CLI locallynode bin/agent-reviews.js
Run testsnpm test

Rules

  • No em dashes. Use commas, periods, or parentheses instead.
  • Node.js CommonJS throughout (no ESM).
  • Version in three places: package.json, .claude-plugin/plugin.json, skills/*/SKILL.md frontmatter.
  • Skills use npx agent-reviews (no bundled scripts).
  • Keep CLI output minimal. No status messages, only results.
  • Changelog: when shipping a new version, add an entry to both README.md (under ## Changelog) and website/src/lib/components/Changelog.svelte (new changelog-entry div at the top of the list). Keep entries concise, one <li> per feature/fix.

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.

Check your setup, free