agentleFS
cykedevcykedev/vereinsheim/.claude/skills/review/SKILL.md

review

Skill1 starsChanged 14 days agoApache-2.0View on GitHub

Run an adversarial code review of the current branch diff by delegating to the committed code-reviewer sub-agent, and record findings in reports/. Use after /validate, before merging to main.

192 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use close-spec, daily-arxiv and 10 more.

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.
  • dzhngSkill

    close-spec

    When a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back to the real code for the how. Use when implementation has landed and the plan no longer matches what shipped, or the user says a feature/spec is finished. Pairs with [write-spec](../write-spec/SKILL.md) (the plan this closes) and [review](../review/SKILL.md) (run before closing).

    Also in 5 projects that use this

  • LambenthanSkill

    daily-arxiv

    每日从 arXiv 拉取新论文,过滤相关性,auto-ingest 高优先级论文,检测 SOTA 更新

    Also in 5 projects that use this

  • dzhngSkill

    design-with-images

    Explore UI and visual design with image generation, then iterate the real implementation against the user-selected concept. Use when brainstorming visual directions, offering mockup variants, or implementing an approved generated design; do not stop at the mockups or the first code approximation.

    Also in 5 projects that use this

  • LambenthanSkill

    exp-eval

    实验判决门:Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges

    Also in 5 projects that use this

  • +5 more from Lambenthan
  • +3 more from dzhng

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 156 edited versions we read keep these.

  • 1

    Distinctive

    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:

    Acting on findings: verify each against the code before implementing — no performative agreement, and push back with technical reasoning if …

    line 15
  2. Very specific:

    Only after green gates + a clean review: merge to main with --ff-only (after user OK).

    line 21

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

PIV step 4 of 4. Delegate the review to the code-reviewer sub-agent (in .claude/agents/):

  • Launch it via the Agent tool (subagent_type: code-reviewer) with the branch diff (git diff main...HEAD) and the relevant conventions (vault/conventions.md, vault/apps/<app>/<app>-code-conventions.md, for Ringwerk also ringwerk-ui-patterns.md; for Spiegel and the packages their CLAUDE.md).
  • It checks correctness, convention adherence, drift between the shared files of Ringwerk and Spiegel, and uses the codegraph MCP for impact/call-graph. It returns a structured verdict (confirmed issues + severity + concrete fixes).
  • Acting on findings: verify each against the code before implementing — no performative agreement, and push back with technical reasoning if a finding is wrong for this codebase. Clarify anything ambiguous first; then fix in order blockers → simple → complex.
  • Record confirmed findings in reports/YYYY-MM-DD-<topic>-review.md; address blockers, then re-run /validate if code changed.

Only after green gates + a clean review: merge to main with --ff-only (after user OK).

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.