smithery.ai

bonfire-context

Load .bonfire/index.md context to understand ongoing work, previous decisions, blockers, and session history. Use when user references past work or asks about project status.

First seen Apr 4, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Declared

Skill metadata

Parsed from SKILL.md frontmatter.

LicenseMIT
Compatibilityopencode
Declared agents opencode
More metadata
category
session-management
author
vieko

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,775 B
  • docs SUMMARY.md 197 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Bonfire Context

This skill loads project session context from .bonfire/index.md to provide continuity across AI coding sessions.

When to Use This Skill

Load this skill when the user:

  • Asks about previous work or decisions
  • References "last time", "previously", "before"
  • Wants to know about blockers or pending issues
  • Asks what the project status is
  • Starts a significant task that might have prior context

Instructions

  1. Find the git root: git rev-parse --show-toplevel
  1. Check if .bonfire/index.md exists at the git root
  1. If it exists, read it to understand:

- Current project status and recent work - Active decisions and their rationale - Known blockers or pending issues - Links to relevant specs or documentation

  1. Check .bonfire/specs/ if the user asks about implementation specs
  1. Check .bonfire/docs/ if the user asks about documented topics

File Structure

.bonfire/
├── index.md          # Main session context (read this first)
├── config.json       # Project settings
├── archive/          # Completed work history
├── docs/             # Topic documentation
└── specs/            # Implementation specs

Important

  • This skill is for reading context, not updating it
  • Session updates happen via /bonfire-end command
  • Don't modify .bonfire/index.md unless explicitly asked
  • If .bonfire/ doesn't exist, the project may not use this pattern