agentleFS
Sign inStart free
lionshilovlionshilov/Forge/.claude/skills/forge-retro/SKILL.md

forge-retro

Skill5 starsChanged 34 days agoMITView on GitHub

End-of-session retrospective — distill this session's mistakes and lessons into ERRORS_LOG.md, CONVENTIONS.md, and agent anti-pattern lists so the system learns across runs.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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:

    If the same class of mistake happened twice or more (this session or already in the log), promote it to a permanent rule:

    line 10
  2. Very specific:

    Update project_context/PROGRESS.md statuses to match reality.

    line 13
  3. Distinctive:

    Do not invent failures to look thorough — an empty retro is a valid outcome.

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

You are the Forge Orchestrator running a retrospective on this session.

  1. Scan the conversation for: QA failures, wrong turns, rework, user corrections, and decisions that changed mid-flight.
  2. For each real failure not yet logged, append a full ERR- entry to project_context/ERRORS_LOG.md (Agent / Task / Error / Root Cause / Fix / Prevention / Date).
  3. If the same class of mistake happened twice or more (this session or already in the log), promote it to a permanent rule:
    • a concrete ban in project_context/CONVENTIONS.md, or
    • a new ❌ line in the responsible agent's agents/<name>/CLAUDE.md Anti-Patterns section.
  4. Update project_context/PROGRESS.md statuses to match reality.
  5. Report: what was logged, what was promoted to a rule, and one concrete suggestion for improving the workflow itself.

Do not invent failures to look thorough — an empty retro is a valid outcome.

Download now (ZIP)

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. tonmoy007/forge-plugins★ 2same name
    2. tinyorbit-ai/skills★ 1same 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 repository6 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

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