agentleFS
sheldor26sheldor26/Blastdoor/.claude/skills/close-session/SKILL.md

close-session

Skill0 starsChanged 57 days agoMITView on GitHub

Use when a working session is ending, or before /clear when switching tasks — verify the build, refresh STATE.md, log what broke and what worked, and leave doctor green.

12 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

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

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 2

    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 this before ending any working session.

    line 8
  2. Very specific:

    Run the project's build and lint.

    line 13
  3. Distinctive:

    Ask two questions honestly:

    line 33

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

Close the session

Run this before ending any working session. The point is that the next session — which remembers nothing — starts from an accurate picture.

1. Verify

Run the project's build and lint. If either fails, fix it or write down exactly where it stopped in STATE.md under In flight. Never close on a red build without saying so in writing.

2. Refresh STATE.md

Rewrite the sections that changed — do not append. STATE.md is a snapshot; it has a line budget and doctor enforces it.

  • Shipped — move anything that is now genuinely done.
  • In flight — where work stopped, precisely enough to resume cold. "Halfway through the checkout form" is useless; "form validates but the Stripe webhook handler in app/api/stripe/route.ts is unwritten" is usable.
  • Next — the next two or three moves, in order.
  • Known rough edges — anything wrong and knowingly tolerated, with why.

Set the updated: line to today's date.

3. Log

Ask two questions honestly:

Did anything break, surprise us, or get fixed twice? → a mistake entry. The entry is only finished when it has a guardrail: the check, test, type or rule that makes the same failure impossible rather than merely known.

node .bitacora/cli.mjs new mistake "Specific title" --tags area,failure-mode --severity high

Did anything work unusually well? → a learning entry, but only if it would change how the next problem is approached. Otherwise it is a changelog line.

node .bitacora/cli.mjs new learning "Specific title" --tags area

Fill every bitacora:fill-me block with real prose. Placeholders left behind fail doctor.

4. Confirm

node .bitacora/cli.mjs doctor

Green, or say out loud what is not.

5. Do not commit unless asked

Show the diff and wait.

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.