cokit-cli 1.2.4 → 1.2.6

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

@@ -0,0 +1,118 @@
+# Test Execution Workflow
+
+Orchestrated workflow for running code-level tests across any language/framework.
+
+## Step 1: Identify Scope
+
+Determine what to test based on recent changes:
+
+| Change Type | Test Strategy |
+|-------------|---------------|
+| 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
+npx eslint .
+
+# 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                      # project default
+npx vitest run                # Vitest
+npx jest --coverage           # Jest with coverage
+bun test                      # Bun
+```
+
+### Python
+```bash
+pytest                                          # basic
+pytest --cov=src --cov-report=term-missing      # with coverage
+python -m unittest discover                     # unittest
+```
+
+### Go
+```bash
+go test ./... -cover          # with coverage
+go test ./... -race           # race condition detection
+```
+
+### Rust
+```bash
+cargo test
+cargo test -- --nocapture     # show stdout
+```
+
+### Flutter
+```bash
+flutter test --coverage
+```
+
+## Step 4: Analyze Results
+
+Focus on:
+1. **Failing tests** — read error messages and stack traces carefully
+2. **Flaky tests** — pass/fail intermittently → race conditions or state leaks
+3. **Slow tests** — >5s per test is suspicious, identify bottlenecks
+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/web-testing/references/ui-testing-workflow.md

@@ -0,0 +1,97 @@
+# UI Testing Workflow
+
+Browser-based visual testing using `agent-browser` skill. Covers screenshots, responsive checks, accessibility, form automation, console errors.
+
+## Prerequisites
+
+Ensure `agent-browser` skill is available. For screenshot analysis, use `ai-multimodal` skill (if available).
+
+## Step 1: Discovery
+
+Browse target URL, discover pages, components, endpoints:
+
+```bash
+# Navigate and capture initial state
+# Use agent-browser skill to browse http://localhost:3000
+# Capture ARIA snapshot for accessibility baseline
+```
+
+## Step 2: Visual Capture
+
+```bash
+# Full page screenshot
+# Screenshot http://localhost:3000 → ./screenshots/home.png (full-page)
+
+# Specific component
+# Screenshot selector ".main-content" → ./screenshots/main.png
+```
+
+## Step 3: Console Error Check
+
+Capture JavaScript errors for 5 seconds on each page.
+
+- Zero errors = pass
+- Any errors = investigate before proceeding
+- Check for: uncaught exceptions, failed promises, deprecation warnings
+
+## Step 4: Network Validation
+
+Check for failed API calls:
+- Filter responses with status >= 400
+- Identify CORS issues, missing endpoints, auth failures
+- Validate API response times
+
+## Step 5: Responsive Testing
+
+Capture at key breakpoints:
+
+| Viewport | Size | Device |
+|----------|------|--------|
+| Desktop | 1920x1080 | Standard monitor |
+| Tablet | 768x1024 | iPad |
+| Mobile | 375x812 | iPhone |
+
+For each viewport:
+1. Resize browser window
+2. Capture full-page screenshot
+3. Check for layout breakage, overflow, hidden elements
+
+## Step 6: Form & Interaction Testing
+
+Test interactive elements:
+1. Fill form fields with valid data
+2. Submit and verify success state
+3. Fill with invalid data and verify error messages
+4. Test keyboard navigation (Tab, Enter, Escape)
+5. Capture screenshots of each state
+
+## Step 7: Performance Metrics
+
+Collect Core Web Vitals:
+- **LCP** (Largest Contentful Paint): < 2.5s
+- **FID/INP** (First Input Delay / Interaction to Next Paint): < 200ms
+- **CLS** (Cumulative Layout Shift): < 0.1
+
+## Authentication for Protected Routes
+
+For pages behind auth:
+
+| Method | Use Case |
+|--------|----------|
+| Cookie injection | Session-based auth |
+| Bearer token | API/JWT auth |
+| localStorage | SPA token storage |
+
+After injection, browser session persists for subsequent tests.
+
+## Screenshot Analysis
+
+Use `ai-multimodal` skill (if available) to analyze captured screenshots for:
+- Layout correctness
+- Visual regressions vs baseline
+- Missing elements or broken styling
+- Accessibility issues (contrast, text size)
+
+## Cleanup
+
+Close browser sessions when testing completes to free resources.

package/prompts/ck-journal.prompt.md

@@ -1,19 +0,0 @@
----
-agent: 'agent'
-description: 'Write journal entries from recent changes and memories'
----
-
-Use the `journal-writer` agent to explore the memories and recent code changes, and write some journal entries.
-Journal entries should be concise and focused on the most important events, key changes, impacts, and decisions.
-Keep journal entries in the `./docs/journals/` directory.
-
----
-
-## Suggested Next Steps
-
-| Command | Description |
-|---------|-------------|
-| `/ck-brainstorm` | Explore ideas |
-| `/ck-plan` | Create plan |
-| `/ck-fix` | Analyze and fix issues |
-| `/ck-spec-specify` | Write detailed feature spec |

package/prompts/ck-preview.prompt.md

@@ -1,77 +0,0 @@
----
-agent: 'agent'
-description: 'Preview markdown files, plan directories, or plans collection'
-argument-hint: 'Path to markdown file or directory'
-tools: ['execute/runInTerminal', 'execute/getTerminalOutput']
----
-
-Universal viewer - pass ANY path and see it rendered nicely.
-
-## Usage
-
-- `/ck-preview <file.md>` - View markdown file in novel-reader UI
-- `/ck-preview <directory/>` - Browse directory contents
-- `/ck-preview --stop` - Stop running server
-
-## Examples
-
-```bash
-/ck-preview plans/my-plan/ck-plan.md     # View markdown file
-/ck-preview plans/                    # Browse plans directory
-/ck-preview docs/                     # Browse docs directory
-/ck-preview any/path/to/file.md      # View any markdown file
-/ck-preview any/path/                 # Browse any directory
-```
-
-## Execution
-
-Run the server using `#tool:execute/runInTerminal`. The skill is located at `$HOME/.copilot/skills/markdown-novel-viewer/`.
-
-### Stop Server
-
-If `--stop` flag is provided:
-
-```bash
-node $HOME/.copilot/skills/markdown-novel-viewer/scripts/server.cjs --stop
-```
-
-### Start Server
-
-Otherwise, run the `markdown-novel-viewer` server with `--foreground` flag:
-
-```bash
-# Determine if path is file or directory
-INPUT_PATH="${input}"
-if [[ -d "$INPUT_PATH" ]]; then
-  # Directory mode - browse
-  node $HOME/.copilot/skills/markdown-novel-viewer/scripts/server.cjs \
-    --dir "$INPUT_PATH" \
-    --host 0.0.0.0 \
-    --open \
-    --foreground
-else
-  # File mode - view markdown
-  node $HOME/.copilot/skills/markdown-novel-viewer/scripts/server.cjs \
-    --file "$INPUT_PATH" \
-    --host 0.0.0.0 \
-    --open \
-    --foreground
-fi
-```
-
-After starting, parse the JSON output (e.g., `{"success":true,"url":"http://localhost:3456/view?file=...","networkUrl":"http://192.168.1.x:3456/view?file=..."}`) and report:
-- Local URL for browser access
-- Network URL for remote device access (if available)
-- Inform user that server is now running in the terminal; stop it by running the stop command
-
-**CRITICAL:** MUST display the FULL URL including path and query string (e.g., `http://localhost:3456/view?file=/path/to/file.md`). NEVER truncate to just `host:port` (e.g., `http://localhost:3456`). The full URL is required for direct file access.
-
----
-
-## Suggested Next Steps
-
-| Command | Description |
-|---------|-------------|
-| `/ck-brainstorm` | Explore ideas |
-| `/ck-plan` | Create plan |
-| `/ck-spec-specify` | Write detailed feature spec |

