vieko/bonfire

Overview

This skill provides session context persistence for AI coding sessions so your assistant remembers past decisions, progress, and blockers. It lets you start and end sessions, create outcome specs and documentation, and run reviews that reference previous work. Use it to keep a continuous record across interactions and restore context on demand.

How this skill works

When you start a session, the skill ensures a .bonfire workspace exists and loads the session index to provide context. It saves outcomes, specs, and docs into the .bonfire directory and updates the index when you end the session. For queries about "last time" or previous decisions, it reads the session index and summarizes relevant context so the assistant can answer with continuity.

When to use it

• Begin a focused coding session and persist context across multiple conversations.
• Capture outcome specs before implementing features or fixes.
• Generate or update documentation tied to a specific session.
• Review current branch or recent work and find blindspots.
• Ask about previous decisions, blockers, or "what we decided" without re-explaining everything.

Best practices

• Start every focused effort with /bonfire start so context is recorded from the beginning.
• Write concise outcome specs with the /bonfire spec command to guide implementation and reviews.
• End sessions with /bonfire end to record accomplishments and run the health check.
• Use the review command to surface severity-graded findings and decide whether to fix or create tickets.
• Configure git strategy and doc/spec locations up front to match your repo workflow.

Example use cases

• Start a bug-fix session, run tests, document findings, and end the session with a summary of changes.
• Create an outcome spec for a new feature, iterate on code, and use the review flow to identify blindspots.
• Ask "what did we decide last time about the logging approach?" and get a summary from session context.
• Generate or update API docs for a component after implementing changes in the same session.
• Run a health check at session end to detect accidental or sensitive file changes before commit.