agentleFS
Sign inStart free
cedaniel200cedaniel200/atlas-template/.agents/skills/session-end/SKILL.md

session-end

Skill3 starsChanged 21 days agoMITView on GitHub

Session close checklist: tests, final commit, clean state and a summary for the next session.

28 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use session-start and ship.

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.
  • bitwize-music-studioSkill

    session-start

    Runs the session startup procedure - verifies setup, loads config and state, checks skill models, and reports project status. Use at the beginning of a fresh session.

    Also in 11 projects that use this

  • AWSSkill

    ship

    Finalize dev work on an issue branch — update docs, push, and open a PR.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 21 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Final commit: if changes remain: conventional commit + role byline.

    line 12

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

Steps (in order)

  1. Full tests with the command declared in AGENTS.md → green.
  2. Final commit if changes remain: conventional commit + role byline.
  3. Push the working branch.
  4. Clean state: git status without pending changes (or only inside the feature worktree).
  5. Summary: what was done, what remains, relevant files.

Checklist

  • Tests green
  • Incremental commits (not one giant commit)
  • Role byline on agent commits
  • No open QA or review findings
  • Default branch clean; work lives in its branch/worktree
  • Summary written for the next session

Persistent memory (if configured)

Store the session summary with the project's memory tool. If there is no memory configured, the summary goes to the chat and to the commit or 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.

Check your setup, free