agentleFS
Sign inStart free
mikkiolamikkiola/radar/.claude/skills/session-end/SKILL.md

session-end

Skill2 starsChanged 27 days agoMITView on GitHub

Explicit, owner-triggered BACKLOG.md closure for Radar: reviews this session's commits for Closes: B-NNN trailers and presents/writes matching docs/BACKLOG.md closures per the confirmation rules below. Triggers on: /session-end only — never invoked by the model on its own judgment. Generic Closes: mechanism only, adapted from article-pipeline's session-end skill.

30 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

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

  • 0

    Common

    Most of the 23 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Exactly one candidate: write the docs/BACKLOG.md edit and make a local commit.

    line 44
  2. Very specific:

    Never touches docs/CONSTITUTION.md, docs/ARCHITECTURE.md, or docs/ROADMAP.md — this skill only handles docs/BACKLOG.md closure.

    line 57

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

Explicit, human-triggered BACKLOG.md closure for Radar, per the Closes: B-NNN convention documented in the universal rules (CT-1 and BL-5). The owner types /session-end; invoking it is the signal this command acts on — it does not try to infer whether a session is "done."

Trailer-detection rule

Never use a naive line-start text match (e.g. grep for lines beginning with "Closes:") — a commit body can contain ordinary prose that happens to start a wrapped line with that same text. Use git's own trailer parser instead, which only recognizes a real trailing key: value block per git-interpret-trailers:

git log <session-commit-range> --format="%H %(trailers:key=Closes,valueonly)"

Each output line is <full SHA> <value-or-blank> — filter out blank values; a commit with no Closes: trailer produces a trailing space and nothing after it. Never fall back to a plain line-start grep under any circumstance.

What this does

  1. Find this session's Closes: B-NNN trailers, per the trailer-detection rule above — never scan further back than this session's own commits, no repo-wide history scan.
  2. Look up each B-NNN's current title in docs/BACKLOG.md (its #### [B-NNN] <title> heading line — note Radar uses 4 hashes, not 3) — verbatim, exactly as written, no summarizing or rewording.
  3. Zero candidates found: say so plainly (e.g. "No Closes: trailers found in this session's commits — nothing to close.").
  4. Exactly one candidate: write the docs/BACKLOG.md edit and make a local commit. Invoking /session-end already is the owner's "close now" signal — no separate per-item confirmation prompt is needed on top of that. Do not push: a push needs the Owner's separate permission (WR-14 of the universal rules), requested only after the mandatory checks pass.
  5. More than one candidate: present them as a numbered list, verbatim titles, and ask which one(s) to mark done, if any. No git/implementation jargon in that question (no "trailer," "commit," "candidate"). Wait for the owner's explicit pick before writing anything; never guess.
  6. If a closure later turns out wrong: an ordinary follow-up edit/commit fixes it — no supersession ritual.
  7. Never touches docs/CONSTITUTION.md, docs/ARCHITECTURE.md, or docs/ROADMAP.md — this skill only handles docs/BACKLOG.md closure.

Source. Adapted 2026-08-27 from article-pipeline's .claude/skills/session-end/SKILL.md, generic Closes: half only. Duplicated rather than shared via tooltempest for now.

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