opencodekit 0.2.0 → 0.2.1

package/dist/index.js

@@ -750,7 +750,7 @@ var cac = (name = "") => new CAC(name);
 // package.json
 var package_default = {
   name: "opencodekit",
-  version: "0.2.0",
+  version: "0.2.1",
   description: "CLI tool for bootstrapping and managing OpenCodeKit projects",
   type: "module",
   repository: {

package/dist/template/.opencode/command/analyze-project.md

@@ -1,5 +1,5 @@
 ---
-description: Analyze project structure and status
+description: Analyze project structure, status, and ready work
 agent: planner
 ---
 
@@ -12,6 +12,16 @@ agent: planner
 3. **CI:** Check build status
 4. **Dependencies:** Check for outdated packages
 
+## Ready Work
+
+Find actionable tasks with no blockers:
+
+```bash
+bd ready
+```
+
+This shows beads that are unblocked and ready to start. Use `/implement <bead-id>` to begin work on any of these.
+
 ## Detailed Analysis (On Request)
 
 ### Task Overview
@@ -23,6 +33,16 @@ bd ready
 
 For active beads, read spec from `.beads/artifacts/<bead-id>/spec.md`
 
+### Blocked Work
+
+Check what's blocking progress:
+
+```bash
+bd list --status blocked
+```
+
+For each blocked bead, identify the blocker and either resolve it or escalate.
+
 ### Project Structure
 
 - Key directories
@@ -33,7 +53,8 @@ For active beads, read spec from `.beads/artifacts/<bead-id>/spec.md`
 
 ### Recommendations
 
-- Tasks ready to start
-- Areas needing attention
-- Dependency updates needed
-- Code patterns to follow
+- **Immediate:** Tasks from `bd ready` to start now
+- **Blocked:** Dependencies preventing progress
+- **Attention:** Areas needing cleanup or refactoring
+- **Updates:** Dependency updates needed
+- **Patterns:** Code patterns to follow

package/dist/template/.opencode/command/commit.md

@@ -1,11 +1,39 @@
 ---
-description: Commit with verification
+description: Commit with verification and optional bead traceability
+argument-hint: "[bead-id]"
 ---
 
 # Commit
 
 use_skill("verification-before-completion")
 
+## Workflow
+
 1. Run all tests/lints
 2. Verify output shows success
-3. Then commit with conventional message format
+3. Commit with conventional message format
+
+## Bead Integration (Optional)
+
+If a bead ID is provided (`$ARGUMENTS`), include it in the commit message for traceability:
+
+```
+<type>(<scope>): <description>
+
+<bead-id>: <what was done for this bead>
+
+[optional body]
+```
+
+**Example:**
+
+```
+feat(auth): add OAuth2 login flow
+
+bd-a1b2c3: implement token refresh mechanism
+
+- Added refresh token storage
+- Integrated with session manager
+```
+
+If no bead ID is provided, proceed with standard conventional commit format.

package/dist/template/.opencode/command/fix-ci.md

@@ -1,5 +1,5 @@
 ---
-description: Analyze Github Actions logs and fix issues
+description: Analyze Github Actions logs and fix issues with bead tracking
 argument-hint: "[github-actions-url]"
 ---
 
@@ -7,14 +7,41 @@ argument-hint: "[github-actions-url]"
 
 <url>$ARGUMENTS</url>
 
+## Create Bug Bead
+
+CI failures are P0 bugs. Create a bead to track:
+
+```bash
+bd create --title "Fix CI: <failure summary>" --type bug --priority p0 --json
+```
+
+Save the bead ID for tracking. Add the CI run reference:
+
+```bash
+bd edit <bead-id> --note "CI Run: $ARGUMENTS"
+```
+
 ## Workflow
 
-- Use `build` agent to read the GitHub Actions logs, analyze and find the root causes of the issues.
-- For complex CI/CD problems (≥3 phases), delegate to `planner` agent to create a detailed implementation plan.
-- Use `build` agent to implement the fixes step by step.
-- Use `review` agent to run tests, ensure quality and security, then report back.
-- If there are issues or failed tests, `build` agent will fix them and repeat the process until all tests pass.
+1. **Analyze:** Use `build` agent to read the GitHub Actions logs, analyze and find the root causes of the issues.
+
+2. **Plan:** For complex CI/CD problems (≥3 phases), delegate to `planner` agent to create a detailed implementation plan. Save plan to `.beads/artifacts/<bead-id>/spec.md`.
+
+3. **Fix:** Use `build` agent to implement the fixes step by step.
+
+4. **Verify:** Use `review` agent to run tests, ensure quality and security, then report back.
+
+5. **Iterate:** If there are issues or failed tests, `build` agent will fix them and repeat the process until all tests pass.
+
+## Close Bead
+
+Once CI passes:
+
+```bash
+bd close <bead-id> --reason "CI fixed: <summary of fix>"
+```
 
 ## Notes
 
 - If `gh` command is not available, instruct the user to install and authorize GitHub CLI first.
+- If the fix reveals systemic issues, create related beads for follow-up work.

package/dist/template/.opencode/command/fix-types.md

@@ -1,10 +1,35 @@
 ---
-description: Fix type errors
+description: Fix type errors with optional bead tracking
+argument-hint: "[bead-id]"
 ---
 
+# Fix Type Errors
+
 Run `bun run typecheck` and fix all type errors.
 
 ## Rules
 
-- Fix all of type errors and repeat the process until there are no more type errors.
-- Do not use `any` just to pass the type check.
+- Fix all type errors and repeat the process until there are no more type errors.
+- Do not use `any` just to pass the type check.
+- Prefer proper typing over type assertions where possible.
+
+## Bead Integration (Optional)
+
+If a bead ID is provided (`$ARGUMENTS`), track the type fixing work:
+
+1. **Before fixing:** Note the initial error count
+
+   ```bash
+   bd edit $ARGUMENTS --note "Type errors found: <count>"
+   ```
+
+2. **After fixing:** Update with resolution
+   ```bash
+   bd edit $ARGUMENTS --note "Type errors resolved: <summary of fixes>"
+   ```
+
+If type errors reveal deeper issues requiring refactoring, create a follow-up bead:
+
+```bash
+bd create --title "Refactor: <type issue summary>" --type task --related $ARGUMENTS
+```

package/dist/template/.opencode/command/issue.md

@@ -1,5 +1,5 @@
 ---
-description: Analyze GitHub issue and create implementation plan
+description: Analyze GitHub issue and create bead for tracking
 argument-hint: "[issue-number]"
 agent: build
 ---
@@ -19,8 +19,24 @@ gh issue view $ARGUMENTS
 3. **Current:** What happens now?
 4. **Steps:** How to reproduce?
 
+## Create Tracking Bead
+
+Create a bead to track this work, linking it to the GitHub issue:
+
+```bash
+bd create --title "<issue title>" --type task --priority <p1|p2|p3> --json
+```
+
+Save the bead ID for subsequent commands. Add the GitHub issue reference:
+
+```bash
+bd edit <bead-id> --note "GitHub issue: #$ARGUMENTS"
+```
+
 ## Implementation Plan
 
+Save to `.beads/artifacts/<bead-id>/spec.md`:
+
 1. **Files to change:** Identify affected code
 2. **Testing strategy:** How to verify fix
 3. **Risks/edge cases:** What could go wrong
@@ -38,4 +54,12 @@ gh issue view $ARGUMENTS
 - [ ] Test cases to verify
 - [ ] Performance considerations
 
-**Next:** Start implementing the planned solution.
+## Discovered Work
+
+If analysis reveals additional issues, create child beads:
+
+```bash
+bd create --title "<discovered issue>" --type discovered --parent <parent-bead-id>
+```
+
+**Next:** Use `/implement <bead-id>` to start implementation.

package/dist/template/.opencode/command/pr.md

@@ -1,5 +1,6 @@
 ---
-description: Create and submit pull request with proper formatting
+description: Create and submit pull request with bead traceability
+argument-hint: "[bead-id]"
 ---
 
 ## Create Pull Request
@@ -14,13 +15,18 @@ Create a pull request following these steps:
 
 2. **Push branch**: `!git push -u origin $(git branch --show-current)`
 
-3. **Generate PR content:**
+3. **Check for bead context:**
+   - If `$ARGUMENTS` contains a bead ID, fetch bead details: `bd show $ARGUMENTS --json`
+   - Use bead title and spec to inform PR content
+   - Reference the bead in the PR body for traceability
+
+4. **Generate PR content:**
    - Title: Clear, descriptive (under 60 chars)
    - Summary: What and why this change matters
    - Testing: How to verify the changes
    - Breaking changes: Note any API/behavior changes
 
-4. **Create PR**: `!gh pr create --title "Generated Title" --body "Generated Description"`
+5. **Create PR**: `!gh pr create --title "Generated Title" --body "Generated Description"`
 
 **Template format:**
 
@@ -28,9 +34,20 @@ Create a pull request following these steps:
 ## Summary
 - Brief description of changes
 
+## Bead Reference
+Closes: bd-XXXXX (if applicable)
+
 ## Testing
 - How to test these changes
 
 ## Breaking Changes
 - None / List any breaking changes
 ```
+
+## After PR Created
+
+If a bead ID was provided, update the bead with PR link:
+
+```bash
+bd edit $ARGUMENTS --note "PR created: <pr-url>"
+```

package/dist/template/.opencode/command/research-ui.md

@@ -1,6 +1,6 @@
 ---
-description: Large-scale UI/UX research using Gemini CLI
-argument-hint: "[research topic or path]"
+description: Large-scale UI/UX research using Gemini CLI with bead artifact storage
+argument-hint: "[bead-id] [research topic or path]"
 agent: review
 ---
 
@@ -9,6 +9,10 @@ agent: review
 use_skill("gemini-large-context")
 use_skill("ui-ux-research")
 
+## Parse Arguments
+
+Extract bead ID (if provided) and research topic from `$ARGUMENTS`. If no bead ID provided, research findings will be saved to memory instead.
+
 ## When to Use Gemini CLI
 
 For a single component, use local tools—they're faster and sufficient. When researching patterns across multiple files or comparing implementations throughout a codebase, switch to Gemini CLI's non-interactive mode to scan entire directories at once. For analyzing images like mockups or screenshots, start Gemini in interactive mode and reference the image directly.
@@ -19,9 +23,21 @@ Point Gemini at the relevant directories and ask about the topic. Include both c
 
 For image analysis, start interactive mode and reference the image file, then describe what aspects you want analyzed.
 
-## What to Do With Findings
+## Save Findings
+
+### With Bead ID
+
+Save research findings to bead artifacts for traceability:
+
+```bash
+# Save to .beads/artifacts/<bead-id>/research-ui.md
+bd edit <bead-id> --note "UI research completed: <key findings summary>"
+```
+
+### Without Bead ID
 
-Synthesize the key patterns you discovered, note any inconsistencies between different parts of the codebase, and formulate concrete recommendations. Save significant findings to `.opencode/memory/research/YYYY-MM-DD-$ARGUMENTS.md` using the research template.
+Save to memory for general reference:
+`.opencode/memory/research/YYYY-MM-DD-<topic>.md`
 
 ## Common Research Topics
 

package/dist/template/.opencode/command/ui-review.md

@@ -1,6 +1,6 @@
 ---
-description: Review UI/UX design or mockup
-argument-hint: "[path to image or component]"
+description: Review UI/UX design or mockup with optional bead tracking
+argument-hint: "[bead-id] [path to image or component]"
 agent: review
 ---
 
@@ -9,6 +9,10 @@ agent: review
 use_skill("ui-ux-research")
 use_skill("frontend-aesthetics")
 
+## Parse Arguments
+
+Extract bead ID (if provided) and path/component from `$ARGUMENTS`. If a bead ID is present, findings will be recorded to the bead.
+
 ## How to Analyze
 
 First, determine what you're reviewing. If it's an image or screenshot, start Gemini in interactive mode and reference the image to analyze it. If it's component code, analyze it directly with local tools. For large codebases spanning many files, use Gemini's non-interactive mode to scan the entire directory.
@@ -23,6 +27,26 @@ For accessibility, verify color contrast meets WCAG AA minimum, check for ARIA l
 
 Provide specific, actionable improvements: suggest alternative fonts, propose color palette changes, identify opportunities for subtle animations, and recommend layout enhancements. Include code snippets when they would help clarify the suggestion.
 
+## Record Findings
+
+### With Bead ID
+
+Update the bead with review findings:
+
+```bash
+bd edit <bead-id> --note "UI Review: <summary of issues found and recommendations>"
+```
+
+If review reveals implementation tasks, create child beads:
+
+```bash
+bd create --title "<specific UI fix>" --type task --parent <bead-id>
+```
+
+### Without Bead ID
+
+Output findings directly to the user.
+
 ## Output
 
 Summarize what issues you found, what specific changes you recommend, and show before/after comparisons for significant improvements.

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "opencodekit",
-	"version": "0.2.0",
+	"version": "0.2.1",
 	"description": "CLI tool for bootstrapping and managing OpenCodeKit projects",
 	"type": "module",
 	"repository": {