opencode-bonfire 1.0.0 → 1.1.1

package/files/agent/work-reviewer.md

@@ -55,21 +55,29 @@ You'll receive:
 
 ## Output Format
 
-Return findings as structured markdown, categorized by action:
+Return findings as structured markdown with a clear verdict at the top:
 
 ```markdown
+## Verdict: APPROVE | CONDITIONAL | BLOCK
+
+**Reason**: [One-line explanation of verdict]
+
+---
+
 ## Summary
 
 - **Total findings**: X
-- **Fix now (trivial)**: Y
-- **Needs spec**: Z
-- **Create issues**: W
+- **Critical**: N (blocks)
+- **Important**: N (blocks)
+- **Moderate**: N (conditional)
+- **Minor**: N (approve)
 
 ---
 
 ## Fix Now (trivial effort, do immediately)
 
 ### [Finding title]
+- **Severity**: Critical | Important | Moderate | Minor
 - **What**: [Description]
 - **Where**: `path/to/file.ts:123`
 - **Fix**: [Specific action]
@@ -80,6 +88,7 @@ Return findings as structured markdown, categorized by action:
 ## Needs Spec (important, needs planning)
 
 ### [Finding title]
+- **Severity**: Critical | Important | Moderate | Minor
 - **What**: [Description]
 - **Effort**: small | medium
 - **Impact**: [Why this matters]
@@ -90,6 +99,7 @@ Return findings as structured markdown, categorized by action:
 ## Create Issues (large effort or nice-to-have)
 
 ### [Finding title]
+- **Severity**: Moderate | Minor
 - **What**: [Description]
 - **Effort**: medium | large
 - **Priority**: important | nice-to-have
@@ -97,11 +107,35 @@ Return findings as structured markdown, categorized by action:
 
 ---
 
+## Verdict Rationale
+
+[Brief explanation of why this verdict was reached and key items to address]
+
+---
+
 ## No Issues Found In
 
 - [Area reviewed that looks good]
 ```
 
+## Verdict Rules
+
+Determine verdict based on highest severity finding:
+
+1. **BLOCK** - Any Critical or Important findings exist
+   - Must address before proceeding
+   - Work is not ready to ship
+
+2. **CONDITIONAL** - Only Moderate findings exist
+   - Proceed with awareness
+   - Should address soon but not blocking
+
+3. **APPROVE** - Only Minor findings (or none)
+   - Safe to proceed
+   - Minor items can be addressed later
+
+**Always state the verdict clearly at the top. Do not bury it.**
+
 ## Rules
 
 1. **Strategic, not pedantic** - Skip style nitpicks, focus on substance
@@ -113,12 +147,12 @@ Return findings as structured markdown, categorized by action:
 
 ## Severity Guide
 
-| Severity | Definition | Action |
-|----------|------------|--------|
-| Critical | Breaks functionality, security issue | Fix now |
-| Important | Significant gap, will cause problems | Fix now or spec |
-| Moderate | Should address, not urgent | Spec or issue |
-| Minor | Nice to have, low impact | Issue or skip |
+| Severity | Definition | Verdict Impact | Action |
+|----------|------------|----------------|--------|
+| **Critical** | Breaks functionality, security issue, data loss | BLOCK | Fix now |
+| **Important** | Significant gap, will cause problems later | BLOCK | Fix now or spec |
+| **Moderate** | Should address, not urgent | CONDITIONAL | Spec or issue |
+| **Minor** | Nice to have, low impact | APPROVE | Issue or skip |
 
 ## Effort Guide
 

package/files/command/bonfire-configure.md

@@ -94,3 +94,4 @@ Report:
 - Settings updated
 - Any manual steps needed (git cleanup)
 - New configuration summary
+- Note: Context preservation during compaction is automatic (handled by Bonfire plugin hooks)

package/files/command/bonfire-end.md

@@ -29,7 +29,46 @@ Update `<git-root>/.bonfire/index.md`:
 
 3. Update "Current State" to reflect new status
 
-## Step 4: Commit Changes (if tracked)
+## Step 4: Update Codemap
+
+Update the "Codemap" section in `index.md` with files referenced this session:
+
+1. **Identify key files** from this session:
+   - Files you read or edited
+   - Files mentioned in commits
+   - Files central to the work done
+
+2. **Update "This Session's Key Files"**:
+   - List up to 10 most relevant files
+   - Include brief description of what each does
+   - Format: `- \`path/to/file.ts\` - Brief description`
+
+3. **Preserve user-curated sections**:
+   - Keep "Entry Points" as-is (user maintains these)
+   - Keep "Core Components" as-is (user maintains these)
+
+4. **Keep it concise**:
+   - Only include files directly relevant to session work
+   - Remove stale entries from previous sessions
+   - Max 10 files in "This Session's Key Files"
+
+Example:
+```markdown
+## Codemap
+
+**Entry Points** (user-curated):
+- `src/index.ts` - Main entry
+
+**Core Components** (user-curated):
+- `src/commands/` - CLI commands
+
+**This Session's Key Files** (auto-updated):
+- `claude/commands/configure.md` - Added PreCompact hook setup
+- `claude/commands/end.md` - Added Codemap update step
+- `.bonfire/specs/codemap-feature.md` - Feature specification
+```
+
+## Step 5: Commit Changes (if tracked)
 
 Read `<git-root>/.bonfire/config.json` to check `gitStrategy`.
 
