cokit-cli 1.2.7 → 1.3.0

package/templates/repo/.github/skills/test/references/report-format.md

@@ -0,0 +1,58 @@
+# Test Report Format
+
+Structured QA report template. Sacrifice grammar for concision.
+
+## Template
+
+```markdown
+# Test Report — {date} — {scope}
+
+## Test Results Overview
+- **Total**: X tests
+- **Passed**: X | **Failed**: X | **Skipped**: X
+- **Duration**: Xs
+
+## Coverage Metrics
+| Metric   | Value | Threshold | Status |
+|----------|-------|-----------|--------|
+| Lines    | X%    | 80%       | PASS/FAIL |
+| Branches | X%    | 70%       | PASS/FAIL |
+| Functions| X%    | 80%       | PASS/FAIL |
+
+## Failed Tests
+### `test/path/file.test.ts` — TestName
+- **Error**: Error message
+- **Stack**: Relevant stack trace (truncated)
+- **Cause**: Brief root cause analysis
+- **Fix**: Suggested resolution
+
+## UI Test Results (if applicable)
+- **Pages tested**: X
+- **Screenshots**: ./screenshots/
+- **Console errors**: none | [list]
+- **Responsive**: checked at [viewports] | skipped
+- **Performance**: LCP Xs, FID Xms, CLS X
+
+## Build Status
+- **Build**: PASS/FAIL
+- **Warnings**: none | [list]
+- **Dependencies**: all resolved | [issues]
+
+## Critical Issues
+1. [Blocking issue description + impact]
+
+## Recommendations
+1. [Actionable improvement with priority]
+
+## Unresolved Questions
+- [Any open questions, if any]
+```
+
+## Guidelines
+
+- Include ALL failed tests with error messages — don't summarize away details
+- Coverage: highlight specific uncovered files/functions, not just percentages
+- Screenshots: embed paths directly in report for easy access
+- Recommendations: prioritize by impact (critical > high > medium > low)
+- Keep report under 200 lines — split into sections if larger scope needed
+- Save report using naming pattern from `## Naming` section injected by hooks

package/templates/repo/.github/skills/test/references/test-execution-workflow.md

@@ -0,0 +1,103 @@
+# Test Execution Workflow
+
+## Step 1: Identify Scope
+
+Determine what to test based on recent changes:
+- New feature → full test suite + new test cases
+- Bug fix → regression tests + targeted fix validation
+- Refactor → existing test suite (no new tests unless gaps found)
+- Coverage check → full suite with coverage flags
+
+## Step 2: Pre-flight Checks
+
+Run syntax/type checks before tests to catch compile errors early:
+
+```bash
+# JavaScript/TypeScript
+npx tsc --noEmit          # TypeScript check
+npx eslint .              # Lint check
+
+# Python
+python -m py_compile file.py
+flake8 .
+
+# Flutter
+flutter analyze
+
+# Go
+go vet ./...
+
+# Rust
+cargo check
+```
+
+## Step 3: Execute Tests
+
+### JavaScript/TypeScript
+```bash
+npm test                    # or yarn test / pnpm test / bun test
+npm run test:coverage       # with coverage
+npx vitest run              # Vitest
+npx jest --coverage         # Jest with coverage
+```
+
+### Python
+```bash
+pytest                      # basic
+pytest --cov=src --cov-report=term-missing  # with coverage
+python -m unittest discover # unittest
+```
+
+### Go / Rust / Flutter
+```bash
+go test ./... -cover        # Go with coverage
+cargo test                  # Rust
+flutter test --coverage     # Flutter
+```
+
+## Step 4: Analyze Results
+
+Focus on:
+1. **Failing tests** — read error messages and stack traces carefully
+2. **Flaky tests** — tests that pass/fail intermittently indicate race conditions or state leaks
+3. **Slow tests** — identify bottlenecks (>5s per test is suspicious)
+4. **Skipped tests** — ensure skips are intentional, not hiding failures
+
+## Step 5: Coverage Analysis
+
+Thresholds:
+- **80%+** line coverage — standard minimum
+- **70%+** branch coverage — acceptable for most projects
+- Focus on critical paths: auth, payment, data mutations
+
+Identify gaps:
+- Uncovered error handlers
+- Missing edge case branches
+- Untested utility functions
+
+## Step 6: Build Verification
+
+```bash
+npm run build               # JS/TS production build
+python setup.py build       # Python
+go build ./...              # Go
+cargo build --release       # Rust
+flutter build               # Flutter
+```
+
+Check for:
+- Build warnings or deprecation notices
+- Unresolved dependencies
+- Production config correctness
+
+## Quality Checklist
+
+- [ ] All tests pass (zero failures)
+- [ ] Coverage meets project threshold
+- [ ] No flaky tests detected
+- [ ] Build completes without errors
+- [ ] Error scenarios tested
+- [ ] Test isolation verified (no shared state)
+- [ ] Test data cleaned up after execution
+- [ ] Mocks/stubs properly configured
+- [ ] Environment variables correctly set

