Skip to content
Back to skills

Bonfire Context

ASecurity

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.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 27, 2026
documentationgogitdocumentation

Security analysis

A100/100

Scanned September 27, 2026

npx -y skills add David-Li0406/meta-skill-evloving --skill bonfire-context --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Bonfire Context?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Bonfire Context
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/david-li0406-bonfire-context/badge)](https://www.skillsdirectory.com/skills/david-li0406-bonfire-context)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: bonfire-context
description: 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.
license: MIT
compatibility: opencode
metadata:
  category: session-management
  author: vieko
---

# 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`

2. Check if `.bonfire/index.md` exists at the git root

3. 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

4. Check `.bonfire/specs/` if the user asks about implementation specs

5. 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

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…