cokit-cli 1.2.7 → 1.4.0

package/skills/context-engineering/references/runtime-awareness.md

@@ -1,202 +0,0 @@
-# Runtime Awareness
-
-Monitor usage limits and context window utilization in real-time to optimize AI agent sessions.
-
-## Overview
-
-Runtime awareness provides visibility into two critical metrics:
-1. **Usage Limits** - API quota consumption (5-hour and 7-day rolling windows)
-2. **Context Window** - Current token utilization within the 200K context limit
-
-## Architecture
-
-```
-┌─────────────────┐    ┌──────────────────────────┐
-│  statusline.cjs │───▶│  /tmp/ck-context-*.json  │
-│  (writes data)  │    │  (context window data)   │
-└─────────────────┘    └────────────┬─────────────┘
-                                    │
-                       ┌────────────▼─────────────┐
-                       │  usage-context-hook.cjs  │◀── PostToolUse
-                       │  - Reads context file    │
-                       │  - Fetches usage limits  │
-                       │  - Injects awareness     │
-                       └──────────────────────────┘
-```
-
-## Usage Limits API
-
-### Endpoint
-
-```
-GET <platform-specific-usage-endpoint>
-```
-
-### Authentication
-
-Requires OAuth Bearer token with platform-specific headers.
-
-### Credential Locations
-
-| Platform | Method | Location |
-|----------|--------|----------|
-| macOS | Keychain | `agent-credentials` |
-| Windows | File | `%USERPROFILE%.copilot\.credentials.json` |
-| Linux | File | `~/.copilot/.credentials.json` |
-
-### Response Structure
-
-```json
-{
-  "five_hour": {
-    "utilization": 45,
-    "resets_at": "2025-01-15T18:00:00Z"
-  },
-  "seven_day": {
-    "utilization": 32,
-    "resets_at": "2025-01-22T00:00:00Z"
-  },
-  "seven_day_sonnet": {
-    "utilization": 11,
-    "resets_at": "2025-01-15T09:00:00Z"
-  }
-}
-```
-
-- `utilization`: Already a percentage (0-100), NOT a decimal
-- `resets_at`: ISO 8601 timestamp when quota resets
-- `seven_day_sonnet`: Model-specific limit (may be null)
-
-## Context Window Data
-
-### Source
-
-Statusline writes context data to `/tmp/ck-context-{session_id}.json`:
-
-```json
-{
-  "percent": 67,
-  "tokens": 134000,
-  "size": 200000,
-  "usage": {
-    "input_tokens": 80000,
-    "cache_creation_input_tokens": 30000,
-    "cache_read_input_tokens": 24000
-  },
-  "timestamp": 1705312000000
-}
-```
-
-### Token Calculation
-
-```
-total = input_tokens + cache_creation_input_tokens + cache_read_input_tokens
-percent = (total + AUTOCOMPACT_BUFFER) / context_window_size * 100
-```
-
-Where `AUTOCOMPACT_BUFFER = 45000` (22.5% reserved).
-
-## Hook Output
-
-The PostToolUse hook injects awareness data every 5 minutes:
-
-```xml
-<usage-awareness>
-Limits: 5h=45%, 7d=32%
-Context: 67%
-</usage-awareness>
-```
-
-### Warning Indicators
-
-| Level | Threshold | Indicator |
-|-------|-----------|-----------|
-| Normal | < 70% | Plain percentage |
-| Warning | 70-89% | `[WARNING]` |
-| Critical | ≥ 90% | `[CRITICAL]` |
-
-### Examples
-
-Normal state:
-```xml
-<usage-awareness>
-Limits: 5h=45%, 7d=32%
-Context: 67%
-</usage-awareness>
-```
-
-Warning state:
-```xml
-<usage-awareness>
-Limits: 5h=75% [WARNING], 7d=32%
-Context: 78% [WARNING - consider compaction]
-</usage-awareness>
-```
-
-Critical state:
-```xml
-<usage-awareness>
-Limits: 5h=92% [CRITICAL], 7d=65%
-Context: 91% [CRITICAL - compaction needed]
-</usage-awareness>
-```
-
-## Recommendations by Threshold
-
-### Context Window
-
-| Utilization | Action |
-|-------------|--------|
-| < 70% | Continue normally |
-| 70-80% | Plan compaction strategy |
-| 80-90% | Execute compaction |
-| > 90% | Immediate compaction or session reset |
-
-### Usage Limits
-
-| 5-Hour | Action |
-|--------|--------|
-| < 70% | Normal usage |
-| 70-90% | Reduce parallelization, delegate to agents |
-| > 90% | Wait for reset or use lower-tier models |
-
-| 7-Day | Action |
-|-------|--------|
-| < 70% | Normal usage |
-| 70-90% | Monitor daily consumption |
-| > 90% | Limit usage to essential tasks |
-
-## Configuration
-
-### Hook Settings (`$HOME/.copilot/settings.json`)
-
-```json
-{
-  "hooks": {
-    "PostToolUse": [
-      {
-        "matcher": "*",
-        "hooks": [{
-          "type": "command",
-          "command": "node $HOME/.copilot/hooks/usage-context-awareness.cjs"
-        }]
-      }
-    ]
-  }
-}
-```
-
-### Throttling
-
-- **Injection interval**: 5 minutes (300,000ms)
-- **API cache TTL**: 60 seconds
-- **Context data freshness**: 30 seconds
-
-## Troubleshooting
-
-| Issue | Cause | Solution |
-|-------|-------|----------|
-| No usage limits shown | No OAuth token | Run the agent login command |
-| Stale context data | Statusline not updating | Check statusline config |
-| 401 Unauthorized | Expired token | Re-authenticate |
-| Hook not firing | Settings misconfigured | Verify PostToolUse matcher |

