opencodekit 0.12.4 → 0.12.6

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
 

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

@@ -22,18 +22,18 @@ skill({ name: "verification-before-completion" });
 
 Before creating PR, run verification gates:
 
-```bash
-git status --porcelain  # Check for uncommitted changes
+```
+!`git status --porcelain`  # Check for uncommitted changes
 ```
 
 If uncommitted changes exist, ask: "Commit these changes first?"
 
 Run project gates:
 
-```bash
-npm run build 2>&1 | tail -5
-npm test 2>&1 | tail -10
-npm run lint 2>&1 | tail -5
+```
+!`npm run build 2>&1 | tail -5`
+!`npm test 2>&1 | tail -10`
+!`npm run lint 2>&1 | tail -5`
 ```
 
 ```
@@ -55,16 +55,16 @@ Fix errors first, then run /pr again.
 
 ## Phase 2: Check for Conflicts
 
-```bash
-git fetch origin main
-git merge-base --is-ancestor origin/main HEAD || git diff origin/main...HEAD --name-only
+```
+!`git fetch origin main`
+!`git merge-base --is-ancestor origin/main HEAD || git diff origin/main...HEAD --name-only`
 ```
 
 Check for merge conflicts:
 
-```bash
-git merge --no-commit --no-ff origin/main 2>&1 || true
-git merge --abort 2>/dev/null || true
+```
+!`git merge --no-commit --no-ff origin/main 2>&1 || true`
+!`git merge --abort 2>/dev/null || true`
 ```
 
 If conflicts detected:
@@ -84,24 +84,24 @@ Resolve conflicts before creating PR:
 
 **Current state:**
 
-```bash
-git branch --show-current
-git diff main...HEAD --stat
-git log main...HEAD --oneline
+```
+!`git branch --show-current`
+!`git diff main...HEAD --stat`
+!`git log main...HEAD --oneline`
 ```
 
 **Load bead context (if provided):**
 
-```typescript
-bd_show({ id: "$ARGUMENTS" });
+```
+!`bd show $ARGUMENTS`
 ```
 
 **Load artifacts:**
 
-```bash
-ls .beads/artifacts/<bead-id>/ 2>/dev/null
-cat .beads/artifacts/<bead-id>/spec.md 2>/dev/null | head -30
-cat .beads/artifacts/<bead-id>/review.md 2>/dev/null | head -30
+```
+!`ls .beads/artifacts/<bead-id>/ 2>/dev/null`
+!`cat .beads/artifacts/<bead-id>/spec.md 2>/dev/null | head -30`
+!`cat .beads/artifacts/<bead-id>/review.md 2>/dev/null | head -30`
 ```
 
 Extract from artifacts:
@@ -122,7 +122,7 @@ git push -u origin $(git branch --show-current)
 Generate PR content from context:
 
 ```bash
-gh pr create --title "<title>" --body "$(cat <<'EOF'
+gh pr create --title "<title>" --body "$(cat <<'EOF'  # Keep as instructional (multi-line)
 ## Summary
 
 [1-2 sentence description of what this PR does and why]
@@ -179,13 +179,13 @@ EOF
 **For draft PRs (--draft):**
 
 ```bash
-gh pr create --draft --title "<title>" --body "..."
+gh pr create --draft --title "<title>" --body "..."  # Keep as-is (instructional)
 ```
 
 ## Phase 6: Wait for CI (if --wait)
 
-```bash
-gh pr checks --watch
+```
+!`gh pr checks --watch`
 ```
 
 Report CI status:
@@ -204,18 +204,9 @@ CI Status:
 
 ## Phase 7: Update Bead & Sync
 
-```typescript
-bd_msg({
-  subj: "PR created",
-  body: "PR: <pr-url>\nStatus: [ready/draft]\nCI: [passing/pending]",
-  to: "all",
-  importance: "normal",
-  global: true,
-});
-```
-
-```typescript
-bd_sync({ reason: "Sync PR creation" });
+```bash
+bd-msg --subj "PR created" --body "PR: <pr-url>\nStatus: [ready/draft]\nCI: [passing/pending]" --to "all" --importance normal
+bd sync
 ```
 
 ## Output

package/dist/template/.opencode/command/quick-build.md

@@ -56,10 +56,7 @@ Fast path for trivial tasks. Skip ceremony, keep safety.
 
 ### Step 1: Verify Scope (30 seconds)
 
-```bash
-# Check what files might be involved
-grep -r "[search-term]" src/ --include="*.{ts,tsx}" -l | head -5
-```
+!`grep -r "[search-term]" src/ --include="*.{ts,tsx}" -l | head -5`
 
 If more than 1 file: **STOP** → Use `/create $ARGUMENTS` instead.
 
@@ -68,11 +65,10 @@ If more than 1 file: **STOP** → Use `/create $ARGUMENTS` instead.
 ```bash
 # Stash any existing changes
 git stash push -m "pre-quickbuild-$(date +%s)" 2>/dev/null || true
