opencodekit 0.12.4 → 0.12.5

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

@@ -10,28 +10,17 @@ CI failures are P0 bugs. Fix fast.
 
 ## Get The Logs
 
-```bash
-# From URL: extract run ID from https://github.com/owner/repo/actions/runs/12345
-# From run ID: use directly
-gh run view $ARGUMENTS --log-failed
-```
+!`gh run view $ARGUMENTS --log-failed`
 
 List recent failures:
 
-```bash
-gh run list --status=failure --limit=5
-```
+!`gh run list --status=failure --limit=5`
 
 ## Extract The Error
 
-```bash
-# Find the failing step
-gh run view $ARGUMENTS --json jobs --jq '.jobs[] | select(.conclusion=="failure")'
+!`gh run view $ARGUMENTS --json jobs --jq '.jobs[] | select(.conclusion=="failure")'`
 
-# Get error context
-gh run view $ARGUMENTS --log > /tmp/ci-log.txt
-grep -i "error\|failed" /tmp/ci-log.txt | head -30
-```
+!`gh run view $ARGUMENTS --log > /tmp/ci-log.txt && grep -i "error\|failed" /tmp/ci-log.txt | head -30`
 
 Identify:
 
@@ -71,17 +60,7 @@ npm run build && npm test && npm run lint && npm run type-check
 
 ## Push And Watch
 
-```bash
-git add <files>
-git commit -m "fix(ci): [description]
-
-Root cause: [brief]"
-
-git push
-
-# Watch the new run
-gh run watch
-```
+!`gh run watch`
 
 ## If Still Failing
 