package/skills/cook/README.md

@@ -1,86 +0,0 @@
-# Cook Skill
-
-End-to-end feature implementation with smart intent detection.
-
-## Installation
-
-Copy the `cook/` folder to your skills directory:
-```bash
-cp -r cook ~/.copilot/skills/
-```
-
-## Usage
-
-```bash
-/cook <natural language task OR plan path>
-```
-
-The skill automatically detects your intent and routes to the appropriate workflow.
-
-## Examples
-
-```bash
-# Interactive mode (default)
-/cook implement user authentication
-
-# Execute existing plan
-/cook plans/260120-auth
-
-# Fast mode (skip research)
-/cook quick fix for login bug
-/cook implement feature --fast
-
-# Auto mode (trust me bro)
-/cook implement dashboard trust me
-/cook implement feature --auto
-
-# Parallel mode (multi-agent)
-/cook implement auth, payments, notifications
-/cook implement feature --parallel
-
-# No-test mode
-/cook implement feature --no-test
-```
-
-## Modes
-
-| Mode | Research | Testing | Review | Use Case |
-|------|----------|---------|--------|----------|
-| interactive | ✓ | ✓ | User approval | Default, full control |
-| auto | ✓ | ✓ | Auto if score≥9.5 | Trusted, hands-off |
-| fast | ✗ | ✓ | Simplified | Quick fixes |
-| parallel | Optional | ✓ | User approval | Multi-feature work |
-| no-test | ✓ | ✗ | User approval | Speed priority |
-| code | ✗ | ✓ | User approval | Existing plans |
-
-## Intent Detection
-
-The skill detects mode from:
-1. **Explicit flags:** `--fast`, `--auto`, `--parallel`, `--no-test`
-2. **Plan paths:** `./plans/*`, `plan.md`, `phase-*.md`
-3. **Keywords:** "fast", "quick", "trust me", "auto", "no test"
-4. **Feature count:** 3+ features → parallel mode
-
-## Workflow
-
-```
-[Intent Detection] → [Research?] → [Plan] → [Implement] → [Test?] → [Review] → [Finalize]
-```
-
-## Files
-
-```
-cook/
-├── SKILL.md                           # Main skill definition
-├── README.md                          # This file
-└── references/
-    ├── intent-detection.md            # Detection rules
-    ├── workflow-steps.md              # Step definitions
-    ├── review-cycle.md                # Review process
-    └── agent-patterns.md               # Agent usage
-```
-
-## Version
-
-2.1.0 - Review gates added for human-in-the-loop mode
-2.0.0 - Smart intent detection (hybrid approach)

