kodelyth-ecc 2.19.0 → 2.20.0

package/.agent/workflows/setup-pm.md

@@ -1,80 +0,0 @@
----
-description: Configure your preferred package manager (npm/pnpm/yarn/bun)
-disable-model-invocation: true
----
-
-# Package Manager Setup
-
-Configure your preferred package manager for this project or globally.
-
-## Usage
-
-```bash
-# Detect current package manager
-node scripts/setup-package-manager.js --detect
-
-# Set global preference
-node scripts/setup-package-manager.js --global pnpm
-
-# Set project preference
-node scripts/setup-package-manager.js --project bun
-
-# List available package managers
-node scripts/setup-package-manager.js --list
-```
-
-## Detection Priority
-
-When determining which package manager to use, the following order is checked:
-
-1. **Environment variable**: `CLAUDE_PACKAGE_MANAGER`
-2. **Project config**: `.claude/package-manager.json`
-3. **package.json**: `packageManager` field
-4. **Lock file**: Presence of package-lock.json, yarn.lock, pnpm-lock.yaml, or bun.lockb
-5. **Global config**: `~/.claude/package-manager.json`
-6. **Fallback**: First available package manager (pnpm > bun > yarn > npm)
-
-## Configuration Files
-
-### Global Configuration
-```json
-// ~/.claude/package-manager.json
-{
-  "packageManager": "pnpm"
-}
-```
-
-### Project Configuration
-```json
-// .claude/package-manager.json
-{
-  "packageManager": "bun"
-}
-```
-
-### package.json
-```json
-{
-  "packageManager": "pnpm@8.6.0"
-}
-```
-
-## Environment Variable
-
-Set `CLAUDE_PACKAGE_MANAGER` to override all other detection methods:
-
-```bash
-# Windows (PowerShell)
-$env:CLAUDE_PACKAGE_MANAGER = "pnpm"
-
-# macOS/Linux
-export CLAUDE_PACKAGE_MANAGER=pnpm
-```
-
-## Run the Detection
-
-To see current package manager detection results, run:
-
-```bash
-node scripts/setup-package-manager.js --detect
-```

package/.agent/workflows/skill-create.md

