opencodekit 0.20.1 → 0.20.3

package/dist/template/.opencode/skill/verification-before-completion/SKILL.md

@@ -95,6 +95,52 @@ Skip any step = lying, not verifying
 | "Partial check is enough"               | Partial proves nothing |
 | "Different words so rule doesn't apply" | Spirit over letter     |
 
+## Diagnostic Failure Phrases
+
+These phrases are **automatic re-verification triggers**. If you catch yourself writing any of these (or semantic equivalents), STOP and run the actual verification command before continuing.
+
+### Completion Claims Without Evidence
+
+- "This should fix it"
+- "That should resolve the issue"
+- "The problem should be gone now"
+- "This will work"
+- "It's fixed"
+- "Everything looks good"
+- "We're all set"
+
+### Confidence Substitution
+
+- "I'm fairly certain this is correct"
+- "Based on my understanding, this works"
+- "This is straightforward enough"
+- "The logic is sound"
+- "This follows the pattern so it should be fine"
+
+### Deflection / Minimization
+
+- "It's just a minor change"
+- "Nothing else should be affected"
+- "The rest of the code is unchanged"
+- "This is a safe change"
+- "No side effects expected"
+
+### Post-Hoc Rationalization
+
+- "The error was probably just [X]"
+- "That failure was likely a fluke"
+- "It probably works in production"
+- "The test environment might be the issue"
+
+### False Completion
+
+- "All done!" / "Done!" / "Complete!"
+- "That takes care of everything"
+- "Ready for review" (without verification output)
+- "Committing now" (without verification output)
+
+**Rule:** If any of these phrases appear in your draft response, delete them and replace with actual verification command output. The phrase IS the signal that you're about to lie.
+
 ## Key Patterns
 
 **Tests:**

package/package.json

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

package/dist/template/.opencode/agent/runner.md

@@ -1,79 +0,0 @@
----
-description: Lightweight runner for trivial shell, git, and filesystem operations
-mode: subagent
-temperature: 0.0
-permission:
-  bash:
-    "*": allow
-    "git push*": ask
-    "git commit*": ask
-    "git merge*": ask
-    "git reset*": ask
-    "rm*": ask
-    "sudo*": deny
-  write:
-    "*": deny
-  edit:
-    "*": deny
----
-
-You are OpenCode, the best coding agent on the planet.
-
-# Runner Agent
-
-**Purpose**: Execute trivial operations — scripts, git commands, file system ops. No code reasoning.
-
-## Identity
-
-You are the runner agent. You execute simple, well-defined operations quickly and reliably. You don't write code or make architectural decisions.
-
-## Model Guidance
-
-- Use the cheapest/fastest available model for execution tasks
-- Temperature: 0.0 (deterministic execution)
-
-## Capabilities
-
-- Run shell commands and scripts
-- Git operations (commit, push, pull, tag, branch, merge)
-- File system operations (move, copy, delete — with confirmation for destructive ops)
-- Run build/test/lint commands
-- Read command output and report results
-
-## Restrictions
-
-- **Never edit source code files** — delegate to general or build agent
-- **Never make architectural decisions** — escalate to plan agent
-- **No complex reasoning** — if a task requires understanding code logic, escalate
-- **No implementation work** — do not fix bugs or build features
-
-## When to Use
-
-- Simple shell commands
-- Git operations (commit, push, tag, merge)
-- Running build/test/lint scripts
-- File system operations (move, copy, delete with confirmation)
-
-## When NOT to Use
-
-- Code changes or refactors
-- Bug fixes or feature implementation
-- Tasks requiring code logic analysis
-- Architecture or design decisions
-
-## Rules
-
-1. Execute exactly what is requested — no improvisation
-2. Report command output faithfully — never fabricate
-3. Ask before destructive operations (delete, force push, reset)
-4. If a command fails, report the error — don't attempt creative fixes
-5. Stage specific files only — never `git add .`
-
-## Output Format
-
-For every operation:
-1. Show the command being run
-2. Show the output
-3. Confirm success or report failure
-
-Keep output minimal. No explanations unless something fails.

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

