npm - opencodekit - Versions diffs - 0.21.10 → 0.23.0 - Mend

opencodekit 0.21.10 → 0.23.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (213) hide show

package/dist/template/.opencode/skill/finishing-a-development-branch/SKILL.md DELETED Viewed

@@ -1,357 +0,0 @@
----
-name: finishing-a-development-branch
-description: Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
-version: 1.0.0
-tags: [workflow, git]
-dependencies: []
----
-# Finishing a Development Branch
-## When to Use
-- Implementation is complete and tests pass, and you need to merge/PR/cleanup
-- You must present structured end-of-work options and execute the chosen path
-## When NOT to Use
-- Tests or mandatory gates are failing
-- Work is still in progress and not ready for integration
-## Overview
-Guide completion of development work by presenting clear options and handling chosen workflow.
-**Core principle:** Verify tests → Present options → Execute choice → Clean up.
-**Announce at start:** "I'm using the finishing-a-development-branch skill to complete this work."
-## The Process
-### Step 1: Verify Tests
-#### Completion Prep Checklist
-- [ ] Run the project's test suite
-- [ ] Stop if any tests fail and report failures
-**Before presenting options, verify tests pass:**
-```bash
-# Run project's test suite
-npm test / cargo test / pytest / go test ./...
-```
-**If tests fail:**
-```
-Tests failing (<N> failures). Must fix before completing:
-[Show failures]
-Cannot proceed with merge/PR until tests pass.
-```
-Stop. Don't proceed to Step 2.
-**If tests pass:** Continue to Step 2.
-### Step 2: Determine Base Branch
-```bash
-# Try common base branches
-git merge-base HEAD main 2>/dev/null || git merge-base HEAD master 2>/dev/null
-```
-Or ask: "This branch split from main - is that correct?"
-### Step 3: Present Options
-Use question tool to present completion options:
-```typescript
-question({
-  questions: [
-    {
-      header: "Complete",
-      question: "Implementation complete. What would you like to do?",
-      options: [
-        {
-          label: "Merge locally (Recommended)",
-          description: "Merge to base branch",
-        },
-        {
-          label: "Push & create PR",
-          description: "Create pull request for review",
-        },
-        { label: "Keep branch", description: "I'll handle it later" },
-        { label: "Discard work", description: "Delete this branch" },
-      ],
-    },
-  ],
-});
-```
-**Don't add explanation** - keep options concise.
-### Step 4: Execute Choice
-#### Execute Choice Checklist
-- [ ] Follow the selected option's steps exactly
-- [ ] Re-run tests on merged result when applicable
-- [ ] Only cleanup worktree for Options 1, 2, or 4
-#### Option 1: Merge Locally
-```bash
-# Switch to base branch
-git checkout <base-branch>
-# Pull latest
-git pull
-# Merge feature branch
-git merge <feature-branch>
-# Verify tests on merged result
-<test command>
-# If tests pass
-git branch -d <feature-branch>
-```
-Then: Cleanup worktree (Step 5)
-#### Option 2: Push and Create PR
-```bash
-# Push branch
-git push -u origin <feature-branch>
-# Create PR
-gh pr create --title "<title>" --body "$(cat <<'EOF'
-## Summary
-<2-3 bullets of what changed>
-## Test Plan
-- [ ] <verification steps>
-EOF
-)"
-```
-Then: Cleanup worktree (Step 5)
-#### Option 3: Keep As-Is
-Report: "Keeping branch <name>. Worktree preserved at <path>."
-**Don't cleanup worktree.**
-#### Option 4: Discard
-**Confirm first:**
-```
-This will permanently delete:
-- Branch <name>
-- All commits: <commit-list>
-- Worktree at <path>
-Type 'discard' to confirm.
-```
-Wait for exact confirmation.
-If confirmed:
-```bash
-git checkout <base-branch>
-git branch -D <feature-branch>
-```
-Then: Cleanup worktree (Step 5)
-### Step 5: Cleanup Worktree
-**For Options 1, 2, 4:**
-Check if in worktree:
-```bash
-git worktree list | grep $(git branch --show-current)
-```
-If yes:
-```bash
-git worktree remove <worktree-path>
-```
-**For Option 3:** Keep worktree.
-## Quick Reference
-| Option           | Merge | Push | Keep Worktree | Cleanup Branch |
-| ---------------- | ----- | ---- | ------------- | -------------- |
-| 1. Merge locally | ✓     | -    | -             | ✓              |
-| 2. Create PR     | -     | ✓    | ✓             | -              |
-| 3. Keep as-is    | -     | -    | ✓             | -              |
-| 4. Discard       | -     | -    | -             | ✓ (force)      |
-## Mandatory Build Gates (Longshot Pattern)
-**Build gates are non-optional before any merge/PR/close.** Advisory verification has failed at scale — gates must be enforced as hard blockers.
-### Gate Sequence
-#### Gate Checklist
-- [ ] Gate 1: `npm run typecheck`
-- [ ] Gate 2: `npm run lint` (run `npm run lint:fix` if needed)
-- [ ] Gate 3: `vitest`
-- [ ] Stop and fix if any gate fails
-Every bead MUST pass all three gates in order. No exceptions.
-```bash
-# Gate 1: Typecheck
-npm run typecheck
-# Must exit 0. If fails → STOP. Fix types first.
-# Gate 2: Lint
-npm run lint
-# Must exit 0. If fails → STOP. Run npm run lint:fix, then fix remaining.
-# Gate 3: Tests
-vitest
-# Must exit 0. If fails → STOP. Fix failing tests first.
-```
-### Gate Enforcement Script
-Run before every merge, PR creation, or bead close:
-```bash
-#!/bin/bash
-# Run mandatory gates — all must pass
-echo "Gate 1/3: Typecheck..."
-npm run typecheck || { echo "FAILED: Fix type errors before proceeding."; exit 1; }
-echo "Gate 2/3: Lint..."
-npm run lint || {
-  echo "Attempting auto-fix..."
-  npm run lint:fix
-  npm run lint || { echo "FAILED: Fix lint errors before proceeding."; exit 1; }
-}
-echo "Gate 3/3: Tests..."
-vitest || { echo "FAILED: Fix failing tests before proceeding."; exit 1; }
-echo "All gates passed. Safe to merge/PR/close."
-```
-### Gate Failure Response
-| Gate Failure | First Action                     | If Still Failing            |
-| ------------ | -------------------------------- | --------------------------- |
-| Typecheck    | Fix type errors at reported line | Use LSP hover for type info |
-| Lint         | Run `npm run lint:fix`           | Fix remaining manually      |
-| Tests        | Read failing test output         | Fix implementation or test  |
-### Hard Rules
-**NEVER:**
-- Close a bead without passing all 3 gates
-- Create a PR without passing all 3 gates
-- Merge locally without passing all 3 gates on merged result
-- Skip gates "because the change is small"
-**ALWAYS:**
-- Run gates after EVERY non-trivial file change
-- Re-run gates after fixing gate failures (to catch regressions)
-- Run gates on the merged result, not just the branch
-### Integration with Bead Workflow
-```bash
-# Before closing any bead:
-npm run typecheck && npm run lint && vitest
-# If all pass:
-br close <id> --reason "Implementation complete. All gates passed."
-br sync --flush-only
-# If any fail:
-# STOP. Fix. Re-run gates. Then close.
-```
-### Gate State in Delegation Packets
-Workers must include gate results in their completion report:
-```markdown
-## Completion Report
-### Gate Results
-- [ ] typecheck: PASS / FAIL (error: ...)
-- [ ] lint: PASS / FAIL (error: ...)
-- [ ] tests: PASS / FAIL (N failed, N passed)
-### Gate Command Used
-`npm run typecheck && npm run lint && vitest`
-```
-## Common Mistakes
-**Skipping test verification**
-- **Problem:** Merge broken code, create failing PR
-- **Fix:** Always verify tests before offering options
-**Open-ended questions**
-- **Problem:** "What should I do next?" → ambiguous
-- **Fix:** Present exactly 4 structured options
-**Automatic worktree cleanup**
-- **Problem:** Remove worktree when might need it (Option 2, 3)
-- **Fix:** Only cleanup for Options 1 and 4
-**No confirmation for discard**
-- **Problem:** Accidentally delete work
-- **Fix:** Require typed "discard" confirmation
-## Red Flags
-**Never:**
-- Proceed with failing tests
-- Merge without verifying tests on result
-- Delete work without confirmation
-- Force-push without explicit request
-**Always:**
-- Verify tests before offering options
-- Present exactly 4 options
-- Get typed confirmation for Option 4
-- Clean up worktree for Options 1 & 4 only
-## Integration
-**Called by:**
-- **subagent-driven-development** (Step 7) - After all tasks complete
-- **executing-plans** (Step 5) - After all batches complete
-**Pairs with:**
-- **using-git-worktrees** - Cleans up worktree created by that skill

