record-session

To automatically record git commit history into a development journal, this skill extracts context from your git history to create session entries with titles, commit hashes, and summaries, then appends them to your journal and updates the index.

Logging daily coding sessions after testing and committing code is best handled by automating the extraction of commit references and summaries into a session entry, which preserves a verifiable history of your feature work and completed tasks.

To archive completed tasks and clean up your project workflow automatically, this skill marks finished items as archived after recording your code commits, maintaining a clean task history alongside your updated journal entries.

This session recording workflow can extract project context using both git history and Trellis data, identifying work items ready for recording without requiring additional external dependencies beyond your existing project state.

Yes, you can create a session entry by running a script with a title, commit hashes, and a concise summary, which automatically logs the new session, appends it to the journal, and updates the index.