ccbox-insightslisted

# ccbox-insights Use `ccbox` session logs to produce an evidence-based "lessons learned" memo for the agent (and humans), plus copy-ready instruction snippets that improve future sessions. Tool-call failures are an important signal, but the goal is broader than errors: capture what worked, what did not, and what should become standing behavior in the future. ## Requirements - `ccbox` on your `$PATH`. - Access to the local sessions directory scanned by `ccbox` (see `ccbox --help` if discovery looks empty). ## Quick start (single session) 1. Find the latest session for the current folder: ```bash ccbox sessions --limit 5 --offset 0 --size ``` 2. Inspect the latest session timeline (increase `--limit` if needed): ```bash ccbox history --full --limit 200 --offset 0 ``` ## Workflow (recommended) Follow a staged pipeline: collect -> filter -> summarize -> label -> aggregate -> synthesize -> propose instructions. ### Stage 0: Choose scope - **Session**: one `.jsonl` log for deep root-cause analysis. - **Project**: last N sessions for one project to find recurring failure patterns. - **Global**: a sample across projects to find cross-project patterns. ### Stage 1: Collect evidence with `ccbox` - Project discovery: `ccbox projects` - Session listing: `ccbox sessions [project-path] --limit N --offset 0 --size` - Timeline capture: `ccbox history [log-or-project] --full --limit N --offset 0` - Skill spans (optional): `ccbox skills [log-or-project] --json` When triaging qu