opencodekit 0.15.21 → 0.16.1

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

@@ -1,70 +0,0 @@
----
-description: Load Cloudflare skill and get contextual guidance for your task
----
-
-Load the Cloudflare platform skill and help with any Cloudflare development task.
-
-## Workflow
-
-### Step 1: Check for --update-skill flag
-
-If $ARGUMENTS contains `--update-skill`:
-
-1. Determine install location by checking which exists:
-   - Local: `.opencode/skill/cloudflare/`
-   - Global: `~/.config/opencode/skill/cloudflare/`
-
-2. Run the appropriate install command:
-   ```bash
-   # For local installation
-   curl -fsSL https://raw.githubusercontent.com/dmmulroy/cloudflare-skill/main/install.sh | bash
-
-   # For global installation
-   curl -fsSL https://raw.githubusercontent.com/dmmulroy/cloudflare-skill/main/install.sh | bash -s -- --global
-   ```
-
-3. Output success message and stop (do not continue to other steps).
-
-### Step 2: Load cloudflare skill
-
-```
-skill({ name: 'cloudflare' })
-```
-
-### Step 3: Identify task type from user request
-
-Analyze $ARGUMENTS to determine:
-- **Product(s) needed** (Workers, D1, R2, Durable Objects, etc.)
-- **Task type** (new project setup, feature implementation, debugging, config)
-
-Use decision trees in SKILL.md to select correct product.
-
-### Step 4: Read relevant reference files
-
-Based on task type, read from `references/<product>/`:
-
-| Task | Files to Read |
-|------|---------------|
-| New project | `README.md` + `configuration.md` |
-| Implement feature | `README.md` + `api.md` + `patterns.md` |
-| Debug/troubleshoot | `gotchas.md` |
-| All-in-one (monolithic) | `SKILL.md` |
-
-### Step 5: Execute task
-
-Apply Cloudflare-specific patterns and APIs from references to complete the user's request.
-
-### Step 6: Summarize
-
-```
-=== Cloudflare Task Complete ===
-
-Product(s): <products used>
-Files referenced: <reference files consulted>
-
-<brief summary of what was done>
-```
-
-<user-request>
-$ARGUMENTS
-</user-request>

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