package/dist/template/.opencode/skill/full-output-enforcement/SKILL.md DELETED Viewed

@@ -1,62 +0,0 @@
----
-name: full-output-enforcement
-description: MUST load when generating complete files, long code blocks, or any output where truncation or placeholder comments like '// ... rest of code' would be harmful. Bans all placeholder patterns and enforces exhaustive, unabridged output.
----
-## When to Use
-- When generating complete files, long code blocks, or full configuration outputs
-- When truncation or placeholder comments like `// ... rest of code` would be harmful
-- When the user needs exhaustive, unabridged output
-## When NOT to Use
-- For short code snippets or single-function responses
-- When summarization is explicitly requested
-- For conversational responses that don't involve code generation
-# Full-Output Enforcement
-## Baseline
-Treat every task as production-critical. A partial output is a broken output. Do not optimize for brevity — optimize for completeness. If the user asks for a full file, deliver the full file. If the user asks for 5 components, deliver 5 components. No exceptions.
-## Banned Output Patterns
-The following patterns are hard failures. Never produce them:
-**In code blocks:** `// ...`, `// rest of code`, `// implement here`, `// TODO`, `/* ... */`, `// similar to above`, `// continue pattern`, `// add more as needed`, bare `...` standing in for omitted code
-**In prose:** "Let me know if you want me to continue", "I can provide more details if needed", "for brevity", "the rest follows the same pattern", "similarly for the remaining", "and so on" (when replacing actual content), "I'll leave that as an exercise"
-**Structural shortcuts:** Outputting a skeleton when the request was for a full implementation. Showing the first and last section while skipping the middle. Replacing repeated logic with one example and a description. Describing what code should do instead of writing it.
-## Execution Process
-1. **Scope** — Read the full request. Count how many distinct deliverables are expected (files, functions, sections, answers). Lock that number.
-2. **Build** — Generate every deliverable completely. No partial drafts, no "you can extend this later."
-3. **Cross-check** — Before output, re-read the original request. Compare your deliverable count against the scope count. If anything is missing, add it before responding.
-## Handling Long Outputs
-When a response approaches the token limit:
-- Do not compress remaining sections to squeeze them in.
-- Do not skip ahead to a conclusion.
-- Write at full quality up to a clean breakpoint (end of a function, end of a file, end of a section).
-- End with:
-```
-[PAUSED — X of Y complete. Send "continue" to resume from: next section name]
-```
-On "continue", pick up exactly where you stopped. No recap, no repetition.
-## Quick Check
-Before finalizing any response, verify:
-- No banned patterns from the list above appear anywhere in the output
-- Every item the user requested is present and finished
-- Code blocks contain actual runnable code, not descriptions of what code would do
-- Nothing was shortened to save space

