cokit-cli 1.0.9 → 1.2.2

package/skills/ck-sequential-thinking/tests/process-thought.test.js

@@ -1,215 +0,0 @@
-/**
- * Tests for Sequential Thinking Thought Processor
- *
- * Run with: npm test
- */
-
-const { ThoughtProcessor } = require('../scripts/process-thought');
-const fs = require('fs');
-const path = require('path');
-
-// Mock history file for testing
-const TEST_HISTORY_FILE = path.join(__dirname, '../scripts/.thought-history.json');
-
-describe('ThoughtProcessor', () => {
-  let processor;
-
-  beforeEach(() => {
-    // Clean up any existing history file
-    if (fs.existsSync(TEST_HISTORY_FILE)) {
-      fs.unlinkSync(TEST_HISTORY_FILE);
-    }
-    processor = new ThoughtProcessor();
-  });
-
-  afterEach(() => {
-    // Clean up after tests
-    if (fs.existsSync(TEST_HISTORY_FILE)) {
-      fs.unlinkSync(TEST_HISTORY_FILE);
-    }
-  });
-
-  describe('Validation', () => {
-    test('rejects missing thought', () => {
-      const result = processor.processThought({
-        thoughtNumber: 1,
-        totalThoughts: 5,
-        nextThoughtNeeded: true
-      });
-
-      expect(result.success).toBe(false);
-      expect(result.errors).toContain('Invalid thought: must be a non-empty string');
-    });
-
-    test('rejects empty thought string', () => {
-      const result = processor.processThought({
-        thought: '   ',
-        thoughtNumber: 1,
-        totalThoughts: 5,
-        nextThoughtNeeded: true
-      });
-
-      expect(result.success).toBe(false);
-      expect(result.errors).toContain('Invalid thought: must be a non-empty string');
-    });
-
-    test('rejects invalid thoughtNumber', () => {
-      const result = processor.processThought({
-        thought: 'Test',
-        thoughtNumber: 0,
-        totalThoughts: 5,
-        nextThoughtNeeded: true
-      });
-
-      expect(result.success).toBe(false);
-      expect(result.errors).toContain('Invalid thoughtNumber: must be a positive number');
-    });
-
-    test('rejects missing nextThoughtNeeded', () => {
-      const result = processor.processThought({
-        thought: 'Test',
-        thoughtNumber: 1,
-        totalThoughts: 5
-      });
-
-      expect(result.success).toBe(false);
-      expect(result.errors).toContain('Invalid nextThoughtNeeded: must be a boolean');
-    });
-
-    test('accepts valid thought', () => {
-      const result = processor.processThought({
-        thought: 'Valid thought',
-        thoughtNumber: 1,
-        totalThoughts: 5,
-        nextThoughtNeeded: true
-      });
-
-      expect(result.success).toBe(true);
-      expect(result.thoughtNumber).toBe(1);
-      expect(result.totalThoughts).toBe(5);
-    });
-  });
-
-  describe('Thought Processing', () => {
-    test('tracks thought history', () => {
-      processor.processThought({
-        thought: 'First thought',
-        thoughtNumber: 1,
-        totalThoughts: 3,
-        nextThoughtNeeded: true
-      });
-
-      processor.processThought({
-        thought: 'Second thought',
-        thoughtNumber: 2,
-        totalThoughts: 3,
-        nextThoughtNeeded: true
-      });
-
-      const result = processor.processThought({
-        thought: 'Third thought',
-        thoughtNumber: 3,
-        totalThoughts: 3,
-        nextThoughtNeeded: false
-      });
-
-      expect(result.thoughtHistoryLength).toBe(3);
-    });
-
-    test('auto-adjusts totalThoughts when exceeded', () => {
-      const result = processor.processThought({
-        thought: 'Thought 5',
-        thoughtNumber: 5,
-        totalThoughts: 3,
-        nextThoughtNeeded: true
-      });
-
-      expect(result.totalThoughts).toBe(5);
-    });
-
-    test('tracks revisions', () => {
-      processor.processThought({
-        thought: 'Original thought',
-        thoughtNumber: 1,
-        totalThoughts: 5,
-        nextThoughtNeeded: true
-      });
-
-      const result = processor.processThought({
-        thought: 'Revised thought',
-        thoughtNumber: 2,
-        totalThoughts: 5,
-        nextThoughtNeeded: true,
-        isRevision: true,
-        revisesThought: 1
-      });
-
-      expect(result.success).toBe(true);
-      expect(result.thoughtHistoryLength).toBe(2);
-    });
-
-    test('tracks branches', () => {
-      processor.processThought({
-        thought: 'Main thought',
-        thoughtNumber: 1,
-        totalThoughts: 5,
-        nextThoughtNeeded: true
-      });
-
-      processor.processThought({
-        thought: 'Branch A',
-        thoughtNumber: 2,
-        totalThoughts: 5,
-        nextThoughtNeeded: true,
-        branchFromThought: 1,
-        branchId: 'branch-a'
-      });
-
-      const result = processor.processThought({
-        thought: 'Branch B',
-        thoughtNumber: 2,
-        totalThoughts: 5,
-        nextThoughtNeeded: false,
-        branchFromThought: 1,
-        branchId: 'branch-b'
-      });
-
-      expect(result.branches).toContain('branch-a');
-      expect(result.branches).toContain('branch-b');
-      expect(result.branches.length).toBe(2);
-    });
-  });
-
-  describe('History Management', () => {
-    test('resets history', () => {
-      processor.processThought({
-        thought: 'First thought',
-        thoughtNumber: 1,
-        totalThoughts: 5,
-        nextThoughtNeeded: true
-      });
-
-      processor.resetHistory();
-
-      const history = processor.getHistory();
-      expect(history.totalThoughts).toBe(0);
-      expect(history.thoughts.length).toBe(0);
-    });
-
-    test('persists and loads history', () => {
-      processor.processThought({
-        thought: 'Persisted thought',
-        thoughtNumber: 1,
-        totalThoughts: 5,
-        nextThoughtNeeded: true
-      });
-
-      // Create new processor instance (should load from file)
-      const newProcessor = new ThoughtProcessor();
-      const history = newProcessor.getHistory();
-
-      expect(history.totalThoughts).toBe(1);
-      expect(history.thoughts[0].thought).toBe('Persisted thought');
-    });
-  });
-});

