agentleFS
lorem-devlorem-dev/duolog/.agents/skills/crit/SKILL.md

crit

Skill4 starsChanged 16 days agoApache-2.0View on GitHub

Review code changes, a plan, a live page (running dev server), or a local HTML file with Crit inline comments and structured human feedback. Use only when the user explicitly invokes /crit or directly asks to use Crit; a generic review request does not count.

3 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 1

    1. tomasz-tomczyk/skills★ 734% same

    Wrote their own version · 2

    1. ion-design/design-crit★ 15same name
    2. vmarafetti/crit★ 9same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository10 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

12 rules. 0 are common, 3 are distinctive, and 9 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 9

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If no arguments, check conversation context:

    line 25
  2. Very specific:

    Keep crit on loopback and reverse-proxy in.

    line 31
  3. Very specific:

    Run crit and wait until it exits:

    line 47
  4. Very specific:

    If a crit server is already running from earlier in this conversation, crit automatically connects to it.

    line 54
  5. Very specific:

    Do NOT proceed until crit completes: Do NOT ask the user to type anything.

    line 60
  6. Very specific:

    When crit completes, read stdout and follow its instructions.

    line 66
  7. Very specific:

    When a comment has quote, anchor, or drifted:

    line 68
  8. Distinctive:

    If it contains a suggestion block, apply that specific change

    line 80
  9. Very specific:

    Use --json for a single bulk call instead of one invocation per comment:

    line 93
  10. Very specific:

    Do NOT proceed until the background crit task completes: When it does, return to Step 3.

    line 118
  11. Distinctive:

    If the user asks for a URL, a shareable link, or to share the review:

    line 122
  12. Very specific:

    Only use --qr in real terminal environments with monospace rendering.

    line 138

“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

Review with Crit

This is the interactive, human-in-the-browser review cycle. Run it only after the user explicitly invokes /crit or directly asks to use Crit. A generic request to review code, a plan, a diff, a PR, or a page does not count.

Review and revise code changes, plans, live pages (running dev servers, staging URLs), or local HTML files using crit for inline comment review.

Step 1: Pass arguments to crit

The CLI auto-detects the review mode from its arguments. Do not ask the user which mode to use. Pass arguments through:

crit <arguments>               # file, dir, URL, .html — CLI auto-detects mode
crit --pr <num|url>            # GitHub PR (range mode)
crit --mr <iid|url>            # GitLab MR (range mode)
crit --range <base>..<head>    # commit range (range mode)
crit                           # no args → branch diff

If no arguments, check conversation context:

  1. A plan file was written earlier in this conversation → crit <plan-file>
  2. Otherwise → bare crit (branch diff)
<important if="the user wants to open the review from another device — e.g. a phone over Tailscale"> Keep crit on loopback and reverse-proxy in. Same Step 1 args still apply (file, bare `crit`, etc.):
crit --public-url "https://<machine>.ts.net" --allow-unauthenticated-network --no-open [args…]
# then: tailscale serve --bg --https=443 http://127.0.0.1:<port>
  • --public-url only changes the URL crit prints — it does not expose the server.
  • --allow-unauthenticated-network is required with --public-url (even on loopback) and with any non-loopback --host. Crit has no auth: anyone who can reach the URL can read the repo and post comments that may trigger agents. Confirm the user wants that blast radius.
  • Do not bind --host to a Tailscale/LAN IP — proxy with tailscale serve (or an SSH tunnel). Get <port> from crit's startup output, or fix it with -p. Relay the URL crit prints (the public one), not localhost.</important>

Step 2: Launch crit and wait for review completion

CRITICAL — you MUST run this step. Do NOT skip it. Do NOT proceed without it.

Run crit and wait until it exits:

crit <plan-file>   # specific file
crit               # git mode

If a crit server is already running from earlier in this conversation, crit automatically connects to it. Starting from scratch, it spawns the daemon, opens the browser, and blocks until the user clicks "Finish Review".

crit prints the review URL on startup (e.g. Started crit daemon at http://localhost:<port>). Relay it verbatim:

"Crit is open at http://localhost:<port>. Leave inline comments, then click Finish Review."

Do NOT proceed until crit completes. Do NOT ask the user to type anything. Do NOT read the review file early. Wait for the command to finish — that is how you know the human is done reviewing.

While crit is still running, do not send user-facing progress updates. Treat the wait loop as internal state.

Step 3: Read the review output

When crit completes, read stdout and follow its instructions. Check stderr for approved: true or approved: false.

When a comment has quote, anchor, or drifted:

  • quote: the specific text the reviewer selected — focus your changes on the quoted text rather than the entire line range
  • anchor: use it to locate the current position of the content; line numbers may be stale after edits
  • drifted: true: original content was removed or heavily rewritten — line numbers are approximate at best

Fallback (mid-round re-entry, plan hooks, or headless workflows): crit comments / crit comments --json. Use crit comments --plan <slug> for plan-mode reviews.

Step 4: Address each review comment

For each unresolved comment:

  1. Understand what the comment asks for
  2. If it contains a suggestion block, apply that specific change
  3. Revise the referenced file (plan or code file from the diff)
  4. Reply with what you did: crit comment --reply-to <id> --author 'Codex' '<what you did>' (reply bodies support markdown)
  5. Do not pass --resolve. Resolving is the reviewer's call. Only add --resolve if the user explicitly asks.

Editing the plan file triggers Crit's live reload — the user sees changes in the browser immediately.

<important if="you are revising in plan mode"> Re-emit the revised plan inside `<proposed_plan>...</proposed_plan>` so Crit can review the new version. </important>

When replying to multiple comments

Use --json for a single bulk call instead of one invocation per comment:

echo '[
  {"reply_to": "c_a1b2c3", "body": "Fixed"},
  {"reply_to": "c_d4e5f6", "body": "Refactored as suggested"}
]' | crit comment --json --author 'Codex'

For long or multi-line bodies, write the JSON to a file and pass --file. Use --file, not a < redirect.

crit comment --json --file /tmp/replies.json --author 'Codex'

Step 5: Signal completion and start next round

CRITICAL — you MUST run this step. Do NOT skip it. Do NOT proceed without it.

The finish prompt on stdout includes the command to run again — use it to start a new round.

On subsequent calls, crit automatically signals round-complete first, then blocks until the next "Finish Review" click.

Tell the user only: "Replied in Crit. Review the changes in your browser and click Finish Review when ready." Do not repeat your replies or list the comments in chat. The reviewer reads them in Crit.

Do NOT proceed until the background crit task completes. When it does, return to Step 3. If the user finishes with zero comments, the review is approved — stop the loop and proceed.

Sharing

If the user asks for a URL, a shareable link, or to share the review:

crit share <file>

Always relay the full output to the user — copy the URL directly into your response. Don't make them dig through tool output.

To remove a shared review:

crit unpublish [file...]

QR codes

Only use --qr in real terminal environments with monospace rendering. Skip it in mobile apps or web chat UIs — Unicode block characters won't render.

crit share --qr <file>

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.