agentleFS
lxyerlxyer/multi-agent-collaboration-system/.agents/skills/record-session/SKILL.md

record-session

Skill1 starsChanged 7 months agoMITView on GitHub

Records completed work progress to .trellis/workspace/ journal files after human testing and commit. Captures session summaries, commit hashes, and updates developer index files for future session context. Use when a coding session is complete, after the human has committed code, or to persist session knowledge for future AI sessions.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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:

    All acceptance criteria met?

    line 22
  2. Very specific:

    Don't skip archiving just because status still says planning or in_progress

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

[!] Prerequisite: This skill should only be used AFTER the human has tested and committed the code.

Do NOT run git commit directly — the scripts below handle their own commits for .trellis/ metadata. You only need to read git history (git log, git status, git diff) and run the Python scripts.


Record Work Progress

Step 1: Get Context & Check Tasks

python3 ./.trellis/scripts/get_context.py --mode record

[!] Archive tasks whose work is actually done — judge by work status, not the status field in task.json:

  • Code committed? → Archive it (don't wait for PR)
  • All acceptance criteria met? → Archive it
  • Don't skip archiving just because status still says planning or in_progress
python3 ./.trellis/scripts/task.py archive <task-name>

Step 2: One-Click Add Session

# Method 1: Simple parameters
python3 ./.trellis/scripts/add_session.py \
  --title "Session Title" \
  --commit "hash1,hash2" \
  --summary "Brief summary of what was done"

# Method 2: Pass detailed content via stdin
cat << 'EOF' | python3 ./.trellis/scripts/add_session.py --stdin --title "Title" --commit "hash"
| Feature | Description |
|---------|-------------|
| New API | Added user authentication endpoint |
| Frontend | Updated login form |

**Updated Files**:
- `packages/api/modules/auth/router.ts`
- `apps/web/modules/auth/components/login-form.tsx`
EOF

Auto-completes:

  • [OK] Appends session to journal-N.md
  • [OK] Auto-detects line count, creates new file if >2000 lines
  • [OK] Auto-detects Branch context (--branch override; otherwise Branch = task.json -> current git branch; missing values are omitted gracefully)
  • [OK] Updates index.md (Total Sessions +1, Last Active, line stats, history)
  • [OK] Auto-commits .trellis/workspace and .trellis/tasks changes

Script Command Reference

CommandPurpose
python3 ./.trellis/scripts/get_context.py --mode recordGet context for record-session
python3 ./.trellis/scripts/add_session.py --title "..." --commit "..."One-click add session (recommended, branch auto-complete)
python3 ./.trellis/scripts/task.py archive <name>Archive completed task (auto-commits)
python3 ./.trellis/scripts/task.py listList active tasks

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.