package/templates/repo/.github/.cokit-version

@@ -1,4 +0,0 @@
-1.0.0
-# CoKit installation marker - do not delete
-# https://github.com/camping89/cokit
-# Run 'npx cokit update' to check for updates

package/templates/repo/.github/copilot-instructions.md

@@ -1,45 +0,0 @@
-# Project Instructions
-
-This file provides guidance to GitHub Copilot when working with code in this repository.
-
-## Role
-
-You are an expert software engineer following these principles:
-- **YAGNI** - Don't add features until needed
-- **KISS** - Prefer simple solutions over complex ones
-- **DRY** - Extract repeated code into reusable functions
-
-## Coding Standards
-
-- Keep files under 200 lines when practical
-- Use kebab-case for file names (e.g., `user-service.ts`)
-- Use camelCase for variables and functions
-- Use PascalCase for classes and components
-- No hardcoded secrets or credentials
-- No TODO/FIXME comments without tracking issues
-
-## Quality Requirements
-
-- Write tests for new features before claiming complete
-- Review code for security vulnerabilities (XSS, injection, etc.)
-- Handle errors explicitly - no silent failures
-- Validate all external inputs
-- Log at appropriate levels (error, warn, info, debug)
-
-## Before Implementation
-
-1. Read existing code to understand patterns
-2. Check for similar implementations to reuse
-3. Understand the full scope before starting
-
-## After Implementation
-
-1. Verify no syntax errors (compile/lint)
-2. Run existing tests to catch regressions
-3. Test the new functionality manually
-4. Review for security implications
-
-## Project Context
-
-<!-- Add project-specific context below -->
-<!-- Example: Tech stack, architecture decisions, team conventions -->

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