-
-# Note current commit
-git rev-parse HEAD
 ```
 
+!`git rev-parse HEAD`
+
 ### Step 3: Make the Change
 
 ```bash

package/dist/template/.opencode/command/research-and-implement.md

@@ -12,10 +12,8 @@ Use this for features with unknowns. For simple changes, use `/fix` or `/impleme
 
 ## Phase 1: Context
 
-```bash
-bd show $ARGUMENTS
-cat .beads/artifacts/$ARGUMENTS/spec.md
-```
+!`bd show $ARGUMENTS`
+!`cat .beads/artifacts/$ARGUMENTS/spec.md`
 
 If no spec exists: "Run `/create $ARGUMENTS` first."
 
@@ -123,8 +121,8 @@ git add -A
 git commit -m "$ARGUMENTS: [summary]"
 ```
 
-```typescript
-bd_sync({ reason: "Sync research and implementation" });
+```bash
+bd sync
 ```
 
 ```

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

@@ -16,10 +16,15 @@ You're gathering information before implementation. Find answers, document findi
 
 ## Load Context
 
-```bash
-bd show $ARGUMENTS
-cat .beads/artifacts/$ARGUMENTS/spec.md
-```
+!`bd show $ARGUMENTS`
+!`cat .beads/artifacts/$ARGUMENTS/spec.md`
+
+Extract questions that need answering from spec.
+
+## Check For Previous Research
+
+!`search_session({ query: "[topic keywords]" })`
+!`list_sessions({ project: "current", since: "this week", limit: 5 })`
 
 Extract the questions that need answering from the spec.
 
@@ -138,9 +143,7 @@ Write `.beads/artifacts/$ARGUMENTS/research.md`:
 
 ## Sync
 
-```typescript
-bd_sync({ reason: "Sync research findings" });
-```
+!`bd sync`
 
 ## Output
 

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

@@ -16,19 +16,15 @@ skill({ name: "beads" });
 
 ## Verify The Task Exists
 
-```bash
-bd show $ARGUMENTS
-```
+!`bd show $ARGUMENTS`
 
 If not found, check `bd list --status=all`. Maybe it was closed, or you have the wrong ID.
 
 ## Check Git State
 
-```bash
-git branch --show-current
-git rev-parse --short HEAD
-git status --porcelain
-```
+!`git branch --show-current`
+!`git rev-parse --short HEAD`
+!`git status --porcelain`
 
 If you're not on the right branch:
 
@@ -40,15 +36,11 @@ If there are uncommitted changes, decide: stash, commit, or discard.
 
 ## Find The Handoff
 
-```bash
-ls -t .beads/artifacts/$ARGUMENTS/handoffs/ 2>/dev/null | head -1
-```
+!`ls -t .beads/artifacts/$ARGUMENTS/handoffs/ 2>/dev/null | head -1`
 
 If a handoff exists, read it:
 
-```bash
-cat .beads/artifacts/$ARGUMENTS/handoffs/[latest].md
-```
+!`cat .beads/artifacts/$ARGUMENTS/handoffs/[latest].md`
 
 The handoff tells you:
 
@@ -83,20 +75,16 @@ Extract from session:
 
 Read all available context:
 
-```bash
-cat .beads/artifacts/$ARGUMENTS/spec.md 2>/dev/null
-cat .beads/artifacts/$ARGUMENTS/plan.md 2>/dev/null
-cat .beads/artifacts/$ARGUMENTS/research.md 2>/dev/null
-```
+!`cat .beads/artifacts/$ARGUMENTS/spec.md 2>/dev/null`
+!`cat .beads/artifacts/$ARGUMENTS/plan.md 2>/dev/null`
+!`cat .beads/artifacts/$ARGUMENTS/research.md 2>/dev/null`
 
 ## Check For Stale Context
 
-If the handoff is more than 3 days old, things may have changed:
+If handoff is more than 3 days old, things may have changed:
 
