opencodekit 0.20.3 → 0.20.5

package/dist/template/.opencode/skill/memory-grounding/SKILL.md

@@ -0,0 +1,68 @@
+---
+name: memory-grounding
+description: >
+  Use at the start of any command that needs prior context — searches memory for decisions, patterns, and handoffs before execution to avoid re-solving solved problems.
+version: 1.0.0
+tags: [memory, grounding, pre-flight]
+---
+
+# Memory Grounding
+
+Search institutional memory before executing any command that modifies state or makes decisions.
+
+## When to Use
+
+- At the start of `/ship`, `/plan`, `/create`, `/pr`, `/research`, `/resume`
+- Before any command that benefits from prior context
+- When you need to check if work was already done or decisions already made
+
+## When NOT to Use
+
+- Read-only commands that don't need historical context (e.g., `/status`)
+- Commands that explicitly skip grounding (e.g., `--no-memory` flag)
+
+## Protocol
+
+### Step 1: Search for relevant context
+
+```typescript
+// Primary: search by bead ID or topic
+memory-search({ query: "$ARGUMENTS" });
+
+// Secondary: search by keywords with limit
+memory-search({ query: "<feature or topic keywords>", limit: 5 });
+
+// Optional: filter by type for specific needs
+memory-search({ query: "<keywords>", type: "decision" });  // Past decisions
+memory-search({ query: "<keywords>", type: "bugfix" });    // Known issues
+```
+
+### Step 2: Check last session handoff
+
+```typescript
+memory-read({ file: "handoffs/last" });
+```
+
+### Step 3: Check session history (if resuming work)
+
+```typescript
+find_sessions({ query: "$ARGUMENTS", limit: 3 });
+```
+
+### Step 4: Apply findings
+
+- **If relevant findings exist:** Incorporate them directly. Don't re-solve solved problems.
+- **If prior decisions found:** Follow them unless there's a clear reason to diverge (document the divergence).
+- **If known issues found:** Account for them in the current approach.
+- **If nothing found:** Proceed normally — absence of memory is not a blocker.
+
+## Command-Specific Variations
+
+| Command     | Extra Focus                                            |
+| ----------- | ------------------------------------------------------ |
+| `/plan`     | Search bugfixes; check for existing plans to overwrite |
+| `/ship`     | Search for failed approaches to avoid repeating        |
+| `/create`   | Search for duplicate beads before creating             |
+| `/pr`       | Include findings in PR description                     |
+| `/research` | Search before spawning agents; narrow scope to gaps    |
+| `/resume`   | Read handoff file by bead ID; check session history    |

package/dist/template/.opencode/skill/verification-gates/SKILL.md

@@ -0,0 +1,63 @@
+---
+name: verification-gates
+description: >
+  Use when running pre-merge or pre-PR verification checks. Detects project type and runs appropriate build, test, lint, and typecheck commands.
+version: 1.0.0
+tags: [verification, testing, lint, typecheck, ci]
+---
+
+# Verification Gates
+
+Detect project type and run the appropriate verification commands before merging or creating PRs.
+
+## When to Use
+
+- In `/pr` before creating a pull request
+- In `/review-codebase` during automated checks phase
+- In `/ship` during final verification
+- Any command that needs to verify code quality before completion
+
+## When NOT to Use
+
+- For incremental checks during development (just run the specific tool)
+- When only one check type is needed (e.g., lint-only)
+
+## Project Type Detection
+
+| Project Type    | Detect Via                    | Build            | Test            | Lint                          | Typecheck                             |
+| --------------- | ----------------------------- | ---------------- | --------------- | ----------------------------- | ------------------------------------- |
+| Node/TypeScript | `package.json`                | `npm run build`  | `npm test`      | `npm run lint`                | `npm run typecheck` or `tsc --noEmit` |
+| Rust            | `Cargo.toml`                  | `cargo build`    | `cargo test`    | `cargo clippy -- -D warnings` | (included in build)                   |
+| Python          | `pyproject.toml` / `setup.py` | —                | `pytest`        | `ruff check .`                | `mypy .`                              |
+| Go              | `go.mod`                      | `go build ./...` | `go test ./...` | `golangci-lint run`           | (included in build)                   |
+
+## Protocol
+
+### Step 1: Detect project type
+
+Check for indicator files in the project root. Multiple types may coexist (e.g., Node + Python monorepo).
+
+### Step 2: Run checks in parallel where possible
+
+```bash
+# Run typecheck and lint in parallel
+npm run typecheck &
+npm run lint &
+wait
+
+# Then run tests (may depend on build)
+npm test
+```
+
+### Step 3: Report results
+
+For each check, report:
+
+- **Pass/Fail** status
+- **Error count** (if failed)
+- **Key error messages** (first 5)
+
+### Step 4: Gate decision
+
+- **All pass:** Proceed with the command
+- **Any fail:** Stop and report. Let the user decide whether to proceed or fix.

package/dist/template/.opencode/skill/workspace-setup/SKILL.md

@@ -0,0 +1,76 @@
+---
+name: workspace-setup
+description: >
+  Use when a command needs to create a feature branch or set up a workspace for bead work. Shared by /create and /ship.
+version: 1.0.0
+tags: [git, workspace, branch, setup]
+---
+
+# Workspace Setup
+
+Set up a git workspace (branch or worktree) for bead-based work.
+
+## When to Use
+
+- In `/create` after bead creation, before task conversion
+- In `/ship` when auto-claiming an unclaimed bead
+- Any command that needs to transition from "no workspace" to "active workspace"
+
+## When NOT to Use
+
+- If bead is already `in_progress` with an existing branch
+- If user explicitly chose "Use current branch"
+
+## Protocol
+
+### Step 1: Ask the user
+
+```typescript
+question({
+  questions: [
+    {
+      header: "Workspace",
+      question: "How do you want to set up the workspace?",
+      options: [
+        {
+          label: "Create feature branch (Recommended)",
+          description: "git checkout -b <prefix>/<bead-id>-<title>",
+        },
+        {
+          label: "Use current branch",
+          description: "Work on current branch without creating a new one",
+        },
+      ],
+    },
+  ],
+});
+```
+
+> **Note:** `/create` may additionally offer a "Create worktree" option using `skill({ name: "using-git-worktrees" })`.
+
+### Step 2: Create branch (if selected)
+
+Map bead type to branch prefix:
+
+| Bead Type | Branch Prefix |
+| --------- | ------------- |
+| feature   | feat          |
+| bug       | fix           |
+| task      | task          |
+| epic      | epic          |
+
+Create the branch:
+
+```bash
+git checkout -b $PREFIX/$BEAD_ID-$TITLE_SLUG
+```
+
+Where `$TITLE_SLUG` is the bead title lowercased with spaces replaced by hyphens, truncated to ~50 chars.
+
+### Step 3: Confirm
+
+```bash
+git branch --show-current
+```
+
+Verify you're on the new branch before proceeding.

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "opencodekit",
-	"version": "0.20.3",
+	"version": "0.20.5",
 	"description": "CLI tool for bootstrapping and managing OpenCodeKit projects",
 	"keywords": [
 		"agents",