package/dist/template/.opencode/skill/gh-address-comments/SKILL.md DELETED Viewed

@@ -1,29 +0,0 @@
----
-name: gh-address-comments
-description: Use when the user asks to review and address GitHub PR comments/threads for the current branch using gh CLI.
-version: 1.0.0
-tags: [workflow, git, agent-coordination]
-dependencies: []
----
-# gh-address-comments
-Fetch PR comments and review threads, then apply selected fixes.
-## When to Use
-- User asks to resolve PR review comments
-- User wants a numbered list of comment threads to triage
-## When NOT to Use
-- No open PR associated with current branch
-- `gh` is unavailable/auth is missing and user declines auth
-## Workflow
-1. Check auth: `gh auth status`
-2. Fetch comments: `python3 .opencode/skill/gh-address-comments/scripts/fetch_comments.py`
-3. Present numbered comment threads with short fix summaries
-4. Ask which comments to address
-5. Implement only selected fixes and report results

package/dist/template/.opencode/skill/gh-address-comments/scripts/fetch_comments.py DELETED Viewed

@@ -1,237 +0,0 @@
-#!/usr/bin/env python3
-"""
-Fetch all PR conversation comments + reviews + review threads (inline threads)
-for the PR associated with the current git branch, by shelling out to:
-  gh api graphql
-Requires:
-  - `gh auth login` already set up
-  - current branch has an associated (open) PR
-Usage:
-  python fetch_comments.py > pr_comments.json
-"""
-from __future__ import annotations
-import json
-import subprocess
-import sys
-from typing import Any
-QUERY = """\
-query(
-  $owner: String!,
-  $repo: String!,
-  $number: Int!,
-  $commentsCursor: String,
-  $reviewsCursor: String,
-  $threadsCursor: String
-) {
-  repository(owner: $owner, name: $repo) {
-    pullRequest(number: $number) {
-      number
-      url
-      title
-      state
-      # Top-level "Conversation" comments (issue comments on the PR)
-      comments(first: 100, after: $commentsCursor) {
-        pageInfo { hasNextPage endCursor }
-        nodes {
-          id
-          body
-          createdAt
-          updatedAt
-          author { login }
-        }
-      }
-      # Review submissions (Approve / Request changes / Comment), with body if present
-      reviews(first: 100, after: $reviewsCursor) {
-        pageInfo { hasNextPage endCursor }
-        nodes {
-          id
-          state
-          body
-          submittedAt
-          author { login }
-        }
-      }
-      # Inline review threads (grouped), includes resolved state
-      reviewThreads(first: 100, after: $threadsCursor) {
-        pageInfo { hasNextPage endCursor }
-        nodes {
-          id
-          isResolved
-          isOutdated
-          path
-          line
-          diffSide
-          startLine
-          startDiffSide
-          originalLine
-          originalStartLine
-          resolvedBy { login }
-          comments(first: 100) {
-            nodes {
-              id
-              body
-              createdAt
-              updatedAt
-              author { login }
-            }
-          }
-        }
-      }
-    }
-  }
-}
-"""
-def _run(cmd: list[str], stdin: str | None = None) -> str:
-    p = subprocess.run(cmd, input=stdin, capture_output=True, text=True)
-    if p.returncode != 0:
-        raise RuntimeError(f"Command failed: {' '.join(cmd)}\n{p.stderr}")
-    return p.stdout
-def _run_json(cmd: list[str], stdin: str | None = None) -> dict[str, Any]:
-    out = _run(cmd, stdin=stdin)
-    try:
-        return json.loads(out)
-    except json.JSONDecodeError as e:
-        raise RuntimeError(f"Failed to parse JSON from command output: {e}\nRaw:\n{out}") from e
-def _ensure_gh_authenticated() -> None:
-    try:
-        _run(["gh", "auth", "status"])
-    except RuntimeError:
-        print("run `gh auth login` to authenticate the GitHub CLI", file=sys.stderr)
-        raise RuntimeError("gh auth status failed; run `gh auth login` to authenticate the GitHub CLI") from None
-def gh_pr_view_json(fields: str) -> dict[str, Any]:
-    # fields is a comma-separated list like: "number,headRepositoryOwner,headRepository"
-    return _run_json(["gh", "pr", "view", "--json", fields])
-def get_current_pr_ref() -> tuple[str, str, int]:
-    """
-    Resolve the PR for the current branch (whatever gh considers associated).
-    Works for cross-repo PRs too, by reading head repository owner/name.
-    """
-    pr = gh_pr_view_json("number,headRepositoryOwner,headRepository")
-    owner = pr["headRepositoryOwner"]["login"]
-    repo = pr["headRepository"]["name"]
-    number = int(pr["number"])
-    return owner, repo, number
-def gh_api_graphql(
-    owner: str,
-    repo: str,
-    number: int,
-    comments_cursor: str | None = None,
-    reviews_cursor: str | None = None,
-    threads_cursor: str | None = None,
-) -> dict[str, Any]:
-    """
-    Call `gh api graphql` using -F variables, avoiding JSON blobs with nulls.
-    Query is passed via stdin using query=@- to avoid shell newline/quoting issues.
-    """
-    cmd = [
-        "gh",
-        "api",
-        "graphql",
-        "-F",
-        "query=@-",
-        "-F",
-        f"owner={owner}",
-        "-F",
-        f"repo={repo}",
-        "-F",
-        f"number={number}",
-    ]
-    if comments_cursor:
-        cmd += ["-F", f"commentsCursor={comments_cursor}"]
-    if reviews_cursor:
-        cmd += ["-F", f"reviewsCursor={reviews_cursor}"]
-    if threads_cursor:
-        cmd += ["-F", f"threadsCursor={threads_cursor}"]
-    return _run_json(cmd, stdin=QUERY)
-def fetch_all(owner: str, repo: str, number: int) -> dict[str, Any]:
-    conversation_comments: list[dict[str, Any]] = []
-    reviews: list[dict[str, Any]] = []
-    review_threads: list[dict[str, Any]] = []
-    comments_cursor: str | None = None
-    reviews_cursor: str | None = None
-    threads_cursor: str | None = None
-    pr_meta: dict[str, Any] | None = None
-    while True:
-        payload = gh_api_graphql(
-            owner=owner,
-            repo=repo,
-            number=number,
-            comments_cursor=comments_cursor,
-            reviews_cursor=reviews_cursor,
-            threads_cursor=threads_cursor,
-        )
-        if "errors" in payload and payload["errors"]:
-            raise RuntimeError(f"GitHub GraphQL errors:\n{json.dumps(payload['errors'], indent=2)}")
-        pr = payload["data"]["repository"]["pullRequest"]
-        if pr_meta is None:
-            pr_meta = {
-                "number": pr["number"],
-                "url": pr["url"],
-                "title": pr["title"],
-                "state": pr["state"],
-                "owner": owner,
-                "repo": repo,
-            }
-        c = pr["comments"]
-        r = pr["reviews"]
-        t = pr["reviewThreads"]
-        conversation_comments.extend(c.get("nodes") or [])
-        reviews.extend(r.get("nodes") or [])
-        review_threads.extend(t.get("nodes") or [])
-        comments_cursor = c["pageInfo"]["endCursor"] if c["pageInfo"]["hasNextPage"] else None
-        reviews_cursor = r["pageInfo"]["endCursor"] if r["pageInfo"]["hasNextPage"] else None
-        threads_cursor = t["pageInfo"]["endCursor"] if t["pageInfo"]["hasNextPage"] else None
-        if not (comments_cursor or reviews_cursor or threads_cursor):
-            break
-    assert pr_meta is not None
-    return {
-        "pull_request": pr_meta,
-        "conversation_comments": conversation_comments,
-        "reviews": reviews,
-        "review_threads": review_threads,
-    }
-def main() -> None:
-    _ensure_gh_authenticated()
-    owner, repo, number = get_current_pr_ref()
-    result = fetch_all(owner, repo, number)
-    print(json.dumps(result, indent=2))
-if __name__ == "__main__":
-    main()