@@ -1,245 +0,0 @@
----
-description: Commit with verification and optional bead traceability
-argument-hint: "[bead-id] [--amend]"
-agent: build
----
-
-# Commit
-
-**Load skills:**
-
-```typescript
-skill({ name: "beads" }); // Session protocol
-skill({ name: "verification-before-completion" });
-```
-
-## Options
-
-- `--amend`: Amend the last commit (only if not pushed and you created it)
-
-## Phase 1: Check Git State
-
-!`git status --porcelain`
-!`git diff --stat`
-!`git diff --cached --stat`
-
-Report:
-
-```
-Git State:
-━━━━━━━━━━
-
-Staged:
-- [file1] (modified)
-- [file2] (new)
-
-Unstaged:
-- [file3] (modified)
-
-Untracked:
-- [file4]
-```
-
-If nothing staged: "No changes staged. Run `git add <files>` first."
-
-## Phase 2: Run Verification Gates
-
-Detect project type and run gates:
-
-!`ls package.json Cargo.toml pyproject.toml go.mod Makefile 2>/dev/null`
-
-| Project | Test Command    | Lint Command                         |
-| ------- | --------------- | ------------------------------------ |
-| Node.js | `npm test`      | `npm run lint && npm run type-check` |
-| Rust    | `cargo test`    | `cargo clippy -- -D warnings`        |
-| Python  | `pytest`        | `ruff check . && mypy .`             |
-| Go      | `go test ./...` | `golangci-lint run`                  |
-
-```
-Verification:
-━━━━━━━━━━━━━
-
-Tests: [✓/✗/skipped]
-Lint:  [✓/✗/skipped]
-Types: [✓/✗/skipped]
-```
-
-**If any gate fails:**
-
-```
-Cannot commit: [gate] failed.
-
-Fix errors or use `git commit --no-verify` (not recommended).
-```
-
-## Phase 3: Analyze Changes for Message
-
-!`git diff --cached --stat`
-!`git diff --cached`
-
-Determine:
-
-- **Type**: What kind of change is this?
-- **Scope**: Which module/component changed?
-- **Summary**: What does this change do?
-
-### Commit Type Guide
-
-| Type       | When to Use                             | Example                            |
-| ---------- | --------------------------------------- | ---------------------------------- |
-| `feat`     | New feature for user                    | `feat(auth): add OAuth login`      |
-| `fix`      | Bug fix                                 | `fix(api): handle null response`   |
-| `refactor` | Code change (no new feature or fix)     | `refactor(utils): simplify parser` |
-| `docs`     | Documentation only                      | `docs: update API reference`       |
-| `test`     | Adding or updating tests                | `test(auth): add login tests`      |
-| `chore`    | Maintenance, deps, tooling              | `chore: update dependencies`       |
-| `style`    | Formatting, whitespace (no code change) | `style: fix indentation`           |
-| `perf`     | Performance improvement                 | `perf(db): add query caching`      |
-| `ci`       | CI/CD changes                           | `ci: add deploy workflow`          |
-
-### Scope Detection
-
-Auto-detect scope from changed files:
-
-| Changed Files           | Suggested Scope |
-| ----------------------- | --------------- |
-| `src/auth/*`            | auth            |
-| `src/api/*`             | api             |
-| `src/components/*`      | ui              |
-| `tests/*`               | test            |
-| `docs/*`                | docs            |
-| Multiple unrelated dirs | (omit scope)    |
-
-## Phase 4: Generate Commit Message
-
-Propose message based on analysis:
-
-```
-Proposed Commit:
-━━━━━━━━━━━━━━━━
-
-<type>(<scope>): <summary>
-
-[body - what and why, not how]
-
-[footer - bead reference, breaking changes]
-```
-
-**Example with bead:**
-
-```
-feat(auth): add token refresh mechanism
-
-Implement automatic token refresh when access token expires.
-Tokens are stored in secure session storage.
-
-bd-a1b2c3: OAuth implementation
-```
-
-**Example with breaking change:**
-
-```
-feat(api)!: change response format
-
-BREAKING CHANGE: API responses now use camelCase instead of snake_case.
-Migration guide: https://...
-```
-
-Ask user:
-
-```
-Use this message? (yes/edit/cancel)
-```
-
-## Phase 5: Execute Commit
-
-```bash
-git commit -m "<message>"
-```
-
-**If pre-commit hook fails:**
-
-```
-Pre-commit hook failed:
-━━━━━━━━━━━━━━━━━━━━━━━
-
-[hook output]
-
-Options:
-1. Fix issues and retry: /commit [bead-id]
-2. Skip hook (not recommended): git commit --no-verify -m "..."
-```
-
-**Do NOT use --amend** unless:
-
-1. User explicitly requested `--amend`
-2. You created the HEAD commit in this session
-3. Commit has NOT been pushed to remote
-
-## Phase 6: Sync (for multi-agent)
-
-If bead ID was provided:
-
-```bash
-bd sync
-```
-
-## Output
-
-```
-Committed: [short-hash]
-━━━━━━━━━━━━━━━━━━━━━━━
-
-Message: <type>(<scope>): <summary>
-Files: [N] changed
-Bead: <bead-id> (if provided)
-
-Verification: All gates passed ✓
-```
-
-**Next steps:**
-
-```
-Continue working:
-  [make more changes]
-  /commit [bead-id]
-
-Ready to finish:
-  /finish <bead-id>
-
-Create PR:
-  /pr <bead-id>
-```
-
-## Amend Workflow (--amend)
-
-**Safety checks before amend:**
-
-!`git log -1 --format='%H %s'` # What we're amending
-!`git status` # Check if pushed
-
-```
-Amend Safety Check:
-━━━━━━━━━━━━━━━━━━━
-
-HEAD commit: [hash] [message]
-Pushed to remote: [yes/no]
-Created by you: [yes/no]
-```
-
-**If pushed or not created by you: STOP.**
-
-```
-Cannot amend: Commit already pushed or not created by you.
-
-Use a new commit instead:
-  git add <files>
-  /commit [bead-id]
-```
-
-**If safe to amend:**
-
-```bash
-git add <files>
-git commit --amend -m "<updated message>"
-```

package/dist/template/.opencode/command/complete-next-task.md

@@ -1,77 +0,0 @@
----
-description: Complete the next incomplete PRD task for a bead
-argument-hint: "<bead-id>"
-agent: build
----
-
-# Complete Next Task: $ARGUMENTS
-
-Complete one task from a bead PRD task list.
-
-This command is **Beads-native**:
-
-- PRD: `.beads/artifacts/<bead-id>/prd.md`
-- Tasks: `.beads/artifacts/<bead-id>/prd.json`
-- Progress: `.beads/artifacts/<bead-id>/progress.txt`
-
-## Preconditions
-
-- A bead exists: `bd show $ARGUMENTS`
-- PRD task list exists:
-
-```bash
-ls ".beads/artifacts/$ARGUMENTS/prd.json"
-```
-
-If missing:
-
-- Create PRD: `.beads/artifacts/$ARGUMENTS/prd.md` (use `skill({ name: "prd" })`)
-- Convert: `skill({ name: "prd-task" })`
-
-## Process
-
-### 1) Get Bearings
-
-- Read `.beads/artifacts/$ARGUMENTS/progress.txt` (create if missing)
-- Read `.beads/artifacts/$ARGUMENTS/prd.json`
-- Pick the next task with `passes: false`
-
-### 2) Implement the Task
-
-Implement only what’s needed to satisfy the verification steps.
-
-### 3) Run Feedback Loops (Required)
-
-Run what applies to the repo:
-
-- tests
-- lint
-- typecheck
-
-Do not commit if any fail.
-
-### 4) Update PRD JSON
-
-Set that task’s `passes` to `true`.
-
-### 5) Update Progress Log
-
-Append a short entry to `.beads/artifacts/$ARGUMENTS/progress.txt`:
-
-```markdown
-## Task - <task.id>
-
-- What was implemented
-- Files changed
-- Learnings / patterns
-```
-
-### 6) Commit (Ask First)
-
-Show staged changes and ask user before committing.
-
-## Completion
-
-If all tasks have `passes: true`, report that the PRD is complete and recommend:
-
-- `/finish $ARGUMENTS`