@@ -1,156 +0,0 @@
----
-description: Start working on a bead - claim it and prepare workspace
-argument-hint: "<bead-id> [--worktree]"
-agent: build
----
-
-# Start: $ARGUMENTS
-
-Claim a task and prepare workspace. Bridge between specification (`/create`) and implementation (`/ship`).
-
-> **Workflow:** `/create` → **`/start <id>`** → `/ship <id>`
->
-> ⛔ Bead MUST have `prd.md` (created via `/create`).
-
-## Load Skills
-
-```typescript
-skill({ name: "beads" });
-skill({ name: "prd-task" }); // PRD → executable tasks
-```
-
-## Parse Arguments
-
-| Argument     | Default  | Description                  |
-| ------------ | -------- | ---------------------------- |
-| `<bead-id>`  | required | The bead to start            |
-| `--worktree` | false    | Create isolated git worktree |
-
-## Determine Input Type
-
-| Input Type | Detection                   | Action                  |
-| ---------- | --------------------------- | ----------------------- |
-| Bead ID    | Matches `br-xxx` or numeric | Start that bead         |
-| Path       | File/directory path         | Not supported for start |
-
-## Before You Start
-
-- **Be certain**: Only start beads with valid PRD (check Phase 2)
-- **Check workspace**: Don't start if uncommitted changes exist (Phase 1)
-- **One task at a time**: Warn if other tasks in progress
-- **Validate spec**: Verify prd.md exists and has real content
-- **Ask about workspace**: Let user choose branch/worktree strategy
-
-## Phase 1: Pre-flight
-
-```bash
-git status --porcelain
-git branch --show-current
-br list --status=in_progress
-```
-
-- If uncommitted changes: ask user to stash, commit, or continue
-- If other tasks in progress: warn before claiming another
-
-## Phase 2: Validate Specification
-
-```bash
-br show $ARGUMENTS
-```
-
-Read `.beads/artifacts/$ARGUMENTS/` to check what artifacts exist.
-
-Verify `prd.md` exists and has real content (not just placeholders). If missing or incomplete, tell user to run `/create` first.
-
-## Phase 3: Claim
-
-```bash
-br update $ARGUMENTS --status in_progress
-```
-
-## Phase 4: Prepare Workspace
-
-Ask user how to handle workspace:
-
-```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 feat/<bead-id>-<title>",
-        },
-        {
-          label: "Use current branch",
-          description: "Work on current branch",
-        },
-        {
-          label: "Create worktree",
-          description: "Isolated git worktree for this bead",
-        },
-      ],
-    },
-  ],
-});
-```
-
-**If feature branch selected:**
-
-Map bead type to branch prefix:
-
-| Bead Type | Branch Prefix |
-| --------- | ------------- |
-| feature   | feat          |
-| bug       | fix           |
-| task      | task          |
-| epic      | epic          |
-
-Create the branch:
-
-```bash
-# Example: feat/br-42-add-auth
-git checkout -b $PREFIX/$BEAD_ID-$TITLE_SLUG
-```
-
-Slugify the title (lowercase, spaces to hyphens) and use the bead type to determine the prefix.
-
-**If worktree selected:**
-
-```typescript
-skill({ name: "using-git-worktrees" });
-```
-
-**If current branch:** Continue without branch creation.
-
-## Phase 5: Convert PRD to Tasks
-
-If `prd.json` doesn't exist yet, use `prd-task` skill to convert PRD markdown → executable JSON.
-
-If `prd.json` already exists, show progress (completed/total tasks).
-
-## Phase 6: Report and Route
-
-Output:
-
-1. Bead type and status
-2. Branch name
-3. Workspace (main or worktree)
-4. Artifact status (prd.md validated, prd.json exists/created)
-5. Next step recommendation
-
-| State              | Next Command             |
-| ------------------ | ------------------------ |
-| Has prd.json       | `/ship $ARGUMENTS`       |
-| Epic with subtasks | `/start <first-subtask>` |
-| Complex task       | `/plan $ARGUMENTS`       |
-
-## Related Commands
-
-| Need                | Command      |
-| ------------------- | ------------ |
-| Create spec first   | `/create`    |
-| Plan implementation | `/plan <id>` |
-| Implement and ship  | `/ship <id>` |