-```bash
-git log --oneline -10  # What happened since?
-git diff [handoff-commit]..HEAD --stat  # What files changed?
-```
+!`git log --oneline -10` # What happened since?
+!`git diff [handoff-commit]..HEAD --stat` # What files changed?
 
 If significant changes occurred on main, consider rebasing:
 

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

@@ -34,16 +34,9 @@ Intelligently revert changes for a bead with comprehensive safety checks.
 
 Before any action, verify:
 
-```bash
-# Check for uncommitted changes
-git status --short
-
-# Check CI status
-gh run list --limit 1
-
-# Check if on correct branch
-git branch --show-current
-```
+!`git status --short`
+!`gh run list --limit 1`
+!`git branch --show-current`
 
 ### Safety Gates
 
@@ -52,26 +45,17 @@ git branch --show-current
 | Clean working tree | No uncommitted changes | Stash or commit first      |
 | CI passing         | Latest run succeeded   | Warn, confirm continue     |
 | Not on main/master | On feature branch      | Require `--force` for main |
-| Bead exists        | `bd_show` returns data | Abort with error           |
+| Bead exists        | `bd show` returns data | Abort with error           |
 
 ---
 
 ## Phase 2: Analyze Bead History
 
-```typescript
-bd_show({ id: "[bead-id]" });
-```
-
-```bash
-# Find all commits for this bead
-git log --oneline --all --grep="[bead-id]"
-
-# Show affected files
-git log --name-only --grep="[bead-id]" --pretty=format:""
+!`bd show [bead-id]`
 
-# Count changes
-git log --shortstat --grep="[bead-id]"
-```
+!`git log --oneline --all --grep="[bead-id]"`
+!`git log --name-only --grep="[bead-id]" --pretty=format:""`
+!`git log --shortstat --grep="[bead-id]"`
 
 ### Impact Report
 
@@ -106,19 +90,12 @@ Lines: +456 / -23
 
 Before reverting, check what depends on this:
 
-```typescript
-// Check for dependent beads
-bd_ls({ status: "all", limit: 50, offset: 0 });
-// Filter for beads that depend on this one
-```
+!`bd list --status all --limit 50`
 
-```bash
-# Check for imports of new files
-grep -r "from './auth/" src/ --include="*.ts"
+# Filter for beads that depend on this one
 
-# Check for references in other features
-git log --oneline --all -- src/auth/ | grep -v "[bead-id]"
-```
+!`grep -r "from './auth/" src/ --include="*.ts"`
+!`git log --oneline --all -- src/auth/ | grep -v "[bead-id]"`
 
 ### Downstream Report
 
@@ -204,10 +181,7 @@ To undo this revert later:
 
 If `--include-migrations` or migrations detected:
 
-```bash
-# Check for migration files in commits
-git log --name-only --grep="[bead-id]" -- "**/migrations/**"
-```
+!`git log --name-only --grep="[bead-id]" -- "**/migrations/**"`
 
 ### Migration Revert Strategy
 
@@ -338,17 +312,8 @@ git checkout --ours [file]    # Use reverted
 
 ## Phase 10: Update Bead Status
 
-```typescript
-bd_msg({
-  subj: "Reverted: [bead-id]",
-  body: "Feature reverted at [timestamp]\nReason: [reason]\nBackup: backup/[bead-id]-pre-revert",
-  to: "all",
-  importance: "normal",
-  global: false,
-});
-
-// Optionally close or re-open bead
-bd_reopen({ id: "[bead-id]" });
+```bash
+bd-msg --subj "Reverted: [bead-id]" --body "Feature reverted at [timestamp]\nReason: [reason]\nBackup: backup/[bead-id]-pre-revert" --to "all" --importance normal
 ```
 
 ---
@@ -401,9 +366,9 @@ git commit -m "restore: [bead-id] from backup"
 
 ## Related Commands
 
-| Need                 | Command                        |
-| -------------------- | ------------------------------ |
-| View bead history    | `bd_show({ id: "[bead-id]" })` |
-| Re-implement feature | `/implement [bead-id]`         |
-| Check status         | `/status [bead-id]`            |
-| Create new feature   | `/new-feature`                 |
+| Need                 | Command                |
+| -------------------- | ---------------------- |
+| View bead history    | `bd show [bead-id]`    |
+| Re-implement feature | `/implement [bead-id]` |
+| Check status         | `/status [bead-id]`    |
+| Create new feature   | `/new-feature`         |

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

@@ -19,7 +19,7 @@ Parse `$ARGUMENTS` to determine what to review:
 | Input                    | Scope                  | How to Get Code                             |
 | ------------------------ | ---------------------- | ------------------------------------------- |
 | File/directory path      | That path only         | `read` or `glob` + `read`                   |
-| Bead ID (e.g., `bd-123`) | Implementation vs spec | `bd_show()` then `git diff` from spec       |
+| Bead ID (e.g., `bd-123`) | Implementation vs spec | `bd show` then `git diff` from spec         |
 | PR number (e.g., `#45`)  | PR changes             | `gh pr diff 45`                             |
 | `all` or empty           | Recent changes         | `git diff main...HEAD` or `git diff HEAD~5` |
 
