Skip to content

ginko log

Usage

ginko log [description] [options]

Description

Records an event to the current session log. Events are categorized and can include impact level and affected files. The session log builds a timeline of decisions, fixes, and discoveries that persists across sessions.

Options

Flag	Description
`-c, --category <category>`	Event category: `fix`, `feature`, `decision`, `insight`, `git`, `achievement`, `blocker`
`-i, --impact <impact>`	Impact level: `high`, `medium`, `low`
`-f, --files <files>`	Comma-separated list of affected files
`-s, --show`	Show current session log with quality score
`--validate`	Check session log quality
`--quick`	Skip interactive prompts
`--shared`	Mark event for team visibility

Examples

# Log a fix
ginko log "Fixed race condition in session cleanup" -c fix -i high

# Log a decision
ginko log -c decision "Chose bcrypt over argon2 for hashing"

# Log with affected files
ginko log "Refactored auth middleware" -f "src/auth.ts,src/middleware.ts"

# View session log
ginko log --show

# Quick log without prompts
ginko log "Updated docs" --quick

ginko start — Logs are loaded at session start
ginko health — Evaluates logging quality
ginko insights — Analyzes log patterns