@@ -1,174 +0,0 @@
----
-name: skill-create
-description: Analyze local git history to extract coding patterns and generate SKILL.md files. Local version of the Skill Creator GitHub App.
-allowed_tools: ["Bash", "Read", "Write", "Grep", "Glob"]
----
-
-# /skill-create - Local Skill Generation
-
-Analyze your repository's git history to extract coding patterns and generate SKILL.md files that teach Claude your team's practices.
-
-## Usage
-
-```bash
-/skill-create                    # Analyze current repo
-/skill-create --commits 100      # Analyze last 100 commits
-/skill-create --output ./skills  # Custom output directory
-/skill-create --instincts        # Also generate instincts for continuous-learning-v2
-```
-
-## What It Does
-
-1. **Parses Git History** - Analyzes commits, file changes, and patterns
-2. **Detects Patterns** - Identifies recurring workflows and conventions
-3. **Generates SKILL.md** - Creates valid Claude Code skill files
-4. **Optionally Creates Instincts** - For the continuous-learning-v2 system
-
-## Analysis Steps
-
-### Step 1: Gather Git Data
-
-```bash
-# Get recent commits with file changes
-git log --oneline -n ${COMMITS:-200} --name-only --pretty=format:"%H|%s|%ad" --date=short
-
-# Get commit frequency by file
-git log --oneline -n 200 --name-only | grep -v "^$" | grep -v "^[a-f0-9]" | sort | uniq -c | sort -rn | head -20
-
-# Get commit message patterns
-git log --oneline -n 200 | cut -d' ' -f2- | head -50
-```
-
-### Step 2: Detect Patterns
-
-Look for these pattern types:
-
-| Pattern | Detection Method |
-|---------|-----------------|
-| **Commit conventions** | Regex on commit messages (feat:, fix:, chore:) |
-| **File co-changes** | Files that always change together |
-| **Workflow sequences** | Repeated file change patterns |
-| **Architecture** | Folder structure and naming conventions |
-| **Testing patterns** | Test file locations, naming, coverage |
-
-### Step 3: Generate SKILL.md
-
-Output format:
-
-```markdown
----
-name: {repo-name}-patterns
-description: Coding patterns extracted from {repo-name}
-version: 1.0.0
-source: local-git-analysis
-analyzed_commits: {count}
----
-
-# {Repo Name} Patterns
-
-## Commit Conventions
-{detected commit message patterns}
-
-## Code Architecture
-{detected folder structure and organization}
-
-## Workflows
-{detected repeating file change patterns}
-
-## Testing Patterns
-{detected test conventions}
-```
-
-### Step 4: Generate Instincts (if --instincts)
-
-For continuous-learning-v2 integration:
-
-```yaml
----
-id: {repo}-commit-convention
-trigger: "when writing a commit message"
-confidence: 0.8
-domain: git
-source: local-repo-analysis
----
-
-# Use Conventional Commits
-
-## Action
-Prefix commits with: feat:, fix:, chore:, docs:, test:, refactor:
-
-## Evidence
-- Analyzed {n} commits
-- {percentage}% follow conventional commit format
-```
-
-## Example Output
-
-Running `/skill-create` on a TypeScript project might produce:
-
-```markdown
----
-name: my-app-patterns
-description: Coding patterns from my-app repository
-version: 1.0.0
-source: local-git-analysis
-analyzed_commits: 150
----
-
-# My App Patterns
-
-## Commit Conventions
-
-This project uses **conventional commits**:
-- `feat:` - New features
-- `fix:` - Bug fixes
-- `chore:` - Maintenance tasks
-- `docs:` - Documentation updates
-
-## Code Architecture
-
-```
-src/
-├── components/     # React components (PascalCase.tsx)
-├── hooks/          # Custom hooks (use*.ts)
-├── utils/          # Utility functions
-├── types/          # TypeScript type definitions
-└── services/       # API and external services
-```
-
-## Workflows
-
-### Adding a New Component
-1. Create `src/components/ComponentName.tsx`
-2. Add tests in `src/components/__tests__/ComponentName.test.tsx`
-3. Export from `src/components/index.ts`
-
-### Database Migration
-1. Modify `src/db/schema.ts`
-2. Run `pnpm db:generate`
-3. Run `pnpm db:migrate`
-
-## Testing Patterns
-
-- Test files: `__tests__/` directories or `.test.ts` suffix
-- Coverage target: 80%+
-- Framework: Vitest
-```
-
-## GitHub App Integration
-
-For advanced features (10k+ commits, team sharing, auto-PRs), use the [Skill Creator GitHub App](https://github.com/apps/skill-creator):
-
-- Install: [github.com/apps/skill-creator](https://github.com/apps/skill-creator)
-- Comment `/skill-creator analyze` on any issue
-- Receives PR with generated skills
-
-## Related Commands
-
-- `/instinct-import` - Import generated instincts
-- `/instinct-status` - View learned instincts
-- `/evolve` - Cluster instincts into skills/agents
-
----
-
-*Part of [Kodelyth ECC](https://github.com/sifxprime/kodelyth-ecc)*

package/.agent/workflows/skill-health.md

@@ -1,54 +0,0 @@
----
-name: skill-health
-description: Show skill portfolio health dashboard with charts and analytics
-command: true
----
-
-# Skill Health Dashboard
-
-Shows a comprehensive health dashboard for all skills in the portfolio with success rate sparklines, failure pattern clustering, pending amendments, and version history.
-
-## Implementation
-
-Run the skill health CLI in dashboard mode:
-
-```bash
-ECC_ROOT="${CLAUDE_PLUGIN_ROOT:-$(node -e "var p=require('path'),f=require('fs'),h=require('os').homedir(),d=p.join(h,'.claude'),q=p.join('scripts','lib','utils.js');if(!f.existsSync(p.join(d,q))){try{var b=p.join(d,'plugins','cache','kodelyth-ecc');for(var o of f.readdirSync(b))for(var v of f.readdirSync(p.join(b,o))){var c=p.join(b,o,v);if(f.existsSync(p.join(c,q))){d=c;break}}}catch(x){}}console.log(d)")}"
-node "$ECC_ROOT/scripts/skills-health.js" --dashboard
-```
-
-For a specific panel only:
-
-```bash
-ECC_ROOT="${CLAUDE_PLUGIN_ROOT:-$(node -e "var p=require('path'),f=require('fs'),h=require('os').homedir(),d=p.join(h,'.claude'),q=p.join('scripts','lib','utils.js');if(!f.existsSync(p.join(d,q))){try{var b=p.join(d,'plugins','cache','kodelyth-ecc');for(var o of f.readdirSync(b))for(var v of f.readdirSync(p.join(b,o))){var c=p.join(b,o,v);if(f.existsSync(p.join(c,q))){d=c;break}}}catch(x){}}console.log(d)")}"
-node "$ECC_ROOT/scripts/skills-health.js" --dashboard --panel failures
-```
-
-For machine-readable output:
-
-```bash
-ECC_ROOT="${CLAUDE_PLUGIN_ROOT:-$(node -e "var p=require('path'),f=require('fs'),h=require('os').homedir(),d=p.join(h,'.claude'),q=p.join('scripts','lib','utils.js');if(!f.existsSync(p.join(d,q))){try{var b=p.join(d,'plugins','cache','kodelyth-ecc');for(var o of f.readdirSync(b))for(var v of f.readdirSync(p.join(b,o))){var c=p.join(b,o,v);if(f.existsSync(p.join(c,q))){d=c;break}}}catch(x){}}console.log(d)")}"
-node "$ECC_ROOT/scripts/skills-health.js" --dashboard --json
-```
-
-## Usage
-
-```
-/skill-health                    # Full dashboard view
-/skill-health --panel failures   # Only failure clustering panel
-/skill-health --json             # Machine-readable JSON output
-```
-
-## What to Do
-
-1. Run the skills-health.js script with --dashboard flag
-2. Display the output to the user
-3. If any skills are declining, highlight them and suggest running /evolve
-4. If there are pending amendments, suggest reviewing them
-
-## Panels
-
-- **Success Rate (30d)** — Sparkline charts showing daily success rates per skill
-- **Failure Patterns** — Clustered failure reasons with horizontal bar chart
-- **Pending Amendments** — Amendment proposals awaiting review
-- **Version History** — Timeline of version snapshots per skill

package/.agent/workflows/swarm.md

@@ -1,68 +0,0 @@
----
-description: Spawn N specialist agents in parallel inside isolated git worktrees + a tmux session. Generalized /devil-mode.
-argument-hint: "[task description] [--agents N|name1,name2,...] [--harness claude|codex|opencode|windsurf]"
----
-
-# /swarm
-
-Run a parallel team of ECC specialists on the same task in isolated git worktrees coordinated by a tmux session. The generalized form of `/devil-mode`, `/team-review`, `/security-audit`, and `/pre-release` — pick any task, pick any agents, get N panes ready to attach.
-
-## Quick examples
-
-```
-/swarm audit oauth flow for security regressions
-/swarm ship v2.0 --agents release-captain,security-reviewer,e2e-runner --execute
-/swarm refactor payments module --agents 6 --harness codex --execute
-/swarm production is down, auth service 502s --agents incident-commander,debug-detective,silent-failure-hunter --execute
-```
-
-## Behavior
-
-By default, prints the dry-run plan (safe to inspect). Add `--execute` to actually create worktrees, spawn the tmux session, and launch agents.
-
-| Flag | Effect |
-|---|---|
-| `--task "..."` | Required (or use `--plan plan.json`). |
-| `--agents N` | Smart-pick N specialists from task signals + baseline anchors + rotation. |
-| `--agents name1,name2,...` | Explicit agent list. |
-| `--harness claude\|codex\|opencode\|windsurf\|echo` | Launcher template (default `claude`). |
-| `--seed <path>` | Overlay path from main repo into each worktree (e.g. `--seed .env`). |
-| `--base-ref <ref>` | Branch base for all worktrees (default `HEAD`). |
-| `--session <name>` | Override the auto-generated tmux session name. |
-| `--replace` | Tear down any existing session/worktrees with the same names. |
-| `--execute` | Create worktrees + tmux + launch agents. |
-| `--write-only` | Just write coordination files without spawning. |
-| `--json` | Print the full plan as JSON. |
-
-## Smart agent picking
-
-If you pass `--agents N` (a number), the swarm picks specialists in this order:
-
-1. **Signal-driven** — task keywords match specialist (security → `security-reviewer`, perf → `performance-optimizer`, API → `api-guardian`, …).
-2. **Baseline anchors** — `code-reviewer` + `pair-programmer` get added (every task benefits).
-3. **Rotation fill** — 4/6/8-agent default rotations tuned for breadth.
-
-## Hard rules
-
-- Never `--execute` without inspecting the dry-run first.
-- Cap N at 8 for a single repo (worktree + pane contention past 8).
-- Always human-merge handoffs from N parallel agents — don't auto-apply.
-- Use `--session NAME` if running multiple swarms in parallel.
-
-## Coordination protocol
-
-Each worker gets three files in `<repo>/.orchestration/<session>/<worker-slug>/`:
-
-- `task.md` — agent-shaped task with required handoff sections
-- `handoff.md` — where the agent writes its output
-- `status.md` — running/completed/failed marker
-
-Inspect any worker's progress with `cat .orchestration/<session>/<slug>/status.md`.
-
-## Implementation
-
-- Skill: `swarm-orchestrator`
-- Builder: `scripts/swarm/build-plan.js`
-- Orchestrator: `scripts/lib/tmux-worktree-orchestrator.js`
-- CLI: `npx kodelyth-ecc swarm`
-- Full docs: `docs/swarm.md`

package/.agent/workflows/tdd.md

@@ -1,231 +0,0 @@
----
-description: Legacy slash-entry shim for the tdd-workflow skill. Prefer the skill directly.
----
-
-# TDD Command (Legacy Shim)
-
-Use this only if you still invoke `/tdd`. The maintained workflow lives in `skills/tdd-workflow/SKILL.md`.
-
-## Canonical Surface
-
-- Prefer the `tdd-workflow` skill directly.
-- Keep this file only as a compatibility entry point.
-
-## Arguments
-
-`$ARGUMENTS`
-
-## Delegation
-
-Apply the `tdd-workflow` skill.
-- Stay strict on RED -> GREEN -> REFACTOR.
-- Keep tests first, coverage explicit, and checkpoint evidence clear.
-- Use the skill as the maintained TDD body instead of duplicating the playbook here.
-})
-```
-
-## Step 3: Run Tests - Verify FAIL
-
-```bash
-npm test lib/liquidity.test.ts
-
-FAIL lib/liquidity.test.ts
-  ✕ should return high score for liquid market (2 ms)
-    Error: Not implemented
-
-1 test failed, 0 passed
-```
-
-PASS: Tests fail as expected. Ready to implement.
-
-## Step 4: Implement Minimal Code (GREEN)
-
-```typescript
-// lib/liquidity.ts
-export function calculateLiquidityScore(market: MarketData): number {
-  // Handle zero volume edge case
-  if (market.totalVolume === 0) {
-    return 0
-  }
-
-  // Calculate component scores (0-100 scale)
-  const volumeScore = Math.min(market.totalVolume / 1000, 100)
-  const spreadScore = Math.max(100 - (market.bidAskSpread * 1000), 0)
-  const traderScore = Math.min(market.activeTraders / 10, 100)
-
-  // Recent activity bonus
-  const hoursSinceLastTrade = (Date.now() - market.lastTradeTime.getTime()) / (1000 * 60 * 60)
-  const recencyScore = Math.max(100 - (hoursSinceLastTrade * 10), 0)
-
-  // Weighted average
-  const score = (
-    volumeScore * 0.4 +
-    spreadScore * 0.3 +
-    traderScore * 0.2 +
-    recencyScore * 0.1
-  )
-
-  return Math.min(Math.max(score, 0), 100) // Clamp to 0-100
-}
-```
-
-## Step 5: Run Tests - Verify PASS
-
-```bash
-npm test lib/liquidity.test.ts
-
-PASS lib/liquidity.test.ts
-  ✓ should return high score for liquid market (3 ms)
-  ✓ should return low score for illiquid market (2 ms)
-  ✓ should handle edge case: zero volume (1 ms)
-
-3 tests passed
-```
-
-PASS: All tests passing!
-
-## Step 6: Refactor (IMPROVE)
-
-```typescript
-// lib/liquidity.ts - Refactored with constants and better readability
-const WEIGHTS = {
-  VOLUME: 0.4,
-  SPREAD: 0.3,
-  TRADERS: 0.2,
-  RECENCY: 0.1,
-} as const
-
-const SCALE_FACTORS = {
-  VOLUME: 1000,
-  SPREAD: 1000,
-  TRADERS: 10,
-  RECENCY_PENALTY: 10,
-} as const
-
-function clamp(value: number, min: number, max: number): number {
-  return Math.min(Math.max(value, min), max)
-}
-
-export function calculateLiquidityScore(market: MarketData): number {
-  if (market.totalVolume === 0) return 0
-
-  const volumeScore = Math.min(market.totalVolume / SCALE_FACTORS.VOLUME, 100)
-  const spreadScore = clamp(100 - (market.bidAskSpread * SCALE_FACTORS.SPREAD), 0, 100)
-  const traderScore = Math.min(market.activeTraders / SCALE_FACTORS.TRADERS, 100)
-
-  const hoursSinceLastTrade = (Date.now() - market.lastTradeTime.getTime()) / (1000 * 60 * 60)
-  const recencyScore = clamp(100 - (hoursSinceLastTrade * SCALE_FACTORS.RECENCY_PENALTY), 0, 100)
-
-  const weightedScore =
-    volumeScore * WEIGHTS.VOLUME +
-    spreadScore * WEIGHTS.SPREAD +
-    traderScore * WEIGHTS.TRADERS +
-    recencyScore * WEIGHTS.RECENCY
-
-  return clamp(weightedScore, 0, 100)
-}
-```
-
-## Step 7: Verify Tests Still Pass
-
-```bash
-npm test lib/liquidity.test.ts
-
-PASS lib/liquidity.test.ts
-  ✓ should return high score for liquid market (3 ms)
-  ✓ should return low score for illiquid market (2 ms)
-  ✓ should handle edge case: zero volume (1 ms)
-
-3 tests passed
-```
-
-PASS: Refactoring complete, tests still passing!
-
-## Step 8: Check Coverage
-
-```bash
-npm test -- --coverage lib/liquidity.test.ts
-
-File           | % Stmts | % Branch | % Funcs | % Lines
----------------|---------|----------|---------|--------
-liquidity.ts   |   100   |   100    |   100   |   100
-
-Coverage: 100% PASS: (Target: 80%)
-```
-
-PASS: TDD session complete!
-```
-
-## TDD Best Practices
-
-**DO:**
-- PASS: Write the test FIRST, before any implementation
-- PASS: Run tests and verify they FAIL before implementing
-- PASS: Write minimal code to make tests pass
-- PASS: Refactor only after tests are green
-- PASS: Add edge cases and error scenarios
-- PASS: Aim for 80%+ coverage (100% for critical code)
-
-**DON'T:**
-- FAIL: Write implementation before tests
-- FAIL: Skip running tests after each change
-- FAIL: Write too much code at once
-- FAIL: Ignore failing tests
-- FAIL: Test implementation details (test behavior)
-- FAIL: Mock everything (prefer integration tests)
-
-## Test Types to Include
-
-**Unit Tests** (Function-level):
-- Happy path scenarios
-- Edge cases (empty, null, max values)
-- Error conditions
-- Boundary values
-
-**Integration Tests** (Component-level):
-- API endpoints
-- Database operations
-- External service calls
-- React components with hooks
-
-**E2E Tests** (use `/e2e` command):
-- Critical user flows
-- Multi-step processes
-- Full stack integration
-
-## Coverage Requirements
-
-- **80% minimum** for all code
-- **100% required** for:
-  - Financial calculations
-  - Authentication logic
-  - Security-critical code
-  - Core business logic
-
-## Important Notes
-
-**MANDATORY**: Tests must be written BEFORE implementation. The TDD cycle is:
-
-1. **RED** - Write failing test
-2. **GREEN** - Implement to pass
-3. **REFACTOR** - Improve code
-
-Never skip the RED phase. Never write code before tests.
-
-## Integration with Other Commands
-
-- Use `/plan` first to understand what to build
-- Use `/tdd` to implement with tests
-- Use `/build-fix` if build errors occur
-- Use `/code-review` to review implementation
-- Use `/test-coverage` to verify coverage
-
-## Related Agents
-
-This command invokes the `tdd-guide` agent provided by ECC.
-
-The related `tdd-workflow` skill is also bundled with ECC.
-
-For manual installs, the source files live at:
-- `agents/tdd-guide.md`
-- `skills/tdd-workflow/SKILL.md`