record-session
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.
Best for post-commit wrap-upWorks with GitHubLow risk
⌘source
- author
@mindfold-ai- language
- TypeScript
★6.7kstars
366forks
Apr 30, 2026
✦overview.md
Key Features
- ·Records session summaries to journal files
- ·Captures commit hashes automatically
- ·Updates developer index files
- ·Archives completed tasks via script
- ·Reads git history, no direct git commit
Use Cases
- →After finishing a coding session and committing code, record what was done
- →Persist session context for future AI sessions
- →Archive tasks that are actually completed, regardless of status field
Best for
- ✓post-commit wrap-up
- ✓maintaining session journal
- ✓AI session continuity
Not ideal for
- !mid-session logging
- !workflows without git commits
FAQs
name
record-session
description
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.
[!] 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
statusstill saysplanningorin_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 |
$install
1-click copynpx skills add mindfold-ai/Trellis --skill record-sessionSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
4/ 5
very goodClear and well structured, with only minor parts that might need a second read.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
4/ 5
highMostly actionable with clear steps; only a few small gaps remain.