Record work progress after human has tested and committed code
[!] 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.
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 --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:
| 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) |
python3 ./.trellis/scripts/task.py archive <name> | Archive completed task (auto-commits) |
python3 ./.trellis/scripts/task.py list | List active tasks |