record-session

Records completed human-verified work into Trellis workspace journal files and updates session indexes.

92|8|Updated May 15, 2026
One-click install
npx skills add https://github.com/LonelyHerbivore/Trellis-Herbivore --skill record-session-lonelyherbivore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: record-session
Source: https://github.com/LonelyHerbivore/Trellis-Herbivore/tree/main/packages/cli/src/templates/codex/skills/record-session
Command: npx skills add https://github.com/LonelyHerbivore/Trellis-Herbivore --skill record-session-lonelyherbivore

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It solves the problem of losing valuable progress, commit evidence, and session knowledge after you finish a coding task, forcing future AI help to relearn context from scratch.

Core Features & Use Cases

  • Session journaling: Records a session title, summary, and commit hashes into .trellis/workspace journal files after human testing and a commit.
  • Task archiving: Archives tasks that are actually completed based on real work completion (including acceptance criteria), not just the task.json status.
  • Future-ready indexing: Updates index.md with totals, last active time, and line statistics so subsequent sessions can load the right context faster.

Quick Start

After the human tests and commits changes, run the record-session workflow to archive completed tasks and add a new journal entry for the session.

Frequently Asked Questions about record-session

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I archive coding sessions with git commits for future AI context?

You can archive completed coding sessions by running the workflow after testing and committing changes, which records session summaries and commit hashes into Trellis workspace journal files for future AI context.

What is workspace journaling and how does it preserve coding session knowledge?

Workspace journaling preserves session knowledge by recording titles, summaries, and commit hashes into Trellis journal files so future AI help can load context without relearning from scratch.

When should I record completed tasks instead of just updating the task status?

You should record completed tasks after human verification and a git commit, because the workflow archives tasks based on actual completion and acceptance criteria rather than just updating a task.json status.

Does the session recording workflow require specific git commit artifacts?

Yes, the session recording workflow requires finalized git commit artifacts, applying specifically to end-of-session workflows where tasks and acceptance criteria are complete and changes have been committed.

Can I use this session archiving approach without a Trellis workspace?

No, session archiving requires a Trellis workspace because the workflow records data directly into .trellis workspace journal files and updates the index.md for future context loading.

What's the best way to maintain session indexes for workflow automation?

The best way to maintain session indexes is to run the record workflow at the end of sessions, which automatically updates index.md with totals, last active time, and line statistics for faster future context loading.