agentleFS
maurice-jobstmaurice-jobst/ai-workbench/skills/session-close/SKILL.md

session-close

Skill0 starsChanged 47 days agoMITView on GitHub

Close a work session in a file-first AI workbench. Captures decisions and learnings, rewrites the desk file, runs scripts/check, commits on a branch and opens a pull request. Use at the end of every session, and whenever git status shows work that would otherwise be lost.

22 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use handoff.

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.
  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 3 projects that use this

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 18 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:

    Documents touched: Every document whose subject changed this session is updated now, not next time.

    line 19
  2. Very specific:

    Run scripts/check. Fix every finding it reports before committing.

    line 32
  3. Distinctive:

    Never commit on the default branch (main unless AGENTS.md says otherwise).

    line 38

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

A session that ends without capturing what it learned is unfinished. Walk every step; each item is either done or named in the hand-over.

1. Capture

  1. Decisions. Anything settled this session that changes how work is done goes into DECISIONS.md (or the log AGENTS.md names): what, why, how to apply. A decision that closes an issue cites its number.
  2. Learnings. A gotcha that cost more than fifteen minutes becomes either a rule in AGENTS.md (only if it changes behaviour, one line) or a note where AGENTS.md says learnings live. Never a dated diary entry.
  3. Documents touched. Every document whose subject changed this session is updated now, not next time. A doc that states how something works is a claim.

2. Rewrite the desk

Rewrite STATUS.md (or the desk file AGENTS.md names) from scratch: what is true now, what is in flight and where, who owes what, the dates that matter, the open questions. Delete finished and struck-through items; git keeps the history. Anything longer than two lines moves to its own document with a link from the desk. Stay under 120 lines.

3. Check

Run scripts/check. Fix every finding it reports before committing; if a finding cannot be fixed this session, say so in the hand-over rather than committing around it. check: clean is the exit condition.

4. Commit on a branch

Never commit on the default branch (main unless AGENTS.md says otherwise). If the session is still on it, cut a branch named for the issue or the track first. Commit everything, work in progress included; the message names the track and references the issue (Refs #N). Half-done work is committed as WIP, never left dangling in the working tree.

5. Push and open a pull request

Push the branch and open a pull request against the default branch. The body states what changed, what is still open, and which issue it closes or advances (Closes #N or Refs #N); the tracker learns about the work from that reference, so nothing is closed by hand. The maintainer merges; the session does not.

6. Hand over

Close with a short list: what landed (branch, PR), what was parked, what the next session should pick up first, and every item this session could not handle. No silent drops.

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.