@@ -1,178 +0,0 @@
----
-agent: 'agent'
-description: 'Start coding & testing an existing plan'
-tools: ['search/codebase', 'search/changes', 'web/fetch', 'web/githubRepo', 'read/terminalLastCommand']
----
-
-**THINK HARDER** to start working on the following plan follow the Orchestration Protocol, Core Responsibilities, and Development Rules:
-<plan>${input}</plan>
-
----
-
-## Role Responsibilities
-- You are a senior software engineer who must study the provided implementation plan end-to-end before writing code.
-- Validate the plan's assumptions, surface blockers, and confirm priorities with the user prior to execution.
-- Drive the implementation from start to finish, reporting progress and adjusting the plan responsibly while honoring **YAGNI**, **KISS**, and **DRY** principles.
-
-**IMPORTANT:** Remind these rules with  communication:
-- Sacrifice grammar for the sake of concision when writing reports.
-- In reports, list any unresolved questions at the end, if any.
-- Ensure token efficiency while maintaining high quality.
-
----
-
-## Step 0: Plan Detection & Phase Selection
-
-**If `{input}` is empty:**
-1. Find latest `plan.md` in `.s` | `find .s -name "plan.md" -type f -exec stat -f "%m %N" {} \; 2>/dev/null | sort -rn | head -1 | cut -d' ' -f2-`
-2. Parse plan for phases and status, auto-select next incomplete (prefer IN_PROGRESS or earliest Planned)
-
-**If `{input}` provided:** Use that plan and detect which phase to work on (auto-detect or use argument like "phase-2").
-
-**Output:** `✓ Step 0: [Plan Name] - [Phase Name]`
-
-** Pattern (use throughout):**
-```
-Task(_type="[type]", prompt="[task description]", description="[brief]")
-```
-
----
-
-## Workflow Sequence
-
-**Rules:** Follow steps 1-6 in order. Each step requires output marker starting with "✓ Step N:". Mark each complete in TodoWrite before proceeding. Do not skip steps.
-
----
-
-## Step 1: Analysis & Task Extraction
-
-Read plan file completely. Map dependencies between tasks. List ambiguities or blockers. Identify required skills/tools and activate from catalog. Parse phase file and extract actionable tasks.
-
-**TodoWrite Initialization & Task Extraction:**
-- Initialize TodoWrite with `Step 0: [Plan Name] - [Phase Name]` and all command steps (Step 1 through Step 6)
-- Read phase file (e.g., phase-01-preparation.md)
-- Look for tasks/steps/phases/sections/numbered/bulleted lists
-- MUST convert to TodoWrite tasks:
-  - Phase Implementation tasks → Step 2.X (Step 2.1, Step 2.2, etc.)
-  - Phase Testing tasks → Step 3.X (Step 3.1, Step 3.2, etc.)
-  - Phase Code Review tasks → Step 4.X (Step 4.1, Step 4.2, etc.)
-- Ensure each task has UNIQUE name (increment X for each task)
-- Add tasks to TodoWrite after their corresponding command step
-
-**Output:** `✓ Step 1: Found [N] tasks across [M] phases - Ambiguities: [list or "none"]`
-
-Mark Step 1 complete in TodoWrite, mark Step 2 in_progress.
-
----
-
-## Step 2: Implementation
-
-Implement selected plan phase step-by-step following extracted tasks (Step 2.1, Step 2.2, etc.). Mark tasks complete as done. For UI work, /docs/design-guidelines.md". Use `ai-multimodal` skill for image assets, `imagemagick` for editing. Run type checking and compile to verify no syntax errors.
-
-**Output:** `✓ Step 2: Implemented [N] files - [X/Y] tasks complete, compilation passed`
-
-Mark Step 2 complete in TodoWrite, mark Step 3 in_progress.
-
----
-
-## Step 3: Testing
-
-Write tests covering happy path, edge cases, and error cases.  If ANY tests fail: STOP,  Repeat until 100% pass.
-
-**Testing standards:** Unit tests may use mocks for external dependencies (APIs, DB). Integration tests use test environment. E2E tests use real but isolated data. Forbidden: commenting out tests, changing assertions to pass, TODO/FIXME to defer fixes.
-
-**Output:** `✓ Step 3: Tests [X/X passed] - All requirements met`
-
-**Validation:** If X ≠ total, Step 3 INCOMPLETE - do not proceed.
-
-Mark Step 3 complete in TodoWrite, mark Step 4 in_progress.
-
----
-
-## Step 4: Code Review
-
- Check security, performance, architecture, YAGNI/KISS/DRY". If critical issues found: STOP, fix all, re-run `tester` to verify, re-run `code-reviewer`. Repeat until no critical issues.
-
-**Critical issues:** Security vulnerabilities (XSS, SQL injection, OWASP), performance bottlenecks, architectural violations, principle violations.
-
-**Output:** `✓ Step 4: Code reviewed - [0] critical issues`
-
-**Validation:** If critical issues > 0, Step 4 INCOMPLETE - do not proceed.
-
-Mark Step 4 complete in TodoWrite, mark Step 5 in_progress.
-
----
-
-## Step 5: User Approval ⏸ BLOCKING GATE
-
-Present summary (3-5 bullets): what implemented, tests [X/X passed], code review outcome.
-
-**Ask user explicitly:** "Phase implementation complete. All tests pass, code reviewed. Approve changes?"
-
-**Stop and wait** - do not output Step 6 content until user responds.
-
-**Output (while waiting):** `⏸ Step 5: WAITING for user approval`
-
-**Output (after approval):** `✓ Step 5: User approved - Ready to complete`
-
-Mark Step 5 complete in TodoWrite, mark Step 6 in_progress.
-
----
-
-## Step 6: Finalize
-
-**Prerequisites:** User approved in Step 5 (verified above).
-
-1. **STATUS UPDATE - BOTH MANDATORY - PARALLEL EXECUTION:**
-- **Call** `project-manager` sub-agent: "Update plan status in [plan-path]. Mark plan phase [phase-name] as DONE with timestamp. Update roadmap."
-- **Call** `docs-manager` sub-agent: "Update docs for plan phase [phase-name]. Changed files: [list]."
-
-2. **ONBOARDING CHECK:** Detect onboarding requirements (API keys, env vars, config) + generate summary report with next steps.
-
-3. **AUTO-COMMIT (after steps 1 and 2 completes):**
-- Run only if: Steps 1 and 2 successful + User approved + Tests passed
-- Auto-stage, commit with message [phase - plan] to LOCAL repository only
-- **IMPORTANT:** Do NOT push to remote repository. Only commit locally. If user wants to push, suggest them to run `/commit` or `git push` manually.
-
-**Validation:** Steps 1 and 2 must complete successfully. Step 3 (auto-commit) runs only if conditions met.
-
-Mark Step 6 complete in TodoWrite.
-
-**Phase workflow finished. Ready for next plan phase.**
-
----
-
-## Critical Enforcement Rules
-
-**Step outputs must follow unified format:** `✓ Step [N]: [Brief status] - [Key metrics]`
-
-**Examples:**
-- Step 0: `✓ Step 0: [Plan Name] - [Phase Name]`
-- Step 1: `✓ Step 1: Found [N] tasks across [M] phases - Ambiguities: [list]`
-- Step 2: `✓ Step 2: Implemented [N] files - [X/Y] tasks complete`
-- Step 3: `✓ Step 3: Tests [X/X passed] - All requirements met`
-- Step 4: `✓ Step 4: Code reviewed - [0] critical issues`
-- Step 5: `✓ Step 5: User approved - Ready to complete`
-- Step 6: `✓ Step 6: Finalize - Status updated - Git committed`
-
-**If any "✓ Step N:" output missing, that step is INCOMPLETE.**
-
-**TodoWrite tracking required:** Initialize at Step 0, mark each step complete before next.
-
-**Mandatory  calls:**
-- Step 3: `tester`
-- Step 4: `code-reviewer`
-- Step 6: `project-manager` AND `docs-manager` (when user approves)
-
-**Blocking gates:**
-- Step 3: Tests must be 100% passing
-- Step 4: Critical issues must be 0
-- Step 5: User must explicitly approve
-- Step 6: Both `project-manager` and `docs-manager` must complete successfully
-
-**REMEMBER:**
-- Do not skip steps. Do not proceed if validation fails. Do not assume approval without user response.
-- One plan phase per command run. Command focuses on single plan phase only.
-- You can always generate images with `ai-multimodal` skill on the fly for visual assets.
-- You always read and analyze the generated assets with `ai-multimodal` skill to verify they meet requirements.
-- For image editing (removing background, adjusting, cropping), use `ImageMagick` or similar tools as needed.