package/skills/cook/SKILL.md

@@ -1,127 +0,0 @@
----
-name: cook
-description: ALWAYS activate this skill before implementing EVERY feature, plan, or fix.
----
-
-# Cook - Smart Feature Implementation
-
-End-to-end implementation with automatic workflow detection.
-
-**Principles:** YAGNI, KISS, DRY | Token efficiency | Concise reports
-
-## Usage
-
-```
-/cook <natural language task OR plan path>
-```
-
-**Optional flags:** `--fast`, `--parallel`, `--no-test`, `--auto`, `--interactive`
-
-Example:
-```
-/cook "Add user authentication to the app" --fast
-/cook path/to/plan.md --auto
-/cook "Fix login bug" --interactive
-```
-
-## Smart Intent Detection
-
-| Input Pattern | Detected Mode | Behavior |
-|---------------|---------------|----------|
-| Path to `plan.md` or `phase-*.md` | code | Execute existing plan |
-| Contains "fast", "quick" | fast | Skip research, scout→plan→code |
-| Contains "trust me", "auto" | auto | Auto-approve all steps |
-| Lists 3+ features OR "parallel" | parallel | Multi-agent execution |
-| Contains "no test", "skip test" | no-test | Skip testing step |
-| `--interactive` flag (explicit) | interactive | Full workflow with user input |
-| Default | interactive | Full workflow with user input |
-
-See `references/intent-detection.md` for detection logic.
-
-## Workflow Overview
-
-```
-[Intent Detection] → [Research?] → [Review] → [Plan] → [Review] → [Implement] → [Review] → [Test?] → [Review] → [Finalize]
-```
-
-**Default (non-auto):** Stops at `[Review]` gates for human approval before each major step.
-**Auto mode (`--auto`):** Skips human review gates, implements all phases continuously.
-
-| Mode | Research | Testing | Review Gates | Phase Progression |
-|------|----------|---------|--------------|-------------------|
-| interactive | ✓ | ✓ | **User approval at each step** | One at a time |
-| auto | ✓ | ✓ | Auto if score≥9.5 | All at once (no stops) |
-| fast | ✗ | ✓ | User approval at each step | One at a time |
-| parallel | Optional | ✓ | User approval at each step | Parallel groups |
-| no-test | ✓ | ✗ | User approval at each step | One at a time |
-| code | ✗ | ✓ | User approval at each step | Per plan |
-
-## Step Output Format
-
-```
-✓ Step [N]: [Brief status] - [Key metrics]
-```
-
-## Blocking Gates (Non-Auto Mode)
-
-Human review required at these checkpoints (skipped with `--auto`):
-- **Post-Research:** Review findings before planning
-- **Post-Plan:** Approve plan before implementation
-- **Post-Implementation:** Approve code before testing
-- **Post-Testing:** 100% pass + approve before finalize
-
-**Always enforced (all modes):**
-- **Testing:** 100% pass required (unless no-test mode)
-- **Code Review:** User approval OR auto-approve (score≥9.5, 0 critical)
-- **Finalize:** docs-manager MUST complete
-
-## Required Agents
-
-| Phase | Agent | Requirement |
-|-------|-------|-------------|
-| Research | `researcher` agent (parallel, optional in fast) | Spawn as needed |
-| Scout | `scout` agent | Spawn for codebase search |
-| Plan | `planner` agent | MUST spawn |
-| UI Work | `ui-ux-designer` agent | Spawn when frontend work exists |
-| Testing | `tester`, `debugger` agents | MUST spawn |
-| Review | `code-reviewer` agent | MUST spawn |
-| Finalize | `docs-manager`, `git-manager` agents | MUST spawn |
-
-## Implementation Progress Tracking
-
-During Step 3 (Implementation), track progress using a todo list/checklist in the active plan or phase file:
-
-```
-- [ ] Phase 1: Setup environment
-- [ ] Phase 2: Database models
-- [ ] Phase 3: API endpoints
-- [ ] Phase 4: UI components
-```
-
-Update each item as completed. This replaces task management tooling with simple markdown tracking visible in the plan.
-
-## CRITICAL ENFORCEMENT
-
-**Steps 4 (Testing), 5 (Code Review), and 6 (Finalize) MUST delegate to agents. DO NOT implement testing, review, or finalization yourself.**
-
-- Step 4: Always delegate to `tester` agent. If failures, delegate to `debugger` agent, then re-delegate to `tester`.
-- Step 5: Always delegate to `code-reviewer` agent. Never self-review.
-- Step 6: Always delegate to `docs-manager` agent for doc updates.
-
-## Finalize Step (MANDATORY)
-
-Step 6 is not optional. All four actions MUST complete:
-
-1. Update plan/phase status to completed in plan files
-2. Delegate to `docs-manager` agent → review and update `./docs` if implementation changed APIs, architecture, or behavior
-3. Mark all todo checklist items complete in the active plan
-4. Ask the user: "Would you like to commit these changes via `git-manager` agent?"
-
-**Never skip finalize**, even in fast or auto mode.
-
-## References
-
-- `references/intent-detection.md` - Detection rules and routing logic
-- `references/workflow-steps.md` - Detailed step definitions for all modes
-- `references/review-cycle.md` - Interactive and auto review processes
-- `references/agent-patterns.md` - Agent invocation patterns

