@soleri/cli 1.9.0 → 1.10.0

package/code-reviewer/skills/executing-plans/SKILL.md

@@ -1,201 +0,0 @@
----
-name: executing-plans
-description: Use when you have a written implementation plan to execute in a separate session with review checkpoints
----
-
-<!-- Adapted from superpowers (MIT License) -->
-
-# Executing Plans
-
-## Overview
-
-Load plan, review critically, execute tasks in batches, report for review between batches.
-
-**Core principle:** Batch execution with checkpoints for architect review.
-
-**Announce at start:** "I'm using the executing-plans skill to implement this plan."
-
-## The Process
-
-### Step 1: Load and Review Plan
-
-First, load the tracked plan from the agent:
-
-```
-code-reviewer_core op:get_plan
-```
-
-List all tasks to understand scope:
-
-```
-code-reviewer_core op:plan_list_tasks
-  params: { planId: "<id>" }
-```
-
-Check plan stats for an overview:
-
-```
-code-reviewer_core op:plan_stats
-```
-
-If no tracked plan exists, read the plan file from `docs/plans/`.
-
-Review critically — identify any questions or concerns about the plan.
-- If concerns: Raise them with your human partner before starting
-- If no concerns: Create TodoWrite and proceed
-
-### Step 2: Start Execution Loop
-
-For iterative tasks, start a validation loop:
-
-```
-code-reviewer_core op:loop_start
-  params: { prompt: "<plan objective>", mode: "custom" }
-```
-
-The loop tracks iterations and validates progress automatically.
-
-### Step 3: Execute Batch
-**Default: First 3 tasks**
-
-For each task:
-1. Mark as in_progress:
-   ```
-   code-reviewer_core op:update_task
-     params: { planId: "<id>", taskIndex: <n>, status: "in_progress" }
-   ```
-2. Follow each step exactly (plan has bite-sized steps)
-3. Run verifications as specified
-4. Mark as completed:
-   ```
-   code-reviewer_core op:update_task
-     params: { planId: "<id>", taskIndex: <n>, status: "completed" }
-   ```
-
-After each task, iterate the loop:
-
-```
-code-reviewer_core op:loop_iterate
-```
-
-### Step 4: Report
-When batch complete:
-- Show what was implemented
-- Show verification output
-- Check loop status:
-  ```
-  code-reviewer_core op:loop_status
-  ```
-- Say: "Ready for feedback."
-
-### Step 5: Continue
-Based on feedback:
-- Apply changes if needed
-- Execute next batch
-- Repeat until complete
-
-### Step 6: Complete Development
-
-After all tasks complete and verified:
-
-1. Run final verification (use verification-before-completion skill)
-
-2. Complete the validation loop:
-   ```
-   code-reviewer_core op:loop_complete
-   ```
-
-3. Reconcile plan — compare what was planned vs what actually happened:
-   ```
-   code-reviewer_core op:plan_reconcile
-     params: {
-       planId: "<id>",
-       actualSteps: "<description of what was actually done>",
-       driftNotes: "<what differed from the plan>"
-     }
-   ```
-
-4. Complete plan lifecycle — extract knowledge and archive:
-   ```
-   code-reviewer_core op:plan_complete_lifecycle
-     params: { planId: "<id>" }
-   ```
-
-5. Archive the plan for historical reference:
-   ```
-   code-reviewer_core op:plan_archive
-     params: { planId: "<id>" }
-   ```
-
-6. Capture a session summary:
-   ```
-   code-reviewer_core op:session_capture
-     params: { summary: "<what was built, key decisions, files modified>" }
-   ```
-
-## Capture Learnings During Execution
-
-If you discover something worth remembering during execution (a gotcha, a better approach, an anti-pattern):
-
-```
-code-reviewer_core op:capture_quick
-  params: {
-    title: "<what you learned>",
-    description: "<context, why it matters, when it applies>"
-  }
-```
-
-Don't wait until the end — capture insights as they happen.
-
-## When to Stop and Ask for Help
-
-**STOP executing immediately when:**
-- Hit a blocker mid-batch (missing dependency, test fails, instruction unclear)
-- Plan has critical gaps preventing starting
-- You don't understand an instruction
-- Verification fails repeatedly
-
-**Ask for clarification rather than guessing.**
-
-## When to Revisit Earlier Steps
-
-**Return to Review (Step 1) when:**
-- Partner updates the plan based on your feedback
-- Fundamental approach needs rethinking
-
-**Don't force through blockers** - stop and ask.
-
-## Remember
-- Review plan critically first
-- Follow plan steps exactly
-- Don't skip verifications
-- Between batches: just report and wait
-- Stop when blocked, don't guess
-- Capture learnings as you go, not just at the end
-- Always reconcile the plan after execution — drift data makes future plans better
-- Never start implementation on main/master branch without explicit user consent
-
-## Agent Tools Reference
-
-| Op | When to Use |
-|----|-------------|
-| `get_plan` | Load tracked plan |
-| `plan_list_tasks` | List all tasks in the plan |
-| `plan_stats` | Plan overview and metrics |
-| `update_task` | Mark tasks in_progress / completed |
-| `loop_start` | Begin validation loop for iterative execution |
-| `loop_iterate` | Track each iteration |
-| `loop_status` | Check loop progress |
-| `loop_complete` | Finish validation loop |
-| `plan_reconcile` | Compare planned vs actual (post-execution) |
-| `plan_complete_lifecycle` | Extract knowledge from execution |
-| `plan_archive` | Archive plan for history |
-| `session_capture` | Save session context |
-| `capture_quick` | Capture mid-execution learnings |
-
-## Integration
-
-**Required workflow skills:**
-- writing-plans — Creates the plan this skill executes
-- verification-before-completion — Verify work before claiming completion
-- test-driven-development — Follow TDD for each implementation step