@@ -113,8 +92,8 @@ observation({
 
 ## Sync
 
-```typescript
-bd_sync({ reason: "Sync CI fix" });
+```bash
+bd sync
 ```
 
 ## Output

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

@@ -10,10 +10,8 @@ Resolve TypeScript errors without adding `any` everywhere.
 
 ## Get Current State
 
-```bash
-npx tsc --noEmit 2>&1 | head -50
-npx tsc --noEmit 2>&1 | grep -c "error TS"
-```
+!`npx tsc --noEmit 2>&1 | head -50`
+!`npx tsc --noEmit 2>&1 | grep -c "error TS"`
 
 ## Use LSP For Context
 
@@ -85,10 +83,8 @@ git commit -m "fix(types): resolve type errors
 
 - Fixed [N] errors
 - No 'any' types added"
-```
 
-```typescript
-bd_sync({ reason: "Sync type fixes" });
+bd sync
 ```
 
 ## Output

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

@@ -10,10 +10,8 @@ Fix visual issues. Capture before/after, verify responsiveness.
 
 ## Load Context
 
-```bash
-bd show $ARGUMENTS
-cat .beads/artifacts/$ARGUMENTS/spec.md 2>/dev/null
-```
+!`bd show $ARGUMENTS`
+!`cat .beads/artifacts/$ARGUMENTS/spec.md 2>/dev/null`
 
 ## Capture Before State
 
@@ -43,10 +41,8 @@ task({
 
 ## Check Design System
 
-```bash
-grep -r "var(--" src/styles/ | head -10
-grep -r "theme\." src/components/ | head -10
-```
+!`grep -r "var(--" src/styles/ | head -10`
+!`grep -r "theme\." src/components/ | head -10`
 
 Use existing tokens, not hardcoded values:
 
@@ -98,10 +94,8 @@ npm test -- --grep "component-name"
 ```bash
 git add <files>
 git commit -m "fix(ui): [description]"
-```
 
-```typescript
-bd_sync({ reason: "Sync UI fix" });
+bd sync
 ```
 
 ## Output

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

@@ -12,10 +12,8 @@ You're debugging and fixing an issue. Understand before you fix.
 
 If `$ARGUMENTS` is a bead ID:
 
-```bash
-bd show $ARGUMENTS
-cat .beads/artifacts/$ARGUMENTS/spec.md 2>/dev/null
-```
+!`bd show $ARGUMENTS`
+!`cat .beads/artifacts/$ARGUMENTS/spec.md 2>/dev/null`
 
 ## Parse The Error
 
@@ -55,9 +53,7 @@ skill({ name: "systematic-debugging" });
 
 Read error location. Trace data flow backward. Check recent changes:
 
-```bash
-git log -p --since="1 week ago" -- <file>
-```
+!`git log -p --since="1 week ago" -- <file>`
 
 Form a hypothesis. Write it down before fixing anything.
 
@@ -117,10 +113,8 @@ git commit -m "fix: [description]
 
 Root cause: [brief]
 $ARGUMENTS"
-```
 
-```typescript
-bd_sync({ reason: "Sync fix completion" });
+bd sync
 ```
 
 ## Output

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

@@ -22,24 +22,18 @@ Don't grind past diminishing returns. A clean handoff beats degraded output.
 
 Get current task status:
 
-```bash
-bd show $ARGUMENTS
-```
+!`bd show $ARGUMENTS`
 
 Get git state:
 
-```bash
-git remote get-url origin 2>/dev/null || echo "No remote"
-git branch --show-current
-git rev-parse --short HEAD
-git status --porcelain
-```
+!`git remote get-url origin 2>/dev/null || echo "No remote"`
+!`git branch --show-current`
+!`git rev-parse --short HEAD`
+!`git status --porcelain`
 
 Check what artifacts exist:
 
-```bash
-ls .beads/artifacts/$ARGUMENTS/ 2>/dev/null || echo "No artifacts yet"
-```
+!`ls .beads/artifacts/$ARGUMENTS/ 2>/dev/null || echo "No artifacts yet"`
 
 ## Commit Work In Progress
 
@@ -109,8 +103,8 @@ Start next session with: `/resume $ARGUMENTS`
 
 ## Sync State
 
-```typescript
-bd_sync();
+```bash
+bd sync
 ```
 
 This commits the handoff and pushes to remote.

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

@@ -18,16 +18,16 @@ skill({ name: "verification-before-completion" });
 
 Get the task details and check for messages:
 
-```bash
-bd show $ARGUMENTS
-bd list --status=in_progress  # See what else is active
+```
+!`bd show $ARGUMENTS`
+!`bd list --status=in_progress`  # See what else is active
 ```
 
 Check git state. If dirty, ask whether to stash, commit, or continue:
 
-```bash
-git status --porcelain
-git branch --show-current
+```
+!`git status --porcelain`
+!`git branch --show-current`
 ```
 
 Create a branch if not already on one for this task:
@@ -46,8 +46,8 @@ bd update $ARGUMENTS --status in_progress
 
 Check what context exists:
 
-```bash
-ls .beads/artifacts/$ARGUMENTS/ 2>/dev/null || echo "No artifacts"
+```
+!`ls .beads/artifacts/$ARGUMENTS/ 2>/dev/null || echo "No artifacts"`
 ```
 
 If `plan.md` exists, follow it step by step. If only `spec.md` exists, implement directly from requirements. If nothing exists, work from the bead description.
@@ -74,8 +74,8 @@ If you hit 80% of budget without finishing, create a handoff. Don't push past li
 
 Detect project type and know your verification commands:
 
-```bash
-ls package.json Cargo.toml pyproject.toml go.mod Makefile 2>/dev/null
+```
+!`ls package.json Cargo.toml pyproject.toml go.mod Makefile 2>/dev/null`
 ```
 
 Node/TypeScript: `npm test`, `npm run lint && npm run type-check`
@@ -97,8 +97,8 @@ Track your progress. Every 10 tool calls, check: Am I on track? Should I checkpo
 
 Verify against success criteria in the spec:
 
-```bash
-cat .beads/artifacts/$ARGUMENTS/spec.md | grep -A 20 "Success Criteria"
+```
+!`cat .beads/artifacts/$ARGUMENTS/spec.md | grep -A 20 "Success Criteria"`
 ```
 
 Run each verification command. All must pass. No exceptions.
@@ -117,10 +117,7 @@ If all gates pass:
 ```bash
 git add -A
 git commit -m "$ARGUMENTS: [summary]"
-```
-
-```typescript
-bd_sync({ reason: "Sync implementation progress" });
+bd sync
 ```
 
 Report what was done and suggest next step:

package/dist/template/.opencode/command/import-plan.md

@@ -30,8 +30,8 @@ Import a markdown plan into Beads epics and issues. Follows Steve Yegge's "plan
 
 Read the plan file:
 
-```bash
-read $ARGUMENTS
+```typescript
+read({ filePath: "$ARGUMENTS" });
 ```
 
 If file not found: "Plan file not found. Provide path to markdown plan."
@@ -42,9 +42,7 @@ If file not found: "Plan file not found. Provide path to markdown plan."
 
 Before importing, check for existing beads with similar titles:
 
-```typescript
-bd_ls({ status: "all", limit: 50, offset: 0 });
-```
+!`bd list --status all --limit 50`
 
 Compare plan titles against existing beads:
 
@@ -108,14 +106,8 @@ Proceed with import? (yes/modify/cancel)
 
 For each epic (top-level section):
 
-```typescript
-bd_add({
-  title: "[prefix][Epic title]",
-  type: "epic",
-  pri: 2,
-  desc: "[description from plan]",
-  tags: ["imported", ...inferred_tags],
-});
+```bash
+bd create "[prefix][Epic title]" -t epic -p 2
 ```
 
 Store epic IDs for dependency linking.
@@ -134,15 +126,9 @@ Creating epics... [3/3] ██████████ Settings ✓
 
 For each issue under an epic:
 
-```typescript
-bd_add({
-  title: "[Issue title]",
-  type: "<inferred-type>",
-  pri: <inferred-priority>,
-  desc: "[description]\n\nEstimate: [size]\nSource: [plan-file]",
-  parent: "<epic-id>",
-  tags: [...inferred_tags]
-});
+```bash
+bd create "[Issue title]" -t <inferred-type> -p <inferred-priority>
+# Then: bd dep add <issue-id> <epic-id>
 ```
 
 ### Type Inference
@@ -191,13 +177,9 @@ Detect from content and extract:
 
 For issues with dependencies, use the `deps` parameter:
 
-```typescript
-bd_add({
-  title: "[title]",
-  type: "task",
-  pri: 2,
-  deps: ["<blocking-issue-id>"],
-});
+```bash
+bd create "[title]" -t task -p 2
+bd dep add <issue-id> <blocking-issue-id>
 ```
 
 ### Dependency Patterns
@@ -236,10 +218,10 @@ Select option (1/2/3):
 
 Rollback implementation:
 
-```typescript
-// Delete in reverse order
-bd_update({ id: "bd-def456", status: "cancelled" });
-bd_update({ id: "bd-abc123", status: "cancelled" });
+```bash
+# Delete in reverse order
+bd update bd-def456 --status cancelled
+bd update bd-abc123 --status cancelled
 ```
 
 ---
@@ -279,8 +261,8 @@ Apply suggestions? (yes/no/select)
 
 If user approves suggestions, update the beads:
 
-```typescript
-bd_update({ id: "bd-abc123", title: "Implement JWT Authentication" });
+```bash
+bd update bd-abc123 --title "Implement JWT Authentication"
 ```
 
 Iterate up to 5 times if user requests more refinement.
@@ -309,9 +291,9 @@ Created:
 └── ...
 
 Next Steps:
-├── View ready tasks: bd_ls({ status: "ready" })
+├── View ready tasks: bd list --status ready
 ├── Start first task: /implement bd-task-001
-└── View dependencies: bd_dep({ action: "tree", child: "<id>" })
+└── View dependencies: bd dep tree <id>
 ```
 
 ---
@@ -399,4 +381,4 @@ Priority: high
 | Create plan from scratch | `/plan`                |
 | Execute imported plan    | `/implement <bead-id>` |
 | View plan status         | `/status`              |
-| Create single bead       | `bd_add()`             |
+| Create single bead       | `bd create`            |

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

@@ -19,7 +19,7 @@ Default: Standard research (~20-50 tool calls).
 
 Unless `--skip-questions`, ask in one message:
 
-1. **Identity**: "Which git contributor are you?" (show top 5 from `git shortlog -sn --all | head -5`)
+1. **Identity**: "Which git contributor are you?" (show top 5 from !`git shortlog -sn --all | head -5`)
 2. **Communication**: "Terse or detailed responses?"
 3. **Workflow**: "Auto-commit or ask-first?"
 4. **Rules**: "Any rules I should always follow?"
@@ -40,17 +40,15 @@ If skipped, infer identity from `git config user.name` and `git config user.emai
 
 ### Validate Commands
 
-```bash
-# Actually run detected commands to verify they work
-npm run build 2>&1 | head -5  # Check for errors
-npm test -- --help 2>&1 | head -3  # Verify test syntax
-```
+!`npm run build 2>&1 | head -5` # Check for errors
+!`npm test -- --help 2>&1 | head -3` # Verify test syntax
 
 ### With --deep
 
-- `git shortlog -sn --all | head -10` - contributors
-- `git log --format="%s" -50` - commit conventions
-- `git branch -a` - branching strategy
+!`git shortlog -sn --all | head -10` # contributors
+!`git log --format="%s" -50` # commit conventions
+!`git branch -a` # branching strategy
+
 - Source file analysis for patterns
 - Identify subsystems needing nested AGENTS.md
 
@@ -122,10 +120,7 @@ Good pattern (from your codebase):
 
 For projects with distinct subsystems, identify candidates for nested AGENTS.md:
 
-```bash
-# Find directories with significant code
-find . -type d -name "src" -o -name "packages" -o -name "apps" | head -10
-````
+!`find . -type d \( -name "src" -o -name "packages" -o -name "apps" \) | head -10`
 
 Suggest nested AGENTS.md for:
 
@@ -293,3 +288,4 @@ Suggested next steps:
 - ❌ Every possible command (context bloat)
 - ❌ Auto-generated content without review
 - ❌ Code snippets that go stale (use pointers)
+````

package/dist/template/.opencode/command/integration-test.md

@@ -42,12 +42,11 @@ skill({ name: "testing-anti-patterns" }); // Avoid common mistakes
 
 ## Phase 1: Task Validation
 
-```typescript
-// Check bead exists
-bd_show({ id: "$ARGUMENTS" });
+!`bd show $ARGUMENTS`
 
+```typescript
 // Read test constraints
-read(".beads/artifacts/$ARGUMENTS/spec.md");
+read({ filePath: ".beads/artifacts/$ARGUMENTS/spec.md" });
 ```
 
 If bead missing: STOP. Create with `/create` first.
@@ -56,15 +55,14 @@ If bead missing: STOP. Create with `/create` first.
 
 ## Phase 2: Framework Detection
 
-```bash
-# Detect test framework
-glob pattern="**/jest.config.*"
-glob pattern="**/vitest.config.*"
-glob pattern="**/pytest.ini"
-glob pattern="**/pyproject.toml"
-
-# Read package.json for test command
-read package.json
+```typescript
+glob({ pattern: "**/jest.config.*" });
+glob({ pattern: "**/vitest.config.*" });
+glob({ pattern: "**/pytest.ini" });
+glob({ pattern: "**/pyproject.toml" });
+
+// Read package.json for test command
+read({ filePath: "package.json" });
 ```
 
 | Framework | File Pattern             | Test Command |

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

@@ -10,17 +10,13 @@ You're importing a GitHub issue into beads for tracking.
 
 ## Check For Duplicates
 
-```bash
-bd list --status=all | grep -i "[keywords from issue]"
-```
+!`bd list --status=all | grep -i "[keywords from issue]"`
 
 If similar bead exists, link to it instead of creating duplicate.
 
 ## Fetch The Issue
 
-```bash
-gh issue view $ARGUMENTS --json title,body,labels,state
-```
+!`gh issue view $ARGUMENTS --json title,body,labels,state`
 
 Extract:
 
@@ -85,8 +81,8 @@ Next: [/implement or /research]"
 
 ## Sync
 
-```typescript
-bd_sync({ reason: "Sync imported issue" });
+```bash
+bd sync
 ```
 
 ## Output

package/dist/template/.opencode/command/new-feature.md

@@ -31,19 +31,16 @@ This skill provides Epic → Task → Subtask hierarchy for complex features.
 
 ## Phase 1: Context Gathering
 
-Before creating anything, understand the landscape:
+Before creating anything, understand of landscape:
 
-```bash
-# Check for related existing work
-bd_ls({ status: "all", limit: 20, offset: 0 })
+!`bd list --status all --limit 20`
 
 # Analyze codebase structure
-glob pattern="src/**/*.{ts,tsx,py}"
+
+glob pattern="src/\*_/_.{ts,tsx,py}"
 lsp_lsp_workspace_symbols({ query: "[relevant-terms]" })
 
-# Check recent changes in related areas
-git log --oneline -10 -- src/[relevant-path]/
-```
+!`git log --oneline -10 -- src/[relevant-path]/`
 
 **Report:**
 
@@ -113,14 +110,8 @@ Proceed with spec? (yes/modify/explore-more)
 
 ## Phase 3: Create Epic Bead
 
-```typescript
-bd_add({
-  title: "[Feature Name]",
-  type: "epic",
-  pri: [priority],
-  desc: "[Brief description from brainstorming]",
-  tags: ["feature", ...inferred_tags],
-});
+```bash
+bd create "[Feature Name]" -t epic -p [priority]
 ```
 
 Capture the bead ID for artifact creation.
@@ -363,28 +354,17 @@ If issues detected:
 
 Break phases into individual trackable beads:
 
-```typescript
-// Phase 1 tasks
-bd_add({
-  title: "Set up database schema for [feature]",
-  type: "task",
-  pri: 2,
-  parent: "<epic-id>",
-  desc: "Phase 1 of [feature]. Create tables and migrations.",
-  tags: ["backend", "database"],
-});
-
-// Phase 2 tasks (with dependency)
-bd_add({
-  title: "Implement [core feature]",
-  type: "task",
-  pri: 2,
-  parent: "<epic-id>",
-  deps: ["<phase-1-bead-id>"],
-  tags: ["backend"],
-});
-
-// Continue for all phases...
+```bash
+# Phase 1 tasks
+bd create "Set up database schema for [feature]" -t task -p 2
+bd dep add <task-id> <epic-id>
+
+# Phase 2 tasks (with dependency)
+bd create "Implement [core feature]" -t task -p 2
+bd dep add <task-id> <epic-id>
+bd dep add <task-id> <phase-1-bead-id>
+
+# Continue for all phases...
 ```
 
 ---
@@ -424,9 +404,9 @@ Sub-tasks created:
 Branch: feature/[feature-name] (if --branch)
 
 Next Steps:
-├── View feature: bd_show({ id: "[bead-id]" })
+├── View feature: bd show [bead-id]
 ├── Start first task: /implement [task-id-1]
-└── View ready work: bd_ls({ status: "ready" })
+└── View ready work: bd list --status ready
 ```
 
 ---

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

@@ -10,11 +10,9 @@ You're creating an implementation plan. Design first, then execute.
 
 ## Load Context
 
-```bash
-bd show $ARGUMENTS
-cat .beads/artifacts/$ARGUMENTS/spec.md
-cat .beads/artifacts/$ARGUMENTS/research.md 2>/dev/null
-```
+!`bd show $ARGUMENTS`
+!`cat .beads/artifacts/$ARGUMENTS/spec.md`
+!`cat .beads/artifacts/$ARGUMENTS/research.md 2>/dev/null`
 
 If spec.md missing: "Run `/create $ARGUMENTS` first."
 If complexity > M and no research: "Consider `/research $ARGUMENTS` first."
@@ -118,7 +116,7 @@ Verify: `npm test -- bar.test.ts`
 
 With `--create-beads` flag or user approval:
 
-```bash
+````bash
 # Task 1 (no blockers)
 bd create "[task 1 title]" -t task -p 2
 
@@ -126,17 +124,15 @@ bd create "[task 1 title]" -t task -p 2
 bd create "[task 2 title]" -t task -p 2
 bd dep add bd-[task2] bd-[task1] --type blocks
 
-# Visualize
-bd dep tree $ARGUMENTS
-```
+!`bd dep tree $ARGUMENTS`
 
 Update plan.md with bead IDs.
 
 ## Sync
 
-```typescript
-bd_sync({ reason: "Sync plan" });
-```
+```bash
+bd sync
+````
 
 ## Output