agentleFS
piotrmechlinskipiotrmechlinski/executive-brain/.claude/skills/review/SKILL.md

review

Skill0 starsChanged 8 days agoMITView on GitHub

The weekly review of the vault, covering what is overdue, what is due soon, projects that have not moved, the Inbox and done projects to archive. Use when the user types /review or asks what needs their attention.

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

Files
SKILL.md

Weekly review

  1. git pull --rebase origin main, then python3 tools/vault.py review.
  2. Show it short. First what was decided, closed or changed since the last review, in a few lines the executive can forward. Then each with its owner: overdue, due within 14 days, the open actions by owner, projects with no change in 30 days, the Inbox, done projects to archive, open risks without a mitigation, rows marked unverified.
  3. Propose one step for each: close it, move its date (with the reason), chase its owner (draft the message), confirm or correct an unverified row, or archive the project.
  4. Apply what the executive agrees. Write the review down as Meetings/YYYY-MM-DD Weekly review.md with source: debrief, and make it the source of every row you change.
  5. python3 tools/vault.py refresh, then python3 tools/vault.py check. Commit as Weekly review YYYY-MM-DD, then pull and push main as CLAUDE.md says under "Git".

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.