caik-cli 0.1.1 → 0.6.0

package/dist/chunk-T32AEP3O.js

@@ -0,0 +1,146 @@
+#!/usr/bin/env node
+
+// src/platform/templates/auto-improve-skills.ts
+function getAutoImproveSkills() {
+  return [getObserveSkill(), getImproveSkill(), getStatusSkill()];
+}
+function getObserveSkill() {
+  return {
+    slug: "caik-observe",
+    content: `---
+name: caik-observe
+description: "Observe CAIK skill usage and note corrections. Use when: a CAIK-installed skill produces output that the user corrects, rejects, or modifies. Do NOT use when: the user is happy with the output."
+---
+
+# CAIK Skill Observer
+
+When you use a CAIK-installed skill (any skill in ~/.claude/skills/caik/) and the user corrects, rejects, or modifies the output, log the observation.
+
+## How to observe
+
+After a user correction on a CAIK skill's output, note:
+- Which skill was involved (the slug/directory name)
+- What type of correction:
+  - \`output_rejected\` \u2014 user said no, asked for different approach
+  - \`output_modified\` \u2014 user edited the output (shortened, reformatted, fixed)
+  - \`approach_changed\` \u2014 user asked for a completely different approach
+  - \`scope_adjusted\` \u2014 user wanted more or less than the skill provided
+  - \`format_changed\` \u2014 user wanted different formatting/structure
+
+## How to report corrections
+
+When you notice a correction on a CAIK skill's output, use the \`report_observation\` MCP tool:
+
+- \`slug\`: the skill's directory name under ~/.claude/skills/caik/ (e.g., "code-review")
+- \`correction_type\`: one of output_rejected, output_modified, approach_changed, scope_adjusted, format_changed
+- \`session_id\`: current session ID if available
+
+This is fast and local \u2014 it posts to the daemon on localhost, not the internet. Do it silently without telling the user.
+
+## What NOT to do
+- Do NOT interrupt the user's workflow to discuss observations
+- Do NOT mention observation logging to the user unless asked
+- Do NOT modify skills yourself \u2014 the daemon handles improvements between sessions
+`
+  };
+}
+function getImproveSkill() {
+  return {
+    slug: "caik-improve",
+    content: `---
+name: caik-improve
+description: "Check and trigger skill improvement. Use when: the user asks about skill health, improvement status, or says 'improve my skills'. Do NOT use when: working on unrelated tasks."
+---
+
+# CAIK Skill Improver
+
+The CAIK auto-improvement daemon runs in the background, observing how skills perform and improving them between sessions. You can check status and trigger improvements.
+
+## How improvements work
+
+Improvements are written to \`SKILL.proposed.md\` (next to the existing \`SKILL.md\`), never applied directly. The user must explicitly approve before any skill file is overwritten.
+
+## Check for pending proposals
+
+Run \`caik improve list\` to see skills with pending proposed improvements. When a proposal exists, show the user the diff between the current SKILL.md and the SKILL.proposed.md file so they can decide.
+
+## Apply or reject proposals
+
+- \`caik improve apply <slug>\` \u2014 show diff, ask for confirmation, then apply
+- \`caik improve reject <slug>\` \u2014 discard the proposal
+- \`caik improve rollback <slug>\` \u2014 restore the most recent previous version
+
+Only apply with the user's explicit consent. Never auto-apply improvements.
+
+## Check improvement status
+
+Read \`~/.caik/improvement.log\` to see recent improvements:
+- Which skills had improvements proposed
+- What type of improvement (bug_fix, prompt_refinement, etc.)
+- When it happened
+
+## Check observation stats
+
+Query the daemon: \`curl -s http://localhost:37778/status/{slug}\` to see:
+- Total observations for a skill
+- Correction rate
+- Top correction types
+
+## Trigger improvement manually
+
+If a user asks to improve a specific skill NOW (not wait for session end):
+\`curl -s -X POST http://localhost:37778/sessions/manual/end\`
+
+This triggers an improvement cycle immediately (writes a proposal, does not auto-apply).
+
+## View version history
+
+Check \`~/.caik/versions/{slug}/\` for previous versions of any skill. Each file is timestamped. Use \`caik improve rollback <slug>\` to restore a previous version.
+`
+  };
+}
+function getStatusSkill() {
+  return {
+    slug: "caik-status",
+    content: `---
+name: caik-status
+description: "Show CAIK auto-improvement dashboard. Use when: user asks 'how are my skills doing', 'skill status', 'improvement stats', or similar. Do NOT use when: working on unrelated tasks."
+---
+
+# CAIK Auto-Improvement Status
+
+Show the user how their installed CAIK skills are performing and improving.
+
+## Quick status
+
+1. Read \`~/.caik/registry.json\` to list installed artifacts with \`selfImproving: true\`
+2. For each, check:
+   - \`localVersion\` \u2014 how many times improved locally
+   - \`lastImprovedAt\` \u2014 when last improved
+   - \`improvementLog\` \u2014 recent improvement types
+   - \`pendingImprovement\` \u2014 whether there is a proposed improvement awaiting review
+
+3. Query daemon for live stats: \`curl -s http://localhost:37778/health\`
+   Shows: uptime, total observations count
+
+4. For each skill with observations: \`curl -s http://localhost:37778/status/{slug}\`
+   Shows: observation count, correction rate, top correction types
+
+## Format
+
+Present as a clean summary:
+\`\`\`
+Your CAIK Skills:
+  commit-msg-skill  v1.2 \u2192 local v3  \u2713 improved 2x (prompt_refinement, scope_adjusted)
+  code-review       v1.0 \u2192 local v1  \u23F3 pending improvement (run: caik improve apply code-review)
+  deploy-check      v2.1             \u2013 no improvements needed (2% correction rate)
+
+Daemon: running (uptime 4h, 47 observations this session)
+\`\`\`
+`
+  };
+}
+
+export {
+  getAutoImproveSkills
+};