agentleFS
albertomartureloalbertomarturelo/sii/.agents/skills/session-close/SKILL.md

session-close

Skill19 starsChanged 6 days agoMITView on GitHub

Close a session: tick docs/ROADMAP.md in its own commit, fold corrections into CONVENTIONS.md, propose ADRs for informal decisions, and stage docs with the code. Invoke explicitly before ending every working session.

22 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use session-open and 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.
  • vishnujchandranSkill

    session-open

    Restart-safe session starter that restores context, validates readiness, and creates a focused execution plan for the current development session.

    Also in 4 projects that use this

  • 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

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

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 3

    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:

    Before this session ends, do ALL of the following.

    line 10
  2. Very specific:

    Update docs/ROADMAP.md: if a surface changed state: tick a row ✅ on merge, flip 🚧/🔒, add a row for a newly planned surface, and refresh …

    line 12
  3. Distinctive:

    Do NOT close the session without completing step 1.

    line 32
  4. Distinctive:

    After completion, output a one-paragraph session summary suitable for pasting into the PR description.

    line 34

“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

Before this session ends, do ALL of the following. Do not skip any step.

  1. Update docs/ROADMAP.md if a surface changed state: tick a row ✅ on merge, flip 🚧/🔒, add a row for a newly planned surface, and refresh the ADR/issue columns. This is the versioned "are we there yet?" source of truth — bookkeeping goes in its OWN commit, never bundled with feature code. (docs/CURRENT_STATUS.md is no longer versioned — #79. If you keep a local one, it is yours; do not commit it.)
  2. If a convention was clarified or a pattern was corrected this session, update docs/CONVENTIONS.md accordingly — or docs/conventions/sii-wire.md when it is an SII wire rule (transport, parsing, session, write, pacing; ADR-033). Do NOT leave corrections only in chat history — they'll be lost next session.
  3. If a significant decision was made informally (in chat, in a review, in passing), propose creating an ADR via /new-decision before closing.
  4. Stage all docs/ changes in the SAME commit/PR as the session's code changes. Context updates ship with code, not after.

Do NOT close the session without completing step 1.

After completion, output a one-paragraph session summary suitable for pasting into the PR description.

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.