package/templates/repo/.github/skills/test/references/ui-testing-workflow.md

@@ -0,0 +1,65 @@
+# UI Testing Workflow
+
+Activate the ck:chrome-devtools (if available) skill.
+
+## Purpose
+Run comprehensive UI tests on a website and generate a detailed report.
+
+## Arguments
+- $1: URL - The URL of the website to test
+- $2: OPTIONS - Optional test configuration (e.g., --headless, --mobile, --auth)
+
+## Testing Protected Routes (Authentication)
+
+### Step 1: User Manual Login
+Instruct the user to:
+1. Open the target site in their browser
+2. Log in manually with their credentials
+3. Open browser DevTools (F12) → Application tab → Cookies/Storage
+
+### Step 2: Extract Auth Credentials
+Ask the user to provide one of:
+- **Cookies**: Copy cookie values (name, value, domain)
+- **Access Token**: Copy JWT/Bearer token from localStorage or cookies
+- **Session Storage**: Copy relevant session keys
+
+### Step 3: Inject Authentication
+Use the `inject-auth.js` script:
+
+```bash
+cd $SKILL_DIR  # chrome-devtools scripts (if available)
+
+# Option A: Inject cookies
+node inject-auth.js --url https://example.com --cookies '[{"name":"session","value":"abc123","domain":".example.com"}]'
+
+# Option B: Inject Bearer token
+node inject-auth.js --url https://example.com --token "Bearer eyJhbGciOi..." --header Authorization --token-key access_token
+
+# Option C: Inject localStorage
+node inject-auth.js --url https://example.com --local-storage '{"auth_token":"xyz","user_id":"123"}'
+```
+
+### Step 4: Run Tests
+After auth injection, run tests normally:
+```bash
+node navigate.js --url https://example.com/dashboard
+node screenshot.js --url https://example.com/profile --output profile.png
+```
+
+## Workflow
+- Use `plan` skill to organize the test plan & report
+- All screenshots saved in the same report directory
+- Browse URL, discover all pages, components, endpoints
+- Create test plan based on discovered structure
+- Use multiple `tester` subagents in parallel for: pages, forms, navigation, user flows, accessibility, responsive layouts, performance, security, seo
+- Use `ai-multimodal` (if available) to analyze all screenshots
+- Generate comprehensive Markdown report
+- Ask user if they want to preview with `/ck-preview`
+
+## Output Requirements
+- Clear, structured Markdown with headers, lists, code blocks
+- Include test results summary, key findings, screenshot references
+- Ensure token efficiency while maintaining high quality
+- Sacrifice grammar for concision
+
+**Do not** start implementing fixes.

package/templates/repo/.github/skills/ui-styling/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: ui-styling
 description: Style UIs with shadcn/ui components (Radix UI + Tailwind CSS). Use for accessible components, themes, dark mode, responsive layouts, design systems, color customization.
+license: MIT
+argument-hint: "[component or layout]"
 ---
 
 # UI Styling Skill

package/templates/repo/.github/skills/web-testing/SKILL.md

@@ -1,52 +1,25 @@
 ---
 name: web-testing
-description: Web testing with Playwright, Vitest, k6. E2E/unit/integration/load/security/visual/a11y testing. Multi-language support (JS/TS, Python, Go, Rust, Flutter). Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser.
+description: Web testing with Playwright, Vitest, k6. E2E/unit/integration/load/security/visual/a11y testing. Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser.
+license: Apache-2.0
+argument-hint: "[test-type] [target]"
 ---
 
 # Web Testing Skill
 
-Comprehensive testing: unit, integration, E2E, load, security, visual regression, accessibility. Multi-language workflow orchestration with structured QA reporting.
-
-## Core Principle
-
-**NEVER IGNORE FAILING TESTS.** Fix root causes, not symptoms. No mocks/cheats/tricks to pass builds.
+Comprehensive web testing: unit, integration, E2E, load, security, visual regression, accessibility.
 
 ## Quick Start
 
 ```bash
-# JavaScript/TypeScript
 npx vitest run                    # Unit tests
 npx playwright test               # E2E tests
-npm run test:coverage             # Coverage
-
-# Python
-pytest --cov=src                  # Unit + coverage
-
-# Go / Rust / Flutter
-go test ./... -cover              # Go
-cargo test                        # Rust
-flutter test --coverage           # Flutter
-
-# Web Quality
+npx playwright test --ui          # E2E with UI
 k6 run load-test.js               # Load tests
-npx @axe-core/cli https://...    # Accessibility
-npx lighthouse https://...       # Performance
+npx @axe-core/cli https://example.com  # Accessibility
+npx lighthouse https://example.com     # Performance
 ```
 
