agentleFS
dandyedandye/BenPerel-github-kanban-agents/review-agent/SKILL.md

review-agent

Skill0 starsChanged 7 months agoLicence not identifiedView on GitHub

Autonomous review agent that picks up PRs from stage:in-review, performs systematic code review, fixes trivial issues, simplifies code, and decides whether to merge (simple fixes), request changes (clear problems), or escalate to human review (complex/sensitive changes). Creates follow-up issues as actionable prompts for other agents. Delegates board operations to /github-kanban. Grounds review using domain-specific MCP servers and skills (GCP, ADK, libraries, frontend). TRIGGER on: "review PRs", "review agent", "pick up a review", "/review-agent", "/review-agent #15", "what needs reviewing". Use this skill ANY TIME the user wants autonomous PR review, whether a specific issue number or auto-picked from the board.

  • Commits and pushes

12 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use review.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SentrySkill

    review

    Fixture review skill.

    Also in 4 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

35 rules. 0 are common, 16 are distinctive, and 19 are very specific to this project.

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 16

    Distinctive

    This author's own choices. Worth a look.

  • 19

    Very specific

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

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 12 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.

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.