record-session

To save coding session context for future AI work, automate persisting session data by recording summaries and commit references into Trellis journal files. This ensures future AI sessions have the historical context of completed work.

Track developer progress after a git commit by running Python scripts under .trellis/scripts to read git history and generate journal entries. This updates .trellis/workspace indexes with commit references and session summaries.

Yes, you need to commit your code before recording a session. The workflow reads git history to capture commit hashes and applies after developers complete a coding session and commit changes to the repository.

Trellis journaling works by using Python scripts under .trellis/scripts to read git history and generate journal entries in .trellis/workspace. It captures session summaries, commit hashes, and updates developer index files for archival search.

Yes, you can search historical coding sessions in Trellis. The Skill enables archival search and impact tracking by updating .trellis/workspace indexes with session summaries, commit hashes, and developer index files.

Limitations include requiring access to the repository root and depending on Python scripts under .trellis/scripts. It applies only after code commits and human testing, not during active uncommitted development.