agentleFS
poradaporada/domfiles/skills/.domfiles-super-review/SKILL.md

super-review

Skill7 starsChanged 5 days agoMITView on GitHub

Review changes thoroughly and resolve validated findings.

4 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

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 2

    Distinctive

    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:

    Follow Super Review for every invocation.

    line 15
  2. Distinctive:

    When the final stage is selected, also follow Final Review.

    line 17

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

Super Review

For super-review in T3 Code, I explicitly request separate top-level reviewer threads by default for the selected stages, including required replacements and repeated final reviews. This standing request covers direct invocations and reviews routed by another workflow. Follow Establish Review Execution for interface selection and verification. Continue follow-ups through the selected interface’s permitted lifecycle.

Follow Super Review for every invocation. Before selecting reviewer settings or creating sessions, read Reviewer Defaults.

When the final stage is selected, also follow Final Review. Read it before preparing the committed target or starting the final reviewer.

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.