package/skills/cook/references/intent-detection.md

@@ -1,101 +0,0 @@
-# Intent Detection Logic
-
-Detect user intent from natural language and route to appropriate workflow.
-
-## Detection Algorithm
-
-```
-FUNCTION detectMode(input):
-  # Priority 1: Explicit flags (override all)
-  IF input contains "--fast": RETURN "fast"
-  IF input contains "--parallel": RETURN "parallel"
-  IF input contains "--auto": RETURN "auto"
-  IF input contains "--no-test": RETURN "no-test"
-
-  # Priority 2: Plan path detection
-  IF input matches path pattern (./plans/*, plan.md, phase-*.md):
-    RETURN "code"
-
-  # Priority 3: Keyword detection (case-insensitive)
-  keywords = lowercase(input)
-
-  IF keywords contains ["fast", "quick", "rapidly", "asap"]:
-    RETURN "fast"
-
-  IF keywords contains ["trust me", "auto", "yolo", "just do it"]:
-    RETURN "auto"
-
-  IF keywords contains ["no test", "skip test", "without test"]:
-    RETURN "no-test"
-
-  # Priority 4: Complexity detection
-  features = extractFeatures(input)  # comma-separated or "and"-joined items
-  IF count(features) >= 3 OR keywords contains "parallel":
-    RETURN "parallel"
-
-  # Default: interactive workflow
-  RETURN "interactive"
-```
-
-## Feature Extraction
-
-Detect multiple features from natural language:
-
-```
-"implement auth, payments, and notifications" → ["auth", "payments", "notifications"]
-"add login + signup + password reset"        → ["login", "signup", "password reset"]
-"create dashboard with charts and tables"    → single feature (dashboard)
-```
-
-**Parallel trigger:** 3+ distinct features = parallel mode
-
-## Mode Behaviors
-
-| Mode | Skip Research | Skip Test | Review Gates | Auto-Approve | Parallel Exec |
-|------|---------------|-----------|--------------|--------------|---------------|
-| interactive | ✗ | ✗ | **Yes (stops)** | ✗ | ✗ |
-| auto | ✗ | ✗ | **No (skips)** | ✓ (score≥9.5) | ✓ (all phases) |
-| fast | ✓ | ✗ | Yes (stops) | ✗ | ✗ |
-| parallel | Optional | ✗ | Yes (stops) | ✗ | ✓ |
-| no-test | ✗ | ✓ | Yes (stops) | ✗ | ✗ |
-| code | ✓ | ✗ | Yes (stops) | Per plan | Per plan |
-
-**Review Gates:** Human approval checkpoints between major steps (see `workflow-steps.md`).
-- All modes EXCEPT `auto` stop at review gates for human approval.
-- `auto` mode is the only mode that runs continuously without stopping.
-
-## Examples
-
-```
-"/cook implement user auth"
-→ Mode: interactive (default, stops at review gates)
-
-"/cook plans/260120-auth/phase-02-api.md"
-→ Mode: code (path detected, stops at review gates)
-
-"/cook quick fix for the login bug"
-→ Mode: fast ("quick" keyword, stops at review gates)
-
-"/cook implement auth, payments, notifications, shipping"
-→ Mode: parallel (4 features, stops at review gates)
-
-"/cook implement dashboard --fast"
-→ Mode: fast (explicit flag, stops at review gates)
-
-"/cook implement everything --auto"
-→ Mode: auto (NO STOPS, implements all phases continuously)
-
-"/cook implement dashboard trust me"
-→ Mode: auto ("trust me" keyword, NO STOPS)
-```
-
-**Note:** Only `--auto` flag or "trust me"/"auto"/"yolo" keywords enable continuous execution.
-
-## Conflict Resolution
-
-When multiple signals detected, priority order:
-1. Explicit flags (`--fast`, `--auto`, etc.)
-2. Path detection (plan files)
-3. Keywords in text
-4. Feature count analysis
-5. Default (interactive)

