opencodekit 0.15.14 → 0.15.15

package/dist/index.js

@@ -750,7 +750,7 @@ var cac = (name = "") => new CAC(name);
 // package.json
 var package_default = {
   name: "opencodekit",
-  version: "0.15.14",
+  version: "0.15.15",
   description: "CLI tool for bootstrapping and managing OpenCodeKit projects",
   keywords: [
     "agents",
@@ -3884,13 +3884,13 @@ var MODEL_PRESETS = {
     }
   },
   recommend: {
-    model: "proxypal/gemini-claude-opus-4-5-thinking",
+    model: "github-copilot/claude-opus-4.5",
     agents: {
-      build: "proxypal/gemini-claude-opus-4-5-thinking",
+      build: "github-copilot/claude-opus-4.5",
       plan: "openai/gpt-5.2",
       review: "openai/gpt-5.2-codex",
       explore: "proxypal/gemini-3-flash-preview",
-      general: "opencode/glm-4.7-free",
+      general: "github-copilot/claude-haiku-4.5",
       looker: "proxypal/gemini-3-flash-preview",
       vision: "proxypal/gemini-3-pro-preview",
       scout: "proxypal/gemini-3-flash-preview",

package/dist/template/.opencode/AGENTS.md

@@ -359,7 +359,26 @@ Before you start implementing, verify the requirements are clear. If interpretat
 
 ### Before claiming done
 
-Before you claim completion, verify these things: you ran `bd close <id>`, you ran `bd sync`, there are no pending LSP nudges, and you saved observations for any important decisions or patterns.
+Before you claim completion, verify these things:
+
+1. **Run Oracle critique** on any significant code changes:
+
+   ```typescript
+   oracle({
+     question: "Is this solution overcomplicated? Could it be 10x simpler?",
+     mode: "critique",
+     context: "<summary of changes>",
+   });
+   ```
+
+   If Oracle suggests simplification, implement it before proceeding.
+
+2. You ran `bd close <id>` with a meaningful reason
+3. You ran `bd sync` to push changes
+4. There are no pending LSP nudges
+5. You saved observations for any important decisions or patterns
+
+**DO NOT skip the Oracle critique for non-trivial changes.** This prevents bloated, overcomplicated solutions that could be 10x simpler.
 
 ---
 

package/dist/template/.opencode/memory/observations/2026-01-29-learning-karpathy-llm-coding-insights-dec-2025.md

@@ -0,0 +1,44 @@
+---
+type: learning
+created: 2026-01-29T01:59:58.781Z
+confidence: high
+valid_until: null
+superseded_by: null
+concepts: ["karpathy", "llm-coding", "best-practices", "declarative", "test-first", "sycophancy", "simplicity", "leverage"]
+---
+
+# 📚 Karpathy LLM coding insights Dec 2025
+
+🟢 **Confidence:** high
+
+From Andrej Karpathy's analysis of LLM-assisted coding (Dec 2025):
+
+KEY PROBLEMS:
+1. Wrong assumptions - models assume without checking
+2. No confusion management - don't seek clarifications
+3. Sycophancy - don't push back when they should
+4. Overcomplicate - bloated abstractions (1000 lines → 100 lines possible)
+5. Side effects - change unrelated code
+6. No cleanup - dead code remains
+
+BEST PRACTICES:
+1. DECLARATIVE > IMPERATIVE - give success criteria, not step-by-step instructions
+2. TEST-FIRST - write tests, then pass them (TDD skill)
+3. LOOPING - LLMs excel at looping until goals met (verification skill)
+4. NAIVE → OPTIMIZED - write correct first, then optimize
+5. BROWSER MCP - put agents in feedback loops with real systems
+
+LEVERAGE PRINCIPLE:
+"Don't tell it what to do, give it success criteria and watch it go"
+
+OPENCODE ALIGNMENT:
+- Oracle tool → anti-sycophancy (critique mode)
+- Question tool → clarification seeking
+- TDD skill → test-first workflow
+- Verification skill → looping until green
+- LSP chain → prevent wrong assumptions
+
+MISSING:
+- Explicit simplicity gate ("can this be 10x simpler?")
+- Dead code cleanup protocol
+- Side-effect prevention checklist