package/code-reviewer/skills/fix-and-learn/SKILL.md

@@ -1,164 +0,0 @@
----
-name: fix-and-learn
-description: Use AFTER systematic-debugging completes to execute the fix and capture the learning in the vault. Invoke this skill when moving from diagnosis to repair for bugs, broken behavior, errors, regressions, or unexpected results. Chains with systematic-debugging — debugging finds root cause, this skill fixes and captures the anti-pattern.
----
-
-# Fix & Learn — Debug, Repair, Capture
-
-Fix bugs through a structured recovery workflow, then capture the root cause as a reusable anti-pattern. The learning step is what makes fixes compound across sessions.
-
-## When to Use
-
-Any time something is broken, behaving unexpectedly, or producing errors. This includes runtime bugs, visual regressions, type errors, and "it used to work" situations.
-
-## The Search Order — MANDATORY
-
-**Never jump to writing code.** Always follow this lookup order:
-
-1. **Vault first** — has this been solved before?
-2. **Web search** — is there a known solution or pattern?
-3. **Plan the fix** — design the approach before touching code
-4. **Implement** — only after steps 1-3
-
-Skipping to implementation is the #1 cause of wasted time and recurring bugs.
-
-## Orchestration Sequence
-
-### Step 1: Classify and Route
-
-Classify the intent to confirm this is a FIX and get routing context:
-
-```
-code-reviewer_core op:route_intent
-  params: { prompt: "<user's bug description>" }
-```
-
-### Step 2: Check Vault First
-
-Search for this bug or similar issues:
-
-```
-code-reviewer_core op:search_intelligent
-  params: { query: "<error message or bug description>" }
-```
-
-Check memory for patterns across sessions:
-
-```
-code-reviewer_core op:memory_search
-  params: { query: "<bug description>" }
-```
-
-Check memory topics — are bugs clustering in a specific area?
-
-```
-code-reviewer_core op:memory_topics
-```
-
-Check memory stats to understand the debugging landscape:
-
-```
-code-reviewer_core op:memory_stats
-```
-
-If vault returns a match with high confidence — **use it**. Don't re-investigate what's already been solved.
-
-### Step 3: Search the Web
-
-If the vault has no answer, search for existing solutions before investigating from scratch:
-- Known issues in the library/framework
-- Stack Overflow answers for the exact error
-- GitHub issues on relevant repos
-- Official documentation for the API or feature involved
-
-A 30-second web search can save hours of investigation.
-
-### Step 4: Start Fix Loop
-
-For complex bugs requiring multiple iterations, start a validation loop:
-
-```
-code-reviewer_core op:loop_start
-  params: { prompt: "Fix: <bug description>", mode: "custom" }
-```
-
-### Step 5: Diagnose and Fix
-
-Only if Steps 2-3 didn't produce a solution, apply the systematic debugging approach (use systematic-debugging skill):
-1. Reproduce the issue
-2. Isolate the root cause
-3. **Plan the fix before writing code** — even a one-line mental plan
-4. Implement the fix
-5. Verify the fix resolves the issue without regressions
-
-Track each iteration:
-
-```
-code-reviewer_core op:loop_iterate
-```
-
-### Step 6: Validate the Fix
-
-Run the project's test suite to ensure the fix didn't introduce regressions. Use the verification-before-completion skill to confirm all checks pass.
-
-Complete the loop when validated:
-
-```
-code-reviewer_core op:loop_complete
-```
-
-### Step 7: Capture the Learning
-
-This step is critical — it's what makes the agent smarter over time.
-
-```
-code-reviewer_core op:capture_knowledge
-  params: {
-    title: "<bug title>",
-    description: "<root cause, solution, what made it hard to find>",
-    type: "anti-pattern",
-    category: "<domain>",
-    tags: ["<error-type>", "<component>"]
-  }
-```
-
-For quick captures:
-```
-code-reviewer_core op:capture_quick
-  params: { title: "<bug>", description: "<root cause and fix>" }
-```
-
-### Step 8: Post-Capture Quality
-
-Run duplicate detection to ensure we didn't create redundant entries:
-
-```
-code-reviewer_core op:curator_detect_duplicates
-```
-
-### Step 9: Verify Health
-
-```
-code-reviewer_core op:admin_health
-```
-
-## Exit Criteria
-
-Fix is complete when: the bug is resolved, tests pass (Step 6), and the root cause is captured in vault (Step 7). A fix without a capture is an incomplete fix.
-
-## Agent Tools Reference
-
-| Op | When to Use |
-|----|-------------|
-| `route_intent` | Classify as FIX intent |
-| `search_intelligent` | Check vault for known bugs |
-| `memory_search` | Search across session memories |
-| `memory_topics` | See if bugs cluster in an area |
-| `memory_stats` | Understand debugging landscape |
-| `loop_start` | Begin iterative fix cycle |
-| `loop_iterate` | Track each fix attempt |
-| `loop_complete` | Finish fix cycle |
-| `capture_knowledge` | Full anti-pattern capture |
-| `capture_quick` | Fast capture |
-| `curator_detect_duplicates` | Prevent redundant entries |
-| `admin_health` | Verify system health |

