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.
75
92%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
[!] 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.
Portability rule: Run all commands from the repository root with repo-relative paths (./.trellis/scripts/...). Never hardcode user names, absolute paths, local home directories, or machine-specific workspace paths. The active developer is resolved from .trellis/.developer; if it is missing, first auto-resolve from TRELLIS_DEVELOPER, git config user.name, git config user.email local-part, or a unique existing .trellis/workspace/<developer>/. Only ask the collaborator for the developer id when those signals still cannot determine one uniquely.
python3 ./.trellis/scripts/get_context.py --mode recordIf this still reports that the developer is not initialized after auto-resolution, ask the collaborator for the developer id, then run:
python3 ./.trellis/scripts/init_developer.py <developer-id>
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:
status still says planning or in_progresspython3 ./.trellis/scripts/task.py archive <task-name># 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`
EOFAuto-completes:
--branch override; otherwise Branch = task.json -> current git branch; missing values are omitted gracefully)After running the script, verify with:
git log -1 --oneline
git status --shortReport both the code commit hash and the Trellis record commit hash. If .trellis/workspace or .trellis/tasks still has unstaged/uncommitted changes, report the exact blocker instead of claiming the session was recorded.
| Command | Purpose |
|---|---|
python3 ./.trellis/scripts/get_context.py --mode record | Get 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 list | List active tasks |
786846c
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.