package/skills/cook/references/review-cycle.md

@@ -1,75 +0,0 @@
-# Code Review Cycle
-
-Interactive review-fix cycle used in code workflows.
-
-## Interactive Cycle (max 3 cycles)
-
-```
-cycle = 0
-LOOP:
-  1. Run code-reviewer → score, critical_count, warnings, suggestions
-
-  2. DISPLAY FINDINGS:
-     ┌─────────────────────────────────────────┐
-     │ Code Review Results: [score]/10         │
-     ├─────────────────────────────────────────┤
-     │ Summary: [what implemented], tests      │
-     │ [X/X passed]                            │
-     ├─────────────────────────────────────────┤
-     │ Critical Issues ([N]): MUST FIX         │
-     │  - [issue] at [file:line]               │
-     │ Warnings ([N]): SHOULD FIX              │
-     │  - [issue] at [file:line]               │
-     │ Suggestions ([N]): NICE TO HAVE         │
-     │  - [suggestion]                         │
-     └─────────────────────────────────────────┘
-
-  3. Ask user directly (header: "Review & Approve") — then wait for response:
-     IF critical_count > 0:
-       - "Fix critical issues" → fix, re-run tester, cycle++, LOOP
-       - "Fix all issues" → fix all, re-run tester, cycle++, LOOP
-       - "Approve anyway" → PROCEED
-       - "Abort" → stop
-     ELSE:
-       - "Approve" → PROCEED
-       - "Fix warnings/suggestions" → fix, cycle++, LOOP
-       - "Abort" → stop
-
-  4. IF cycle >= 3 AND user selects fix:
-     → "⚠ 3 review cycles completed. Final decision required."
-     → Ask user: "Approve with noted issues" / "Abort workflow" — wait for response
-```
-
-## Auto-Handling Cycle (for auto modes)
-
-```
-cycle = 0
-LOOP:
-  1. Run code-reviewer → score, critical_count, warnings
-
-  2. IF score >= 9.5 AND critical_count == 0:
-     → Auto-approve, PROCEED
-
-  3. ELSE IF critical_count > 0 AND cycle < 3:
-     → Auto-fix critical issues
-     → Re-run tester
-     → cycle++, LOOP
-
-  4. ELSE IF critical_count > 0 AND cycle >= 3:
-     → ESCALATE TO USER
-
-  5. ELSE (no critical, score < 9.5):
-     → Approve with warnings logged, PROCEED
-```
-
-## Critical Issues Definition
-- Security: XSS, SQL injection, OWASP vulnerabilities
-- Performance: bottlenecks, inefficient algorithms
-- Architecture: violations of patterns, coupling
-- Principles: YAGNI, KISS, DRY violations
-
-## Output Formats
-- Waiting: `⏸ Step 4: Code reviewed - [score]/10 - WAITING for approval`
-- After fix: `✓ Step 4: [old]/10 → Fixed [N] issues → [new]/10 - Approved`
-- Auto-approved: `✓ Step 4: Code reviewed - 9.8/10 - Auto-approved`
-- Approved: `✓ Step 4: Code reviewed - [score]/10 - User approved`