agentleFS
Sign inStart free
javiarmestojaviarmesto/ALDC-AL-Development-Collection/.claude/skills/review/SKILL.md

review

Skill115 starsChanged 12 days agoMITView on GitHub

Independent read-only review of an AL increment implemented directly by Developer, without Conductor. Checks acceptance, BCQuality and current validation evidence before human approval.

192 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use close-spec, design-with-images 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

  • 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

    daily-arxiv

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

    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

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

The file

Create a free account to mount
Files
SKILL.md

/aldc:review

<!-- Generated by scripts/sync-plugin-support.js from the al-developer-reviewer contract; edit ENTRY_SKILLS in the generator, not this file. -->

Delegate this to the aldc:al-developer-reviewer subagent with the Agent/Task tool (subagent_type: "aldc:al-developer-reviewer", run_in_background: false), so that it runs with its own read-only tool list instead of this session's. In the prompt, pass the input below, the project root, the scope (changed objects or the files named) and any plan or spec path under .claude/plans/. Return its report to the user as it comes, without rewriting its verdict. Only if the host cannot launch subagents, read ${CLAUDE_PROJECT_DIR}/claude-plugin/agents/al-developer-reviewer.md in full and act as that agent, stating that the read-only tool list is not enforced.

Input: $ARGUMENTS

Requirement artifacts live under .claude/plans/ in the project; run /aldc:al-initialize once if that folder does not exist.

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