prizmkit 1.0.0 → 1.0.2

package/bundled/skills/bug-planner/SKILL.md

@@ -0,0 +1,235 @@
+---
+name: "bug-planner"
+tier: companion
+description: "Interactive bug planning that produces bug-fix-list.json for the Bug Fix Pipeline. Supports multiple input formats: error logs, stack traces, user reports, failed tests, monitoring alerts. (project)"
+---
+
+# Bug Planner
+
+Interactive skill that collects bug information from various input formats and generates a standardized `bug-fix-list.json` for the Bug Fix Pipeline. This is the bug-fix counterpart to `app-planner` (which generates `feature-list.json`).
+
+## When to Use
+
+User says:
+- "plan bug fixes", "report bugs", "create bug list"
+- "修复 bug", "生成 bug 列表", "规划 bug 修复"
+- "I have some bugs to fix", "these tests are failing"
+- "here's an error log", "parse these errors"
+- After receiving bug reports, error logs, or failed test output
+
+## Commands
+
+### prizmkit.bug-plan
+
+Launch the interactive bug planning process.
+
+### prizmkit.bug-plan-from-log \<log-file-or-content\>
+
+Auto-generate bug entries from error logs or stack traces.
+
+### prizmkit.bug-plan-from-tests \<test-output\>
+
+Auto-generate bug entries from failed test case output.
+
+### prizmkit.bug-plan-validate \<bug-fix-list.json\>
+
+Validate an existing `bug-fix-list.json` against the schema.
+
+### prizmkit.bug-plan-summary \<bug-fix-list.json\>
+
+Print a summary of bugs grouped by severity and status.
+
+---
+
+## Interactive Planning Process
+
+The interactive `prizmkit.bug-plan` command guides through 4 phases:
+
+### Phase 1: Project Context
+
+1. **Identify project**: Read project name and description from existing `feature-list.json` or ask user
+2. **Identify tech stack**: Read from `feature-list.json` global_context or `.prizm-docs/root.prizm`, or ask user
+3. **Identify testing framework**: Auto-detect from package.json/requirements.txt/etc., or ask user
+
+Output: `project_name`, `project_description`, `global_context` fields populated.
+
+### Phase 2: Bug Collection
+
+Accept bug information in ANY of these formats (auto-detect):
+
+#### Format A: Stack Trace / Error Log
+```
+TypeError: Cannot read property 'token' of null
+    at AuthService.handleLogin (src/services/auth.ts:42)
+    at LoginPage.onSubmit (src/pages/login.tsx:28)
+```
+→ Auto-extract: `error_source.type="stack_trace"`, `error_message`, `stack_trace`, `affected_modules`
+
+#### Format B: Natural Language User Report
+```
+When I click the login button with correct credentials, the page turns white.
+Expected: redirect to home page.
+Actual: white screen with no error message visible.
+```
+→ Auto-extract: `error_source.type="user_report"`, `reproduction_steps`, `description` (expected vs actual)
+
+#### Format C: Failed Test Output
+```
+FAIL src/services/__tests__/auth.test.ts
+  ● AuthService > handleLogin > should return token on success
+    Expected: "abc123"
+    Received: null
+```
+→ Auto-extract: `error_source.type="failed_test"`, `failed_test_path`, `error_message`
+
+#### Format D: Log Pattern
+```
+[2026-03-07 10:23:45] ERROR [auth-service] Connection timeout after 30000ms
+[2026-03-07 10:23:45] ERROR [auth-service] Failed to authenticate user: ETIMEDOUT
+[2026-03-07 10:23:46] ERROR [auth-service] Connection timeout after 30000ms
+```
+→ Auto-extract: `error_source.type="log_pattern"`, `log_snippet`, `affected_modules`
+
+#### Format E: Monitoring Alert
+```
+ALERT: CPU usage > 95% for auth-service pod (5min avg)
+ALERT: Error rate spike: 500 errors/min on /api/login endpoint
+```
+→ Auto-extract: `error_source.type="monitoring_alert"`, `error_message`, `affected_modules`
+
+**For each bug collected**, interactively confirm or fill in:
+- Title (auto-suggest from error message, user can edit)
+- Description (auto-generate expected vs actual, user can edit)
+- Severity (auto-suggest based on error type, user can override)
+- Affected feature (ask if known, map to existing F-NNN IDs)
+- Environment (ask or auto-detect from logs)
+- Verification type (suggest `automated` by default, ask user)
+- Acceptance criteria (auto-suggest based on description, user can edit)
+
+**Multiple bugs per session**: After each bug, ask "Any more bugs to add? (yes/no)"
+
+### Phase 3: Prioritization & Review
+
+1. **Auto-assign priorities**: Based on severity (critical=1, high=2, medium=3, low=4), adjustable by user
+2. **Display summary table**:
+   ```
+   ID    | Title                        | Severity | Priority | Verification
+   B-001 | Login null reference crash    | critical | 1        | automated
+   B-002 | CSV export Chinese encoding   | medium   | 3        | hybrid
+   B-003 | Slow dashboard loading        | low      | 4        | manual
+   ```
+3. **Ask for adjustments**: "Want to reorder priorities, change severity, or remove any bugs?"
+4. **Detect potential duplicates**: If two bugs have similar error messages or affected modules, warn user
+
+### Phase 4: Generate & Validate
+
+1. **Generate `bug-fix-list.json`**: Conform to `dev-pipeline/templates/bug-fix-list-schema.json`
+2. **Validate against schema**: Auto-run validation
+3. **Write file** to project root (or user-specified path)
+4. **Output**: File path, summary, and next steps:
+   ```
+   ✅ bug-fix-list.json generated with 3 bugs (1 critical, 1 medium, 1 low)
+   
+   Next steps:
+   - Review: cat bug-fix-list.json
+   - Start fixing: say "开始修复" or "start fixing bugs" to launch the bugfix pipeline
+   - Or run directly: ./dev-pipeline/launch-bugfix-daemon.sh start bug-fix-list.json
+   - Fix one interactively: invoke prizmkit-bug-fix-workflow for each bug
+   ```
+
+---
+
+## Non-Interactive Commands
+
+### prizmkit.bug-plan-from-log
+
+Batch-parse error logs to generate bug entries without interactive prompts:
+
+1. Accept log file path or piped content
+2. Parse all unique errors (deduplicate by error message pattern)
+3. Auto-generate bug entries with:
+   - Title: first line of error message
+   - Description: full error context
+   - Severity: auto-classify (crash/OOM=critical, auth/timeout=high, validation=medium, other=low)
+   - error_source: populated from log content
+   - verification_type: default to `automated`
+   - acceptance_criteria: auto-generate "Error no longer occurs in [scenario]"
+4. Output draft `bug-fix-list.json` for user review
+5. Ask: "Review and confirm? You can edit individual entries."
+
+### prizmkit.bug-plan-from-tests
+
+Batch-parse failed test output:
+
+1. Accept test runner output (Jest, pytest, Go test, etc.)
+2. Parse each failed test case as a separate bug entry
+3. Auto-populate `failed_test_path`, `error_message`
+4. Set verification_type to `automated` (test already exists)
+5. Output draft `bug-fix-list.json`
+
+### prizmkit.bug-plan-validate
+
+Validate existing `bug-fix-list.json`:
+
+1. Check JSON syntax
+2. Validate against `dev-pipeline/templates/bug-fix-list-schema.json`
+3. Check for:
+   - Duplicate IDs
+   - Missing required fields
+   - Invalid status values
+   - Priority conflicts (same priority for different bugs)
+   - Invalid `affected_feature` references (if feature-list.json exists)
+4. Output: validation result with specific errors/warnings
+
+### prizmkit.bug-plan-summary
+
+Print human-readable summary:
+
+```
+Bug Fix List Summary: my-web-app
+═══════════════════════════════
+
+Total: 3 bugs
+By Severity: critical=1, high=0, medium=1, low=1
+By Status:   pending=3
+
+Bug List (by priority):
+  1. [B-001] Login null reference crash (CRITICAL) — automated
+  2. [B-002] CSV export Chinese encoding (MEDIUM) — hybrid
+  3. [B-003] Slow dashboard loading (LOW) — manual
+
+Affected Features: F-003 (1 bug), F-012 (1 bug), none (1 bug)
+```
+
+---
+
+## Integration with Bug Fix Pipeline
+
+After `bug-fix-list.json` is generated, the user can:
+
+1. **Say "开始修复" or "start fixing bugs"** — triggers `bugfix-pipeline-launcher` skill to auto-launch pipeline in background (recommended)
+2. **Background daemon**: `./dev-pipeline/launch-bugfix-daemon.sh start bug-fix-list.json`
+3. **Foreground run**: `./dev-pipeline/run-bugfix.sh run bug-fix-list.json`
+4. **Fix single bug interactively**: invoke `prizmkit-bug-fix-workflow` in current session
+5. **Retry a failed bug**: `./dev-pipeline/retry-bug.sh B-001`
+
+## Error Handling
+
+| Error | Action |
+|-------|--------|
+| Cannot parse error log format | Ask user to specify format or provide raw text |
+| Ambiguous severity classification | Present options, ask user to choose |
+| Duplicate bug detected | Warn user, suggest merging or keeping separate |
+| No bugs provided | Prompt with examples of supported input formats |
+| Invalid feature reference | Warn and ask user to correct or remove reference |
+| Schema validation failure | Show specific errors, offer to fix interactively |
+
+## Path References
+
+All internal asset paths MUST use `${SKILL_DIR}` placeholder for cross-IDE compatibility.
+
+## Output
+
+- `bug-fix-list.json` conforming to `dev-pipeline/templates/bug-fix-list-schema.json`
+- Validation report (if validation run)
+- Summary report (if summary run)