@@ -52,7 +91,7 @@ Read `<git-root>/.bonfire/config.json` to check `gitStrategy`.
 
 If the commit fails due to hooks, help resolve the issue (but never bypass hooks with `--no-verify`).
 
-## Step 5: Confirm
+## Step 6: Confirm
 
 Summarize:
 - What was documented

package/files/command/bonfire-start.md

@@ -112,6 +112,19 @@ Check if `<git-root>/.bonfire/index.md` exists.
 
    ---
 
+   ## Codemap
+
+   **Entry Points** (user-curated):
+   - [Add main entry points here]
+
+   **Core Components** (user-curated):
+   - [Add key directories/modules here]
+
+   **This Session's Key Files** (auto-updated):
+   - [Files will be added by /bonfire-end]
+
+   ---
+
    ## Archived Sessions
 
    [Links to archived sessions will appear here]

package/files/opencode.json

@@ -1,4 +1,12 @@
 {
   "$schema": "https://opencode.ai/config.json",
-  "instructions": ["CLAUDE.md", ".bonfire/index.md"]
+  "instructions": ["CLAUDE.md", ".bonfire/index.md"],
+  "skill": [
+    {
+      "directory": "skill/bonfire-context"
+    },
+    {
+      "directory": "skill/archive-bonfire-awareness"
+    }
+  ]
 }

package/files/plugin/bonfire-hooks.ts

@@ -2,8 +2,11 @@
  * Bonfire Plugin for OpenCode
  *
  * Provides event hooks for:
- * - Suggesting archive after PR merge
+ * - Suggesting archive after PR merge (backup to skill-based detection)
  * - Preserving session context during compaction
+ * 
+ * Note: Archive suggestion also handled by archive-bonfire-awareness skill
+ * for better reliability across different OpenCode versions.
  */
 
 import type { Plugin } from "@opencode-ai/plugin"
@@ -30,6 +33,9 @@ export const BonfirePlugin: Plugin = async ({ directory }) => {
       const succeeded = !output.error && output.result
 
       if (isPrMerge && succeeded && existsSync(indexPath)) {
+        // Log for debugging - remove this once hook display is confirmed working
+        console.log("[Bonfire] PR merge detected, suggesting archive")
+        
         return {
           message: `PR merged! Run \`/bonfire-archive\` to archive this session.`,
         }

package/files/skill/archive-bonfire-awareness/SKILL.md

@@ -0,0 +1,62 @@
+---
+name: Archive Bonfire Awareness
+model: anthropic/claude-haiku-4-20250514
+mode: task
+hidden: true
+tools:
+  - bash
+  - read
+  - glob
+permission:
+  task:
+    "*": deny
+---
+
+# Archive Bonfire Awareness
+
+This skill detects when session work may be ready for archiving and suggests the appropriate action.
+
+## When to Use This Skill
+
+Trigger when:
+- User asks to merge: "merge it", "merge the PR", "go ahead and merge", "ship it"
+- After you successfully run `gh pr merge`
+- User mentions completion: "PR merged", "shipped", "done with X", "finished"
+- User references merged state: "merged to main", "closed the issue"
+
+## Instructions
+
+1. If user asks to merge a PR:
+   - Perform the merge as requested
+   - On success, continue to step 2
+   - On failure, help resolve the issue (don't suggest archiving)
+
+2. Find git root and check if `.bonfire/index.md` exists
+
+3. If it exists, read it to assess work state
+
+4. If user provided a PR URL/number (or you just merged one), verify status:
+   ```
+   gh pr view [URL/number] --json state,mergedAt,title
+   ```
+
+5. Assess if work appears complete:
+   - PR merged?
+   - Related tasks marked done in session notes?
+   - No obvious follow-up work mentioned?
+
+6. If work appears complete, suggest archiving:
+   > "PR merged successfully. This session's work looks complete - want me to archive it?
+   > Run `/bonfire-archive` to move completed work to the archive."
+
+7. If there's more work in the session:
+   > "PR merged. I see there's still [X, Y] in the session notes - want to continue
+   > with those or archive what's done so far?"
+
+## Important
+
+- This skill **suggests** archiving, it does NOT archive automatically
+- User must explicitly run `/bonfire-archive` to perform the archive
+- Trigger AFTER merge succeeds, not before
+- Multiple PRs may be part of one logical session - check context
+- If `.bonfire/` doesn't exist, don't suggest archiving

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-bonfire",
-  "version": "1.0.0",
+  "version": "1.1.1",
   "description": "OpenCode forgets everything between sessions. Bonfire remembers.",
   "type": "module",
   "bin": {