agentleFS
ravindu57ravindu57/SCML/.claude/skills/session-end/SKILL.md

session-end

Skill0 starsChanged 26 days agoApache-2.0View on GitHub

Close a work session — verify, record evidence, update PROGRESS.md / feature_list.json / ADRs, and commit.

28 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use 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.
  • 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

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

  • 0

    Common

    Most of the 21 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

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

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

    Run the full test suite (env prefix in CLAUDE.md) and .venv/bin/python -m ruff check trust_mediator/ tests/.

    line 7
  2. Very specific:

    Run scripts/check_frozen.sh.

    line 8
  3. Very specific:

    If trust_mediator/ changed this session, run the security-reviewer agent on the diff.

    line 9
  4. Very specific:

    Update feature_list.json for that item: set passes: true only if the verifier confirms every acceptance criterion with evidence that …

    line 10
  5. Very specific:

    Add an ADR to docs/DECISIONS.md for every decision made this session (next free number.

    line 11
  6. Very specific:

    Update PROGRESS.md: rewrite the current-state block (tests, HEAD, next item) and add a newest-first log entry with date, role, item, what …

    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
  1. Run the full test suite (env prefix in CLAUDE.md) and .venv/bin/python -m ruff check trust_mediator/ tests/. Record the counts.
  2. Run scripts/check_frozen.sh. If any hash fails, stop: report which file changed and how, and do not commit.
  3. If trust_mediator/ changed this session, run the security-reviewer agent on the diff. Run the verifier agent on the item worked on.
  4. Update feature_list.json for that item: set passes: true only if the verifier confirms every acceptance criterion with evidence that reproduces (test names, result file paths, commit). Otherwise leave it false and write what is missing in notes.
  5. Add an ADR to docs/DECISIONS.md for every decision made this session (next free number; status active). If a decision replaces an older one, mark the old one superseded and link both ways. Never delete an ADR.
  6. Update PROGRESS.md: rewrite the current-state block (tests, HEAD, next item) and add a newest-first log entry with date, role, item, what changed, evidence and open questions.
  7. Show the diff summary, then commit with a message that names the item and the evidence. Do not push.

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.