agentleFS
deanmikandeanmikan/ai-native-company-starter/.agents/skills/review-workspace/SKILL.md

review-workspace

Skill0 starsChanged 2 months agoMITView on GitHub

Periodic maintenance pass over the workspace: run lint, surface stale and orphaned pages, verify and promote learnings, refresh work/now.md prompts, and run the evaluation questions. Use weekly or when asked to "tidy", "review", "audit", or "check freshness" of the workspace.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Lint: Run python3 scripts/lint.py --strict.

    line 13
  2. Very specific:

    Now: Read work/now.md. Ask the owner whether the focus, finish line, and next decisions are still current.

    line 30
  3. Distinctive:

    Decisions: Check "Revisit when" conditions on approved decisions.

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “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 the workspace

This pass keeps the workspace trustworthy. It proposes changes; the owner approves anything that touches approved knowledge.

Steps

  1. Lint. Run python3 scripts/lint.py --strict. Fix mechanical errors (frontmatter, broken relative links, numbering) directly.
  2. Stale pages. Lint lists pages past review_by. For each, read it and decide: still true (bump review_by, and updated only if content changed), needs an update (draft the change, keep status unchanged, flag for owner), or no longer true (status: superseded, link replacement, consider archive/). Never silently extend a review date on a page you did not read.
  3. Learnings. For each knowledge/learnings/ page:
    • draft: can it be verified from its evidence? If yes, set approved and tell the owner. If it has been draft through two reviews, resolve it: promote, correct, or supersede.
    • approved: has it proved durable? Fold it into the page named in "Promote to", then set the learning to superseded with a link.
  4. Orphans. Find pages under company/, areas/, work/, knowledge/ that no README.md or other page links to. Link them from the right index or archive them.
  5. Now. Read work/now.md. Ask the owner whether the focus, finish line, and next decisions are still current. Do not change it yourself beyond formatting.
  6. Projects. For each work/projects/ page, check the tracker or ask the owner for status. Close finished projects following work/projects/README.md.
  7. Decisions. Check "Revisit when" conditions on approved decisions. If a condition is met, tell the owner; do not reopen the decision yourself.
  8. Evaluations. Answer every question in agents/evals.md using only answer-company-question. Record pass/fail and what you fixed as knowledge/learnings/YYYY-MM-DD-eval-run.md. A failure is a workspace bug: fix the page or the registry, not the answer.
  9. Security. Confirm no secrets, credentials, or restricted personal data entered the repository since the last review (git log -p on the period, plus lint's secret scan).

Report

One message: what was fixed directly, what is proposed and awaits the owner (with paths), eval results, and the learnings promoted. Keep it under thirty lines.

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.