-## Workflows
-
-Three orchestrated workflows — load the relevant reference when needed:
-
-| Workflow | Reference | Use When |
-|----------|-----------|----------|
-| Code Testing | `./references/test-execution-workflow.md` | Running unit/integration/e2e, checking coverage, validating builds |
-| UI Testing | `./references/ui-testing-workflow.md` | Visual regression, responsive checks, accessibility audits, form automation |
-| Report Format | `./references/report-format.md` | Generating structured QA summary reports |
-
-**Code Testing Process:** Identify scope → Pre-flight checks → Execute tests → Analyze results → Coverage analysis → Build verification → Report
-
-**UI Testing Process:** Discovery → Visual capture → Console errors → Network validation → Responsive testing → Form testing → Performance metrics → Report
-
 ## Testing Strategy (Choose Your Model)
 
 | Model | Structure | Best For |
@@ -55,15 +28,10 @@ Three orchestrated workflows — load the relevant reference when needed:
 | Trophy | Integration-heavy | Modern SPAs |
 | Honeycomb | Contract-centric | Microservices |
 
-> `./references/testing-pyramid-strategy.md`
+→ `./references/testing-pyramid-strategy.md`
 
 ## Reference Documentation
 
-### Workflows & Reports
-- `./references/test-execution-workflow.md` - Orchestrated code testing (multi-language)
-- `./references/ui-testing-workflow.md` - Browser-based visual testing via `agent-browser`
-- `./references/report-format.md` - Structured QA report template
-
 ### Core Testing
 - `./references/unit-integration-testing.md` - Vitest, browser mode, AAA
 - `./references/e2e-testing-playwright.md` - Fixtures, sharding, selectors
@@ -98,17 +66,6 @@ Three orchestrated workflows — load the relevant reference when needed:
 - `./references/pre-release-checklist.md` - Complete release checklist
 - `./references/functional-testing-checklist.md` - Feature testing
 
-## Tools Integration
-
-- **Test runners**: Vitest, Jest, Mocha, pytest, go test, cargo test, flutter test
-- **Coverage**: Istanbul/c8/nyc, pytest-cov, go cover
-- **E2E**: Playwright (multi-browser, sharding)
-- **Load**: k6
-- **Browser**: `agent-browser` skill for UI testing
-- **Analysis**: `ai-multimodal` skill (if available) for screenshot analysis
-- **Debugging**: `debug` skill when tests reveal bugs
-- **Thinking**: `sequential-thinking` skill for complex test failure analysis
-
 ## Scripts
 
 ### Initialize Playwright Project