package/code-reviewer/skills/health-check/SKILL.md

@@ -1,225 +0,0 @@
----
-name: health-check
-description: Use when the user asks "check health", "vault health", "knowledge quality", "clean up vault", "groom knowledge", "maintenance", "housekeeping", "deduplicate", "find contradictions", or wants to run a maintenance cycle on the knowledge base to keep it healthy and accurate.
----
-
-# Health Check — Knowledge Base Maintenance
-
-Run a comprehensive maintenance cycle on the knowledge base. Finds stale entries, duplicates, contradictions, quality issues, and fixes them. Like a doctor's checkup for your knowledge.
-
-## When to Use
-
-- Weekly/monthly maintenance ritual
-- "Is my vault healthy?"
-- "Clean up my knowledge base"
-- Before a retrospective (clean data = better insights)
-- After a knowledge harvest (post-ingest quality check)
-
-## The Magic: Comprehensive Quality Audit
-
-### Step 1: System Health
-
-```
-code-reviewer_core op:admin_health
-```
-
-```
-code-reviewer_core op:admin_diagnostic
-```
-
-Catches infrastructure issues — database corruption, stale caches, configuration problems.
-
-### Step 2: Vault Metrics
-
-```
-code-reviewer_core op:admin_vault_size
-```
-
-```
-code-reviewer_core op:admin_vault_analytics
-```
-
-```
-code-reviewer_core op:vault_domains
-```
-
-```
-code-reviewer_core op:vault_tags
-```
-
-Shows the big picture: how many entries, which domains, tag distribution.
-
-### Step 3: Quality Audit
-
-Run the curator's health audit — the most comprehensive quality check:
-
-```
-code-reviewer_core op:curator_health_audit
-```
-
-This checks: tag normalization, description quality, severity distribution, domain coverage balance, and overall vault quality score.
-
-### Step 4: Find Duplicates
-
-```
-code-reviewer_core op:curator_detect_duplicates
-```
-
-Present duplicates for review. Offer to merge or remove them.
-
-### Step 5: Find Contradictions
-
-```
-code-reviewer_core op:curator_contradictions
-```
-
-Contradictions are entries that give conflicting advice. Present each pair for the user to resolve:
-
-```
-code-reviewer_core op:curator_resolve_contradiction
-  params: { contradictionId: "<id>" }
-```
-
-### Step 6: Find Stale Entries
-
-```
-code-reviewer_core op:vault_age_report
-```
-
-Entries older than 30 days without updates are candidates for:
-- Refresh (still relevant, needs updating)
-- Archive (no longer relevant)
-- Delete (incorrect or superseded)
-
-### Step 7: Check Search Quality
-
-```
-code-reviewer_core op:admin_search_insights
-```
-
-Shows what people search for but don't find — these are knowledge gaps that should be filled.
-
-### Step 8: Memory Health
-
-```
-code-reviewer_core op:memory_stats
-```
-
-```
-code-reviewer_core op:memory_deduplicate
-```
-
-Clean up duplicate memories.
-
-### Step 9: Governance Queue
-
-Check if any proposals are pending review:
-
-```
-code-reviewer_core op:governance_proposals
-  params: { action: "list" }
-```
-
-```
-code-reviewer_core op:governance_stats
-```
-
-Expire stale proposals:
-
-```
-code-reviewer_core op:governance_expire
-```
-
-### Step 10: Fix Everything (Optional)
-
-If the user approves, run the full cleanup:
-
-**Groom all entries — normalize tags, fix metadata:**
-```
-code-reviewer_core op:curator_groom_all
-```
-
-**Full consolidation — deduplicate, normalize, quality-score:**
-```
-code-reviewer_core op:curator_consolidate
-```
-
-**Prune stale memory:**
-```
-code-reviewer_core op:memory_prune
-```
-
-**Rebuild brain intelligence with clean data:**
-```
-code-reviewer_core op:brain_build_intelligence
-```
-
-**Reset caches to pick up changes:**
-```
-code-reviewer_core op:admin_reset_cache
-```
-
-## Presenting the Health Report
-
-```
-## Knowledge Health Report
-
-### System
-| Check | Status |
-|-------|--------|
-| Infrastructure | OK / Issues |
-| Database | OK / Issues |
-| Cache | OK / Issues |
-
-### Vault Quality
-| Metric | Value | Status |
-|--------|-------|--------|
-| Total entries | X | — |
-| Quality score | X/100 | Good/Warning/Critical |
-| Domains | X | — |
-| Tags | X | — |
-
-### Issues Found
-| Issue | Count | Action |
-|-------|-------|--------|
-| Duplicates | X | Merge |
-| Contradictions | X | Resolve |
-| Stale entries (>30d) | X | Review |
-| Search misses | X | Fill gaps |
-| Pending proposals | X | Review |
-
-### Recommended Actions
-1. [Most impactful fix]
-2. [Second most impactful]
-3. [Third most impactful]
-```
-
-## The Magic
-
-This feels like magic because knowledge bases normally decay silently — duplicates accumulate, entries go stale, contradictions creep in, gaps grow. This skill makes decay visible and fixable in one command. It's like having a librarian who does a weekly audit of every book on every shelf.
-
-## Agent Tools Reference
-
-| Op | When to Use |
-|----|-------------|
-| `admin_health` | System health check |
-| `admin_diagnostic` | Comprehensive system diagnostic |
-| `admin_vault_size` | Vault storage metrics |
-| `admin_vault_analytics` | Knowledge quality metrics |
-| `admin_search_insights` | Search miss analysis |
-| `admin_reset_cache` | Clear caches after cleanup |
-| `vault_domains` / `vault_tags` | Knowledge landscape |
-| `vault_age_report` | Stale entry detection |
-| `curator_health_audit` | Quality score and audit |
-| `curator_detect_duplicates` | Find duplicates |
-| `curator_contradictions` | Find conflicting entries |
-| `curator_resolve_contradiction` | Resolve conflicts |
-| `curator_groom_all` | Batch tag normalization |
-| `curator_consolidate` | Full cleanup pipeline |
-| `memory_stats` | Memory health |
-| `memory_deduplicate` | Remove duplicate memories |
-| `memory_prune` | Remove stale memories |
-| `governance_proposals` | Pending review queue |
-| `governance_stats` | Governance metrics |
-| `governance_expire` | Expire stale proposals |
-| `brain_build_intelligence` | Rebuild after cleanup |