package/templates/repo/.github/prompts/ck-journal.prompt.md

@@ -1,19 +0,0 @@
----
-agent: 'agent'
-description: 'Write journal entries from recent changes and memories'
----
-
-Use the `journal-writer` agent to explore the memories and recent code changes, and write some journal entries.
-Journal entries should be concise and focused on the most important events, key changes, impacts, and decisions.
-Keep journal entries in the `./docs/journals/` directory.
-
----
-
-## Suggested Next Steps
-
-| Command | Description |
-|---------|-------------|
-| `/ck-brainstorm` | Explore ideas |
-| `/ck-plan` | Create plan |
-| `/ck-fix` | Analyze and fix issues |
-| `/ck-spec-specify` | Write detailed feature spec |

package/templates/repo/.github/prompts/ck-preview.prompt.md

@@ -1,77 +0,0 @@
----
-agent: 'agent'
-description: 'Preview markdown files, plan directories, or plans collection'
-argument-hint: 'Path to markdown file or directory'
-tools: ['execute/runInTerminal', 'execute/getTerminalOutput']
----
-
-Universal viewer - pass ANY path and see it rendered nicely.
-
-## Usage
-
-- `/ck-preview <file.md>` - View markdown file in novel-reader UI
-- `/ck-preview <directory/>` - Browse directory contents
-- `/ck-preview --stop` - Stop running server
-
-## Examples
-
-```bash
-/ck-preview plans/my-plan/ck-plan.md     # View markdown file
-/ck-preview plans/                    # Browse plans directory
-/ck-preview docs/                     # Browse docs directory
-/ck-preview any/path/to/file.md      # View any markdown file
-/ck-preview any/path/                 # Browse any directory
-```
-
-## Execution
-
-Run the server using `#tool:execute/runInTerminal`. The skill is located at `$HOME/.copilot/skills/markdown-novel-viewer/`.
-
-### Stop Server
-
-If `--stop` flag is provided:
-
-```bash
-node $HOME/.copilot/skills/markdown-novel-viewer/scripts/server.cjs --stop
-```
-
-### Start Server
-
-Otherwise, run the `markdown-novel-viewer` server with `--foreground` flag:
-
-```bash
-# Determine if path is file or directory
-INPUT_PATH="${input}"
-if [[ -d "$INPUT_PATH" ]]; then
-  # Directory mode - browse
-  node $HOME/.copilot/skills/markdown-novel-viewer/scripts/server.cjs \
-    --dir "$INPUT_PATH" \
-    --host 0.0.0.0 \
-    --open \
-    --foreground
-else
-  # File mode - view markdown
-  node $HOME/.copilot/skills/markdown-novel-viewer/scripts/server.cjs \
-    --file "$INPUT_PATH" \
-    --host 0.0.0.0 \
-    --open \
-    --foreground
-fi
-```
-
-After starting, parse the JSON output (e.g., `{"success":true,"url":"http://localhost:3456/view?file=...","networkUrl":"http://192.168.1.x:3456/view?file=..."}`) and report:
-- Local URL for browser access
-- Network URL for remote device access (if available)
-- Inform user that server is now running in the terminal; stop it by running the stop command
-
-**CRITICAL:** MUST display the FULL URL including path and query string (e.g., `http://localhost:3456/view?file=/path/to/file.md`). NEVER truncate to just `host:port` (e.g., `http://localhost:3456`). The full URL is required for direct file access.
-
----
-
-## Suggested Next Steps
-
-| Command | Description |
-|---------|-------------|
-| `/ck-brainstorm` | Explore ideas |
-| `/ck-plan` | Create plan |
-| `/ck-spec-specify` | Write detailed feature spec |