package/bundled/skills/bugfix-pipeline-launcher/SKILL.md

@@ -0,0 +1,252 @@
+---
+name: "bugfix-pipeline-launcher"
+description: "Launch and manage the bugfix pipeline from within a cbc session. Start pipeline in background, monitor logs, check status, stop pipeline. Invoke when user wants to start fixing bugs, run the bugfix pipeline, or check bugfix progress. (project)"
+---
+
+# Bugfix-Pipeline Launcher
+
+Launch the autonomous bug fix pipeline from within a cbc conversation. The pipeline runs as a fully detached background process -- closing the cbc session does NOT stop the pipeline.
+
+### When to Use
+
+**Start bugfix pipeline** -- User says:
+- "start fixing bugs", "run bugfix pipeline", "launch bug fixes", "fix all bugs"
+- "start bug fix", "run bug fix", "execute bug list", "begin fixing"
+- "启动 bug 修复", "开始修复 bug", "运行 bug 修复流水线", "开始修 bug"
+- "修复所有 bug", "批量修复", "启动修复流水线"
+- After bug-planner completes: "go", "start", "fix them", "开始吧", "开始修复"
+
+**Check status** -- User says:
+- "bugfix status", "check bug fixes", "how's the fixing going", "bug fix progress"
+- "修复进度", "bug 修复状态", "查看修复进度", "修复到哪了"
+
+**Stop bugfix pipeline** -- User says:
+- "stop bug fix", "stop fixing", "halt bugfix", "pause bug fix"
+- "停止修复", "暂停 bug 修复", "停止修复流水线"
+
+**Show logs** -- User says:
+- "bugfix logs", "show fix logs", "what's being fixed"
+- "查看修复日志", "修复日志", "看看修复情况"
+
+**Do NOT use this skill when:**
+- User wants to plan/collect bugs (use `bug-planner` instead)
+- User wants to fix a single bug interactively in current session (use `prizmkit-bug-fix-workflow`)
+- User wants to launch the feature pipeline (use `dev-pipeline-launcher`)
+
+### Prerequisites
+
+Before any action, validate:
+
+1. **bugfix pipeline exists**: Confirm `dev-pipeline/launch-bugfix-daemon.sh` is present and executable
+2. **For start**: `bug-fix-list.json` must exist in project root (or user-specified path)
+3. **Dependencies**: `jq`, `python3`, AI CLI (`cbc` or `claude`) must be in PATH
+
+Quick check:
+```bash
+command -v jq && command -v python3 && (command -v cbc || command -v claude) && echo "All dependencies OK"
+```
+
+If `bug-fix-list.json` is missing, inform user:
+> "No bug-fix-list.json found. Run the `bug-planner` skill first to generate one, or provide a path to your bug fix list."
+
+### Workflow
+
+Detect user intent from their message, then follow the corresponding workflow:
+
+---
+
+#### Intent A: Start Bugfix Pipeline
+
+1. **Check prerequisites**:
+   ```bash
+   ls bug-fix-list.json 2>/dev/null && echo "Found" || echo "Missing"
+   ```
+
+2. **Check not already running**:
+   ```bash
+   dev-pipeline/launch-bugfix-daemon.sh status 2>/dev/null
+   ```
+   If running, inform user and ask: "Bugfix pipeline is already running. Want to restart it, check status, or view logs?"
+
+3. **Show bug summary** (so user knows what will be fixed):
+   ```bash
+   python3 -c "
+   import json
+   with open('bug-fix-list.json') as f:
+       data = json.load(f)
+   bugs = data.get('bugs', [])
+   severity_order = {'critical': 0, 'high': 1, 'medium': 2, 'low': 3}
+   bugs_sorted = sorted(bugs, key=lambda b: (severity_order.get(b.get('severity', 'medium'), 2), b.get('priority', 99)))
+   print(f'Total bugs: {len(bugs)}')
+   sev_counts = {}
+   for b in bugs:
+       s = b.get('severity', 'medium')
+       sev_counts[s] = sev_counts.get(s, 0) + 1
+   print(f'By severity: {dict(sorted(sev_counts.items(), key=lambda x: severity_order.get(x[0], 2)))}')
+   print()
+   for b in bugs_sorted:
+       print(f\"  {b['id']}: [{b.get('severity','?').upper()}] {b.get('title', 'untitled')}\")
+   "
+   ```
+   If pipeline state already exists, use the status command instead:
+   ```bash
+   python3 dev-pipeline/scripts/update-bug-status.py \
+     --bug-list bug-fix-list.json \
+     --state-dir dev-pipeline/bugfix-state \
+     --action status 2>/dev/null
+   ```
+
+4. **Ask user to confirm**: "Ready to launch the bugfix pipeline? It will process N bugs (by severity order) in the background."
+
+5. **Launch**:
+   ```bash
+   dev-pipeline/launch-bugfix-daemon.sh start bug-fix-list.json
+   ```
+   If user specified environment overrides (e.g. timeout, retries, verbose):
+   ```bash
+   dev-pipeline/launch-bugfix-daemon.sh start bug-fix-list.json --env "SESSION_TIMEOUT=7200 MAX_RETRIES=5"
+   ```
+
+6. **Verify launch**:
+   ```bash
+   dev-pipeline/launch-bugfix-daemon.sh status
+   ```
+
+7. **Start log monitoring** -- Use the Bash tool with `run_in_background: true`:
+   ```bash
+   tail -f dev-pipeline/bugfix-state/pipeline-daemon.log
+   ```
+   This runs in background so you can continue interacting with the user.
+
+8. **Report to user**:
+   - Pipeline PID
+   - Log file location
+   - "You can ask me 'bugfix status' or 'show fix logs' at any time"
+   - "Closing this session will NOT stop the pipeline"
+
+---
+
+#### Intent B: Check Status
+
+1. **Check daemon status**:
+   ```bash
+   dev-pipeline/launch-bugfix-daemon.sh status
+   ```
+
+2. **Show bug-level progress**:
+   ```bash
+   python3 dev-pipeline/scripts/update-bug-status.py \
+     --bug-list bug-fix-list.json \
+     --state-dir dev-pipeline/bugfix-state \
+     --action status
+   ```
+
+3. **Show recent log activity** (last 20 lines):
+   ```bash
+   tail -20 dev-pipeline/bugfix-state/pipeline-daemon.log
+   ```
+
+4. **Summarize** to user: total bugs, completed, in-progress, failed, pending, needs-info.
+
+---
+
+#### Intent C: Stop Bugfix Pipeline
+
+1. **Stop the daemon**:
+   ```bash
+   dev-pipeline/launch-bugfix-daemon.sh stop
+   ```
+
+2. **Verify stopped**:
+   ```bash
+   dev-pipeline/launch-bugfix-daemon.sh status 2>/dev/null || true
+   ```
+
+3. **Inform user**: "Bugfix pipeline stopped. State is preserved -- you can resume later with 'start bug fix' and it will pick up where it left off."
+
+---
+
+#### Intent D: Show Logs
+
+1. **Check if running**:
+   ```bash
+   dev-pipeline/launch-bugfix-daemon.sh status 2>/dev/null
+   ```
+
+2. **If running** -- Start live tail with Bash tool `run_in_background: true`:
+   ```bash
+   tail -f dev-pipeline/bugfix-state/pipeline-daemon.log
+   ```
+
+3. **If not running** -- Show last 50 lines:
+   ```bash
+   tail -50 dev-pipeline/bugfix-state/pipeline-daemon.log
+   ```
+
+4. **For per-bug session logs** (when user asks about a specific bug):
+   ```bash
+   # Find current/recent session
+   cat dev-pipeline/bugfix-state/current-session.json 2>/dev/null
+   # Then tail that bug's session log
+   tail -100 dev-pipeline/bugfix-state/bugs/<BUG_ID>/sessions/<SESSION_ID>/logs/session.log
+   ```
+
+---
+
+#### Intent E: Custom Parameters
+
+When user specifies custom settings, map to environment variables:
+
+| User says | Environment variable |
+|-----------|---------------------|
+| "timeout 2 hours" / "超时2小时" | `SESSION_TIMEOUT=7200` |
+| "max 5 retries" / "最多重试5次" | `MAX_RETRIES=5` |
+| "verbose mode" / "详细模式" | `VERBOSE=1` |
+| "heartbeat every 60s" | `HEARTBEAT_INTERVAL=60` |
+
+Pass via `--env`:
+```bash
+dev-pipeline/launch-bugfix-daemon.sh start bug-fix-list.json --env "SESSION_TIMEOUT=7200 MAX_RETRIES=5 VERBOSE=1"
+```
+
+---
+
+#### Intent F: Retry Single Bug
+
+When user says "retry B-001" or "重试 B-001":
+
+```bash
+dev-pipeline/retry-bug.sh B-001 bug-fix-list.json
+```
+
+Or within the main pipeline (reset + resume):
+```bash
+python3 dev-pipeline/scripts/update-bug-status.py \
+  --bug-list bug-fix-list.json \
+  --state-dir dev-pipeline/bugfix-state \
+  --bug-id B-001 --action reset
+# Then restart pipeline to pick it up
+```
+
+### Error Handling
+
+| Error | Action |
+|-------|--------|
+| `bug-fix-list.json` not found | Tell user to run `bug-planner` skill first |
+| `jq` not installed | Suggest: `brew install jq` |
+| `cbc`/`claude` not in PATH | Check AI CLI installation |
+| Bugfix pipeline already running | Show status, ask if user wants to stop and restart |
+| PID file stale (process dead) | `launch-bugfix-daemon.sh` auto-cleans, retry start |
+| Launch failed (process died immediately) | Show last 20 lines of log: `tail -20 dev-pipeline/bugfix-state/pipeline-daemon.log` |
+| All bugs blocked/failed/needs-info | Show status, suggest retrying or providing more info |
+| Permission denied on script | Run `chmod +x dev-pipeline/launch-bugfix-daemon.sh dev-pipeline/run-bugfix.sh` |
+
+### Integration Notes
+
+- **After bug-planner**: This is the natural next step. When user finishes bug planning and has `bug-fix-list.json`, suggest launching the bugfix pipeline.
+- **Session independence**: The bugfix pipeline runs completely detached. User can close cbc, open a new session later, and use this skill to check progress or stop the pipeline.
+- **Single instance**: Only one bugfix pipeline can run at a time. The PID file prevents duplicates.
+- **Feature pipeline coexistence**: Bugfix and feature pipelines use separate state directories (`bugfix-state/` vs `state/`), so they can run simultaneously without conflict.
+- **State preservation**: Stopping and restarting the bugfix pipeline resumes from where it left off -- completed bugs are not re-fixed.
+- **Bug ordering**: Bugs are processed by severity (critical → high → medium → low), then by priority number within the same severity.
+- **HANDOFF**: After pipeline completes all bugs, suggest running `prizmkit-retrospective` to capture lessons learned, or checking the fix reports in `.prizmkit/bugfix/`.