record-session

Append session summaries and commit hashes to repository journal files.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/SilentFlower/flower-cli --skill record-session-silentflower
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: record-session
Source: https://github.com/SilentFlower/flower-cli/tree/main/.agents/skills/record-session
Command: npx skills add https://github.com/SilentFlower/flower-cli --skill record-session-silentflower

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Captures and persists the outcome of a completed coding session so that human-tested and committed work is recorded in repository-maintained journals and developer index files, preventing loss of session context and improving future AI-assisted work.

Core Features & Use Cases

  • Session journaling: Append session summaries to journal files with automatic splitting when files grow large.
  • Commit linkage: Record one or more commit hashes and detect branch context to tie session notes to concrete code changes.
  • Index & workspace updates: Update index.md statistics, last-active timestamps, and .trellis workspace metadata and auto-commit those changes.
  • Task archiving: Archive tasks judged complete based on commit history and acceptance criteria to keep task lists accurate.
  • Use Case: After manually testing and committing a feature, run the record-session flow to add a summary, link the commits, and update the developer journal and indexes for future reference.

Quick Start

After committing and testing your code, run the record-session workflow to add a session title, provide commit hashes and a concise summary so the repository's .trellis journal and indexes are updated.

Frequently Asked Questions about record-session

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

FAQPage Schema
How do I record git commit metadata to a developer journal?

You can record git commit metadata by running this workflow after committing code, which appends session summaries, detects branch context, and links commit hashes to repository journal files.

What is a trellis workspace and how does it track session history?

A trellis workspace tracks session history by maintaining journal files and developer indexes inside a local git repository, automatically appending commit metadata and updating last-active timestamps after each session.

Does this session journaling workflow require local git repository access?

Yes, this session journaling workflow requires local git repository access because it reads git history to detect branch context and executes Python scripts under .trellis/scripts to append journal entries and update metadata.

How do I archive completed tasks based on git commit history?

You archive completed tasks by running the session recording workflow after human testing and commits, which evaluates commit history and acceptance criteria to judge tasks complete and automatically archives them in the task list.

Can I append multiple commit hashes to a single coding session summary?

Yes, you can append multiple commit hashes to a single coding session summary. The workflow records one or more commit hashes and detects branch context to tie your session notes to concrete code changes.