@@ -137,12 +94,3 @@ jobs:
       - run: npm run test:a11y      # Accessibility
       - run: npx lhci autorun       # Performance
 ```
-
-## Quality Standards
-
-- All critical paths must have test coverage
-- Validate happy path AND error scenarios
-- Ensure test isolation — no interdependencies
-- Tests must be deterministic and reproducible
-- Clean up test data after execution
-- Coverage: 80%+ lines, 70%+ branches minimum

package/docs/guide-next-steps-speckit-cokit-implementation.md

@@ -1,187 +0,0 @@
-# Next Steps Guide: Spec-Kit + Cokit Implementation
-
-**Created:** Feb 3, 2026
-**Status:** COMPLETE (v1.2.6 released with SpecKit integration)
-
----
-
-## Phase 1: Setup Spec-Kit (Week 1)
-
-### Step 1.1: Install GitHub Spec-Kit (Reference)
-```bash
-# Install spec-kit CLI for reference
-uv tool install specify-cli --from git+https://github.com/github/spec-kit.git
-
-# Test it works
-specify --help
-```
-
-### Step 1.2: Study Spec-Kit Structure
-```bash
-# Clone for reference (don't modify)
-git clone https://github.com/github/spec-kit.git ~/reference/spec-kit
-
-# Key files to study:
-# - templates/claude/commands/*.md
-# - src/specify_cli/
-# - docs/
-```
-
-### Step 1.3: Create my-spec-kit Scaffold
-```bash
-cd /Users/admin/workspace/_me/cokit
-mkdir -p src/spec-kit/{cli,templates,validators}
-
-# Create initial files
-touch src/spec-kit/cli/init.js
-touch src/spec-kit/cli/constitution.js
-touch src/spec-kit/cli/specify.js
-touch src/spec-kit/templates/constitution.md
-touch src/spec-kit/templates/spec-feature.md
-touch src/spec-kit/templates/spec-api.md
-```
-
-### Step 1.4: Define Custom Templates
-
-**constitution.md** - Project governance:
-- Tech stack decisions
-- Code standards
-- Security requirements
-- Team conventions
-
-**spec-feature.md** - Feature specs:
-- User stories
-- Acceptance criteria
-- Technical constraints
-- Dependencies
-
----
-
-## Phase 2: Port ClaudeKit → Cokit (Week 2-3)
-
-### Step 2.1: Research Copilot CLI
-```bash
-# Check Copilot CLI docs
-# https://docs.github.com/en/copilot/using-github-copilot/using-github-copilot-in-the-command-line
-
-# Install GitHub CLI with Copilot extension
-gh extension install github/gh-copilot
-```
-
-### Step 2.2: Map Commands
-| ClaudeKit | Cokit (Copilot) | Notes |
-|-----------|-----------------|-------|
-| `/brainstorm` | `cokit brainstorm` | Adapt prompts |
-| `/plan` | `cokit plan` | Different context model |
-| `/cook` | `cokit cook` | Simplify for Copilot |
-| `/fix` | `cokit fix` | Direct port |
-| `/worktree` | `cokit worktree` | Git-only, no AI needed |
-
-### Step 2.3: Create Cokit CLI
-```bash
-# Scaffold already exists in /src
-# Enhance with new commands:
-
-# src/commands/
-#   brainstorm.js
-#   plan.js
-#   cook.js
-#   fix.js
-#   worktree.js
-```
-
----
-
-## Phase 3: Integrate Spec-Kit + Cokit (Week 3-4)
-
-### Step 3.1: Create Combo Workflows
-```
-cokit workflow enterprise  → speckit.constitution → speckit.specify → brainstorm → plan → cook
-cokit workflow quick       → brainstorm → plan:fast → cook
-cokit workflow fix         → fix --auto
-```
-
-### Step 3.2: Add to Instructions
-```bash
-# Update /instructions/ with combo workflows
-touch instructions/workflow-enterprise.md
-touch instructions/workflow-quick-md
-touch instructions/workflow-fix.md
-```
-
----
-
-## Phase 4: Team Training (Week 4)
-
-### Step 4.1: Create Training Materials
-- [ ] Quick start guide (5 min read)
-- [ ] Video demo (10 min)
-- [ ] Cheat sheet (1 page)
-- [ ] FAQ document
-
-### Step 4.2: Pilot Program
-- [ ] Select 2-3 volunteer devs
-- [ ] Run 1-week pilot
-- [ ] Collect feedback
-- [ ] Iterate
-
-### Step 4.3: Full Rollout
-- [ ] Team presentation
-- [ ] Pair programming sessions
-- [ ] Office hours for questions
-
----
-
-## Quick Reference: Commands After Setup
-
-```bash
-# Enterprise feature (with specs)
-cokit workflow enterprise "new payment system"
-
-# Quick feature (no specs)
-cokit workflow quick "add dark mode"
-
-# Bug fix
-cokit fix "error: undefined is not a function"
-
-# Parallel development
-cokit worktree "feature-x"
-```
-
----
-
-## Checklist
-
-### Week 1
-- [ ] Install spec-kit CLI (reference)
-- [ ] Clone spec-kit repo (study)
-- [ ] Create my-spec-kit scaffold
-- [ ] Write constitution template
-- [ ] Write spec-feature template
-
-### Week 2
-- [ ] Research Copilot CLI API
-- [ ] Map ClaudeKit → Cokit commands
-- [ ] Port `/brainstorm` command
-- [ ] Port `/plan` command
-
-### Week 3
-- [ ] Port `/cook` command
-- [ ] Port `/fix` command
-- [ ] Port `/worktree` command
-- [ ] Create combo workflows
-
-### Week 4
-- [ ] Write training materials
-- [ ] Run pilot program
-- [ ] Collect feedback
-- [ ] Full team rollout
-
----
-
-## Resources
-
-- [GitHub Spec-Kit](https://github.com/github/spec-kit)
-- [ClaudeKit Reference](https://github.com/duthaho/claudekit)
-- [Copilot CLI Docs](https://docs.github.com/en/copilot)
-- Research reports: `pocketquant/plans/reports/brainstorm-260203-*`