agentleFS
alectivismalectivism/maven-template/skills/end/SKILL.md

end

Skill1 starsChanged 6 months agoMITView on GitHub

End MARVIN session, save context, and commit changes. Use when user types /end or /quit. Creates session log, updates state, and optionally commits to git.

  • Commits and pushes

10 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 9

    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:

    When user types /end or /quit

    line 21
  2. Distinctive:

    When actually done for a while

    line 22
  3. Distinctive:

    When wanting a full session summary

    line 23
  4. Distinctive:

    When closing out the day

    line 24
  5. Very specific:

    If any content was shipped, append to content/log.md:

    line 43
  6. Distinctive:

    If file doesn't exist, create it with header:

    line 73
  7. Distinctive:

    Update the "Last updated" timestamp

    line 84
  8. Distinctive:

    Ensure nothing falls through the cracks:

    line 86
  9. Distinctive:

    Follow-ups needed → add to open threads

    line 88
  10. Distinctive:

    If user wants to commit:

    line 97
  11. Distinctive:

    Keep summaries concise but complete enough for future context

    line 126

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

End MARVIN session with full context preservation.

When to Use

  • When user types /end or /quit
  • When actually done for a while
  • When wanting a full session summary
  • When closing out the day

Inputs

  • Full conversation from this session
  • Current state from state/current.md
  • Today's date (from startup)

Process

Step 1: Summarize Session

Review the conversation and extract:

  • Topics discussed — What did we work on?
  • Decisions made — What was decided?
  • Content shipped — Any work completed or published?
  • Open threads — What's unfinished or needs follow-up?
  • Action items — What does user need to do next?

Step 2: Update Content Log

If any content was shipped, append to content/log.md:

### {TODAY}
- **[TYPE]** "Title"
  - URL: {link if applicable}
  - Notes: {any relevant notes}

Step 3: Update Session Log

Append to sessions/{TODAY}.md:

## Session: {TIMESTAMP}

### Topics
- {topic 1}
- {topic 2}

### Decisions
- {decision 1}

### Shipped
- {content shipped, if any}

### Open Threads
- {thread 1}

### Next Actions
- {action 1}

If file doesn't exist, create it with header:

# Session Log: {TODAY}

Step 4: Update State

Update state/current.md with:

  • Any new priorities or action items
  • Changed project statuses
  • New open threads
  • Removed/completed items (mark as done)
  • Update the "Last updated" timestamp

Ensure nothing falls through the cracks:

  • Commitments made → add to priorities with context
  • Follow-ups needed → add to open threads

Step 5: Confirm with User

Show brief summary:

  • What was logged
  • Any follow-ups scheduled
  • State updated

Step 6: Commit Changes (Optional)

If user wants to commit:

git add -A
git commit -m "$(cat <<'EOF'
chore: session log and state update

Co-Authored-By: Claude <noreply@anthropic.com>
EOF
)"
git push

Output Format

**Session Summary:**
- Topics: {list}
- Shipped: {content if any}
- Open threads: {count}

**Updated:**
- sessions/{TODAY}.md
- state/current.md

See you next time!

Notes

  • Multiple /end calls in one day append to the same session file
  • Keep summaries concise but complete enough for future context

Skill created: 2026-01-22

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.