@@ -29,27 +29,31 @@ If bead exists, load spec from `.beads/artifacts/$ID/spec.md` and review against
 
 Run these checks first (batch for speed):
 
+```typescript
+// Type/lint errors
+lsp_lsp_diagnostics(); // for each changed file
 ```
-# Type/lint errors
-lsp_lsp_diagnostics() for each changed file
-npm run type-check || tsc --noEmit
-npm run lint || true
-
-# Anti-pattern detection with ast-grep
-ast-grep pattern="console.log($$$)"           # Debug statements
-ast-grep pattern="any"                         # TypeScript any
-ast-grep pattern="// TODO" OR grep "TODO|FIXME|HACK|XXX"
-ast-grep pattern="password = \"$$$\""          # Hardcoded secrets
-
-# Test status
-npm test || pytest || cargo test
+
+!`npm run type-check || tsc --noEmit`
+!`npm run lint || true`
+
+```typescript
+// Anti-pattern detection with ast-grep
+ast - grep({ pattern: "console.log($$$)" }); // Debug statements
+ast - grep({ pattern: "any" }); // TypeScript any
+grep({ pattern: "TODO|FIXME|HACK|XXX" });
+ast - grep({ pattern: 'password = "$$$"' }); // Hardcoded secrets
 ```
 
+!`npm test || pytest || cargo test`
+
 Collect all automated findings before manual review.
 
 ## Phase 3: Manual Review Categories
 
-skill({ name: "requesting-code-review" })
+```typescript
+skill({ name: "requesting-code-review" });
+```
 
 Review each category with specific focus:
 
@@ -102,14 +106,8 @@ Review each category with specific focus:
 
 For each Critical or Important finding:
 
-```
-bd_add({
-  title: "[Review] <brief issue description>",
-  desc: "File: <path>:<line>\nIssue: <what's wrong>\nFix: <how to fix>",
-  type: "bug",
-  pri: 1,  # Critical=0, Important=1, Minor=2
-  tags: ["review", "security|perf|maintainability"]
-})
+```bash
+bd create "[Review] <brief issue description>" -t bug -p 1
 ```
 
 Skip creating beads for Minor issues (just report them).

package/dist/template/.opencode/command/skill-create.md

@@ -405,9 +405,7 @@ Run test scenarios again until skill guides behavior correctly.
 
 ### File Structure Check
 
-```bash
-ls -la .opencode/skill/$ARGUMENTS/
-```
+!`ls -la .opencode/skill/$ARGUMENTS/`
 
 Expected:
 
@@ -474,8 +472,6 @@ If creating from an existing observation:
 /skill-create my-skill --from-observation
 ```
 
-This will:
-
 1. Search observations for patterns
 2. Extract relevant learnings
 3. Pre-populate skill with discovered knowledge

package/dist/template/.opencode/command/skill-optimize.md

@@ -20,16 +20,9 @@ skill({ name: "writing-skills" });
 
 ### Find Skill Location
 
-```bash
-# Check local skills first
-ls -la .opencode/skill/$ARGUMENTS/ 2>/dev/null
-
-# Check superpowers (shared skills)
-ls -la .opencode/superpowers/skills/$ARGUMENTS/ 2>/dev/null
-
-# Check installed skills
-ls -la ~/.opencode/skills/$ARGUMENTS/ 2>/dev/null
-```
+!`ls -la .opencode/skill/$ARGUMENTS/ 2>/dev/null`
+!`ls -la .opencode/superpowers/skills/$ARGUMENTS/ 2>/dev/null`
+!`ls -la ~/.opencode/skills/$ARGUMENTS/ 2>/dev/null`
 
 ### Load Current Content