basui01/record-session
.agents/skills/record-session/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add basui01/agentflow record-sessionInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 17, 2026, 1:17 PM8.6s1 file scanned
SKILL.md
- 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 |
|---------|-------------|
| 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 (
--branchoverride; 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
| 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 |
Related Skills
basui01/parallel
development
VerifiedTrustedCommunity
Multi-agent pipeline orchestrator that plans and dispatches parallel development tasks to worktree agents. Reads project context, configures task directories with PRDs and jsonl context files, and launches isolated coding agents. Use when multiple independent features need parallel development, orchestrating worktree agents, or managing multi-agent coding pipelines.
1SKILL.mdUpdated Apr 17, 2026
basui01/update-spec
development
VerifiedTrustedCommunity
Captures executable contracts and coding knowledge into .trellis/spec/ documents after implementation, debugging, or design decisions. Enforces code-spec depth for infra and cross-layer changes with mandatory sections for signatures, contracts, validation matrices, and test points. Use when a feature is implemented, a bug is fixed, a design decision is made, a new pattern is discovered, or cross-layer contracts change.
1SKILL.mdUpdated Apr 17, 2026
basui01/start
development
VerifiedTrustedCommunity
Initializes an AI development session by reading workflow guides, developer identity, git status, active tasks, and project guidelines from .trellis/. Classifies incoming tasks and routes to brainstorm, direct edit, or task workflow. Use when beginning a new coding session, resuming work, starting a new task, or re-establishing project context.
1SKILL.mdUpdated Apr 17, 2026
basui01/onboard
development
VerifiedTrustedCommunity
Interactive three-part onboarding for new team members to the Trellis AI-assisted workflow system. Covers core philosophy (AI memory, project-specific knowledge, context drift), system structure and command deep-dives, real-world workflow examples, and guideline customization. Use when a new developer joins the project, someone needs to understand the Trellis workflow, or project guidelines need initial setup.
1SKILL.mdUpdated Apr 17, 2026