agentleFS
anymasoftanymasoft/1c-ai/.claude/skills/session-retro/SKILL.md

session-retro

Skill0 starsChanged 4 months agoMITView on GitHub

Run a quick session retrospective: what worked, what didn't, lessons learned.

14 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 4

    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:

    Run a quick session retrospective: what worked, what didn't, lessons learned.

    line 9
  2. Very specific:

    Write retro to session-notes.md (append "## Retrospective" section if file exists, or create new)

    line 20
  3. Distinctive:

    If any lessons are universal (not project-specific), suggest adding to project CLAUDE.md

    line 21
  4. Distinctive:

    Keep it brief — 5-10 bullet points max

    line 25
  5. Distinctive:

    Don't over-analyze one-off issues

    line 27

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

session-retro

Run a quick session retrospective: what worked, what didn't, lessons learned.

Trigger

User says: "session-retro", "ретроспектива", "retro", "итоги"

Steps

  1. Review the current session:
    • What tasks were completed?
    • What approaches worked well?
    • What failed or took too long?
    • Any patterns discovered?
  2. Write retro to session-notes.md (append "## Retrospective" section if file exists, or create new)
  3. If any lessons are universal (not project-specific), suggest adding to project CLAUDE.md
  4. Report summary to user

Rules

  • Keep it brief — 5-10 bullet points max
  • Focus on actionable insights, not descriptions of what happened
  • Don't over-analyze one-off issues

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.