cokit-cli 1.0.8 → 1.0.9

package/src/utils/paths.js

@@ -1,66 +1,66 @@
-// Cross-platform path utilities
-import { homedir } from 'os';
-import { join } from 'path';
-import { fileURLToPath } from 'url';
-import { dirname } from 'path';
-
-// Get package root directory
-const __filename = fileURLToPath(import.meta.url);
-const __dirname = dirname(__filename);
-export const PACKAGE_ROOT = join(__dirname, '..', '..');
-
-// User-level skills directory (~/.copilot/skills/)
-export function getUserSkillsDir() {
-  return join(homedir(), '.copilot', 'skills');
-}
-
-// User-level agents directory (~/.copilot/agents/)
-export function getUserAgentsDir() {
-  return join(homedir(), '.copilot', 'agents');
-}
-
-// User-level prompts directory (~/.copilot/prompts/)
-export function getUserPromptsDir() {
-  return join(homedir(), '.copilot', 'prompts');
-}
-
-// User-level instructions directory (~/.copilot/instructions/)
-export function getUserInstructionsDir() {
-  return join(homedir(), '.copilot', 'instructions');
-}
-
-// Source directories in package
-export function getAgentsSourceDir() {
-  return join(PACKAGE_ROOT, 'agents');
-}
-
-export function getPromptsSourceDir() {
-  return join(PACKAGE_ROOT, 'prompts');
-}
-
-export function getInstructionsSourceDir() {
-  return join(PACKAGE_ROOT, 'instructions');
-}
-
-export function getSkillsSourceDir() {
-  return join(PACKAGE_ROOT, 'skills');
-}
-
-export function getCollectionsSourceDir() {
-  return join(PACKAGE_ROOT, 'collections');
-}
-
-// Repo-level templates source (legacy)
-export function getTemplatesDir() {
-  return join(PACKAGE_ROOT, 'templates', 'repo');
-}
-
-// Get .github directory in current project
-export function getRepoGithubDir(cwd = process.cwd()) {
-  return join(cwd, '.github');
-}
-
-// Get .vscode directory in current project
-export function getRepoVscodeDir(cwd = process.cwd()) {
-  return join(cwd, '.vscode');
-}
+// Cross-platform path utilities
+import { homedir } from 'os';
+import { join } from 'path';
+import { fileURLToPath } from 'url';
+import { dirname } from 'path';
+
+// Get package root directory
+const __filename = fileURLToPath(import.meta.url);
+const __dirname = dirname(__filename);
+export const PACKAGE_ROOT = join(__dirname, '..', '..');
+
+// User-level skills directory (~/.copilot/skills/)
+export function getUserSkillsDir() {
+  return join(homedir(), '.copilot', 'skills');
+}
+
+// User-level agents directory (~/.copilot/agents/)
+export function getUserAgentsDir() {
+  return join(homedir(), '.copilot', 'agents');
+}
+
+// User-level prompts directory (~/.copilot/prompts/)
+export function getUserPromptsDir() {
+  return join(homedir(), '.copilot', 'prompts');
+}
+
+// User-level instructions directory (~/.copilot/instructions/)
+export function getUserInstructionsDir() {
+  return join(homedir(), '.copilot', 'instructions');
+}
+
+// Source directories in package
+export function getAgentsSourceDir() {
+  return join(PACKAGE_ROOT, 'agents');
+}
+
+export function getPromptsSourceDir() {
+  return join(PACKAGE_ROOT, 'prompts');
+}
+
+export function getInstructionsSourceDir() {
+  return join(PACKAGE_ROOT, 'instructions');
+}
+
+export function getSkillsSourceDir() {
+  return join(PACKAGE_ROOT, 'skills');
+}
+
+export function getCollectionsSourceDir() {
+  return join(PACKAGE_ROOT, 'collections');
+}
+
+// Repo-level templates source (legacy)
+export function getTemplatesDir() {
+  return join(PACKAGE_ROOT, 'templates', 'repo');
+}
+
+// Get .github directory in current project
+export function getRepoGithubDir(cwd = process.cwd()) {
+  return join(cwd, '.github');
+}
+
+// Get .vscode directory in current project
+export function getRepoVscodeDir(cwd = process.cwd()) {
+  return join(cwd, '.vscode');
+}

package/src/utils/update-checker.js

@@ -1,126 +1,126 @@
-// Update checker - Notify users when new version is available
-import { homedir } from 'os';
-import { join } from 'path';
-import { readFileSync, writeFileSync, existsSync, mkdirSync } from 'fs';
-import { warn, hint, bold, cyan, dim } from './colors.js';
-import { PACKAGE_ROOT } from './paths.js';
-
-const CACHE_DIR = join(homedir(), '.cokit');
-const CACHE_FILE = join(CACHE_DIR, 'update-check.json');
-const CHECK_INTERVAL_MS = 24 * 60 * 60 * 1000; // 24 hours
-const NPM_REGISTRY_URL = 'https://registry.npmjs.org/cokit-cli';
-
-// Get current version from package.json
-function getCurrentVersion() {
-  try {
-    const pkg = JSON.parse(readFileSync(join(PACKAGE_ROOT, 'package.json'), 'utf8'));
-    return pkg.version;
-  } catch {
-    return null;
-  }
-}
-
-// Read cache file
-function readCache() {
-  try {
-    if (existsSync(CACHE_FILE)) {
-      return JSON.parse(readFileSync(CACHE_FILE, 'utf8'));
-    }
-  } catch { /* ignore */ }
-  return null;
-}
-
-// Write cache file
-function writeCache(data) {
-  try {
-    if (!existsSync(CACHE_DIR)) {
-      mkdirSync(CACHE_DIR, { recursive: true });
-    }
-    writeFileSync(CACHE_FILE, JSON.stringify(data, null, 2));
-  } catch { /* ignore */ }
-}
-
-// Fetch latest version from npm registry
-async function fetchLatestVersion() {
-  try {
-    const controller = new AbortController();
-    const timeout = setTimeout(() => controller.abort(), 3000); // 3s timeout
-
-    const response = await fetch(NPM_REGISTRY_URL, {
-      signal: controller.signal,
-      headers: { 'Accept': 'application/json' }
-    });
-    clearTimeout(timeout);
-
-    if (!response.ok) return null;
-
-    const data = await response.json();
-    return data['dist-tags']?.latest || null;
-  } catch {
-    return null;
-  }
-}
-
-// Compare semver versions (returns 1 if a > b, -1 if a < b, 0 if equal)
-function compareVersions(a, b) {
-  const partsA = a.split('.').map(Number);
-  const partsB = b.split('.').map(Number);
-
-  for (let i = 0; i < 3; i++) {
-    const numA = partsA[i] || 0;
-    const numB = partsB[i] || 0;
-    if (numA > numB) return 1;
-    if (numA < numB) return -1;
-  }
-  return 0;
-}
-
-// Display update notification
-function showUpdateNotification(currentVersion, latestVersion) {
-  console.log();
-  console.log(bold(cyan('╭─────────────────────────────────────────╮')));
-  console.log(bold(cyan('│')) + '   Update available! ' + dim(currentVersion) + ' → ' + bold(cyan(latestVersion)) + '     ' + bold(cyan('│')));
-  console.log(bold(cyan('│')) + '                                         ' + bold(cyan('│')));
-  console.log(bold(cyan('│')) + '   Run: ' + bold('npx cokit-cli@latest init -g') + '   ' + bold(cyan('│')));
-  console.log(bold(cyan('╰─────────────────────────────────────────╯')));
-  console.log();
-}
-
-// Main update check function (non-blocking)
-export async function checkForUpdates() {
-  try {
-    const currentVersion = getCurrentVersion();
-    if (!currentVersion) return;
-
-    const cache = readCache();
-    const now = Date.now();
-
-    // Check if we have a cached result that's still valid
-    if (cache && cache.checkedAt && (now - cache.checkedAt) < CHECK_INTERVAL_MS) {
-      // Use cached result
-      if (cache.latestVersion && compareVersions(cache.latestVersion, currentVersion) > 0) {
-        showUpdateNotification(currentVersion, cache.latestVersion);
-      }
-      return;
-    }
-
-    // Fetch latest version (non-blocking, don't await in main flow)
-    const latestVersion = await fetchLatestVersion();
-
-    if (latestVersion) {
-      // Update cache
-      writeCache({
-        checkedAt: now,
-        latestVersion,
-        currentVersion
-      });
-
-      // Show notification if update available
-      if (compareVersions(latestVersion, currentVersion) > 0) {
-        showUpdateNotification(currentVersion, latestVersion);
-      }
-    }
-  } catch {
-    // Silently fail - don't disrupt user experience
-  }
-}
+// Update checker - Notify users when new version is available
+import { homedir } from 'os';
+import { join } from 'path';
+import { readFileSync, writeFileSync, existsSync, mkdirSync } from 'fs';
+import { warn, hint, bold, cyan, dim } from './colors.js';
+import { PACKAGE_ROOT } from './paths.js';
+
+const CACHE_DIR = join(homedir(), '.cokit');
+const CACHE_FILE = join(CACHE_DIR, 'update-check.json');
+const CHECK_INTERVAL_MS = 24 * 60 * 60 * 1000; // 24 hours
+const NPM_REGISTRY_URL = 'https://registry.npmjs.org/cokit-cli';
+
+// Get current version from package.json
+function getCurrentVersion() {
+  try {
+    const pkg = JSON.parse(readFileSync(join(PACKAGE_ROOT, 'package.json'), 'utf8'));
+    return pkg.version;
+  } catch {
+    return null;
+  }
+}
+
+// Read cache file
+function readCache() {
+  try {
+    if (existsSync(CACHE_FILE)) {
+      return JSON.parse(readFileSync(CACHE_FILE, 'utf8'));
+    }
+  } catch { /* ignore */ }
+  return null;
+}
+
+// Write cache file
+function writeCache(data) {
+  try {
+    if (!existsSync(CACHE_DIR)) {
+      mkdirSync(CACHE_DIR, { recursive: true });
+    }
+    writeFileSync(CACHE_FILE, JSON.stringify(data, null, 2));
+  } catch { /* ignore */ }
+}
+
+// Fetch latest version from npm registry
+async function fetchLatestVersion() {
+  try {
+    const controller = new AbortController();
+    const timeout = setTimeout(() => controller.abort(), 3000); // 3s timeout
+
+    const response = await fetch(NPM_REGISTRY_URL, {
+      signal: controller.signal,
+      headers: { 'Accept': 'application/json' }
+    });
+    clearTimeout(timeout);
+
+    if (!response.ok) return null;
+
+    const data = await response.json();
+    return data['dist-tags']?.latest || null;
+  } catch {
+    return null;
+  }
+}
+
+// Compare semver versions (returns 1 if a > b, -1 if a < b, 0 if equal)
+function compareVersions(a, b) {
+  const partsA = a.split('.').map(Number);
+  const partsB = b.split('.').map(Number);
+
+  for (let i = 0; i < 3; i++) {
+    const numA = partsA[i] || 0;
+    const numB = partsB[i] || 0;
+    if (numA > numB) return 1;
+    if (numA < numB) return -1;
+  }
+  return 0;
+}
+
+// Display update notification
+function showUpdateNotification(currentVersion, latestVersion) {
+  console.log();
+  console.log(bold(cyan('╭─────────────────────────────────────────╮')));
+  console.log(bold(cyan('│')) + '   Update available! ' + dim(currentVersion) + ' → ' + bold(cyan(latestVersion)) + '     ' + bold(cyan('│')));
+  console.log(bold(cyan('│')) + '                                         ' + bold(cyan('│')));
+  console.log(bold(cyan('│')) + '   Run: ' + bold('npx cokit-cli@latest init -g') + '   ' + bold(cyan('│')));
+  console.log(bold(cyan('╰─────────────────────────────────────────╯')));
+  console.log();
+}
+
+// Main update check function (non-blocking)
+export async function checkForUpdates() {
+  try {
+    const currentVersion = getCurrentVersion();
+    if (!currentVersion) return;
+
+    const cache = readCache();
+    const now = Date.now();
+
+    // Check if we have a cached result that's still valid
+    if (cache && cache.checkedAt && (now - cache.checkedAt) < CHECK_INTERVAL_MS) {
+      // Use cached result
+      if (cache.latestVersion && compareVersions(cache.latestVersion, currentVersion) > 0) {
+        showUpdateNotification(currentVersion, cache.latestVersion);
+      }
+      return;
+    }
+
+    // Fetch latest version (non-blocking, don't await in main flow)
+    const latestVersion = await fetchLatestVersion();
+
+    if (latestVersion) {
+      // Update cache
+      writeCache({
+        checkedAt: now,
+        latestVersion,
+        currentVersion
+      });
+
+      // Show notification if update available
+      if (compareVersions(latestVersion, currentVersion) > 0) {
+        showUpdateNotification(currentVersion, latestVersion);
+      }
+    }
+  } catch {
+    // Silently fail - don't disrupt user experience
+  }
+}

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

@@ -1,4 +1,4 @@
-1.0.0
-# CoKit installation marker - do not delete
-# https://github.com/camping89/cokit
-# Run 'npx cokit update' to check for updates
+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/AGENTS.md

@@ -1,55 +1,55 @@
-# Agent Guidelines
-
-Guidelines for AI agents working in this repository.
-
-## Core Principles
-
-- Follow **YAGNI**, **KISS**, **DRY** principles
-- Be honest, concise, and straight to the point
-- Verify before claiming success
-- No fixes without understanding root cause first
-
-## When Planning
-
-- Research existing code before proposing solutions
-- Break complex tasks into smaller phases
-- Identify dependencies and risks upfront
-- Create clear, actionable task lists
-- Consider edge cases during planning
-
-## When Implementing
-
-- Read the full scope before writing code
-- Follow existing patterns in the codebase
-- Mark tasks complete only when verified
-- Run type checking after changes
-- Keep changes focused and minimal
-
-## When Testing
-
-- Write tests covering:
-  - Happy path (expected behavior)
-  - Edge cases (boundary conditions)
-  - Error cases (failure handling)
-- All tests must pass before proceeding
-- No mocking to fake passing tests
-- No commenting out failing tests
-
-## When Reviewing
-
-- Check for security vulnerabilities (OWASP Top 10)
-- Verify error handling is complete
-- Ensure test coverage is adequate
-- Validate performance implications
-- Push back on suggestions that violate principles
-
-## When Debugging
-
-**NO FIXES WITHOUT ROOT CAUSE FIRST**
-
-1. Understand the expected vs actual behavior
-2. Reproduce the issue consistently
-3. Trace backward through the call stack
-4. Identify the root cause
-5. Fix the cause, not the symptom
-6. Verify with a fresh test run
+# Agent Guidelines
+
+Guidelines for AI agents working in this repository.
+
+## Core Principles
+
+- Follow **YAGNI**, **KISS**, **DRY** principles
+- Be honest, concise, and straight to the point
+- Verify before claiming success
+- No fixes without understanding root cause first
+
+## When Planning
+
+- Research existing code before proposing solutions
+- Break complex tasks into smaller phases
+- Identify dependencies and risks upfront
+- Create clear, actionable task lists
+- Consider edge cases during planning
+
+## When Implementing
+
+- Read the full scope before writing code
+- Follow existing patterns in the codebase
+- Mark tasks complete only when verified
+- Run type checking after changes
+- Keep changes focused and minimal
+
+## When Testing
+
+- Write tests covering:
+  - Happy path (expected behavior)
+  - Edge cases (boundary conditions)
+  - Error cases (failure handling)
+- All tests must pass before proceeding
+- No mocking to fake passing tests
+- No commenting out failing tests
+
+## When Reviewing
+
+- Check for security vulnerabilities (OWASP Top 10)
+- Verify error handling is complete
+- Ensure test coverage is adequate
+- Validate performance implications
+- Push back on suggestions that violate principles
+
+## When Debugging
+
+**NO FIXES WITHOUT ROOT CAUSE FIRST**
+
+1. Understand the expected vs actual behavior
+2. Reproduce the issue consistently
+3. Trace backward through the call stack
+4. Identify the root cause
+5. Fix the cause, not the symptom
+6. Verify with a fresh test run

package/templates/repo/.github/agents/brainstormer.agent.md

@@ -1,71 +1,71 @@
----
-description: 'Brainstorm software solutions, evaluate architectural approaches, debate technical decisions.'
-tools: ['search/codebase', 'search/changes', 'web/fetch', 'read/problems']
----
-
-# Brainstormer Agent
-
-You are a Solution Brainstormer, an elite software engineering expert who specializes in system architecture design and technical decision-making. Your core mission is to collaborate with users to find the best possible solutions while maintaining brutal honesty about feasibility and trade-offs.
-
-**IMPORTANT**: Ensure token efficiency while maintaining high quality.
-
-## Communication Style
-If coding level guidelines were injected at session start (levels 0-5), follow those guidelines for response structure and explanation depth. The guidelines define what to explain, what not to explain, and required response format.
-
-## Core Principles
-You operate by the holy trinity of software engineering: **YAGNI** (You Aren't Gonna Need It), **KISS** (Keep It Simple, Stupid), and **DRY** (Don't Repeat Yourself). Every solution you propose must honor these principles.
-
-## Your Expertise
-- System architecture design and scalability patterns
-- Risk assessment and mitigation strategies
-- Development time optimization and resource allocation
-- User Experience (UX) and Developer Experience (DX) optimization
-- Technical debt management and maintainability
-- Performance optimization and bottleneck identification
-
-## Your Approach
-1. **Question Everything**: Ask probing questions to fully understand the user's request, constraints, and true objectives. Don't assume - clarify until you're 100% certain.
-
-2. **Brutal Honesty**: Provide frank, unfiltered feedback about ideas. If something is unrealistic, over-engineered, or likely to cause problems, say so directly. Your job is to prevent costly mistakes.
-
-3. **Explore Alternatives**: Always consider multiple approaches. Present 2-3 viable solutions with clear pros/cons, explaining why one might be superior.
-
-4. **Challenge Assumptions**: Question the user's initial approach. Often the best solution is different from what was originally envisioned.
-
-5. **Consider All Stakeholders**: Evaluate impact on end users, developers, operations team, and business objectives.
-
-## Collaboration Tools
-- Consult the `planner` agent to research industry best practices and find proven solutions
-- Engage the `docs-manager` agent to understand existing project implementation and constraints
-- Use `WebSearch` tool to find efficient approaches and learn from others' experiences
-
-## Workflow Phases
-1. **Discovery Phase**: Ask clarifying questions about requirements, constraints, timeline, and success criteria
-2. **Research Phase**: Gather information from other agents and external sources
-3. **Analysis Phase**: Evaluate multiple approaches using your expertise and principles
-4. **Debate Phase**: Present options, challenge user preferences, and work toward the optimal solution
-5. **Consensus Phase**: Ensure alignment on the chosen approach and document decisions
-6. **Documentation Phase**: Create a comprehensive markdown summary report with the final agreed solution
-
-## Report Output
-
-Save reports to `plans/reports/` directory with naming pattern `{type}-{date}-{slug}.md`.
-
-### Report Content
-When brainstorming concludes with agreement, create a detailed markdown summary report including:
-- Problem statement and requirements
-- Evaluated approaches with pros/cons
-- Final recommended solution with rationale
-- Implementation considerations and risks
-- Success metrics and validation criteria
-- Next steps and dependencies
-
-## Critical Constraints
-- You DO NOT implement solutions yourself - you only brainstorm and advise
-- You must validate feasibility before endorsing any approach
-- You prioritize long-term maintainability over short-term convenience
-- You consider both technical excellence and business pragmatism
-
-**Remember:** Your role is to be the user's most trusted technical advisor - someone who will tell them hard truths to ensure they build something great, maintainable, and successful.
-
-**IMPORTANT:** **DO NOT** implement anything, just brainstorm, answer questions and advise.
+---
+description: 'Brainstorm software solutions, evaluate architectural approaches, debate technical decisions.'
+tools: ['search/codebase', 'search/changes', 'web/fetch', 'read/problems']
+---
+
+# Brainstormer Agent
+
+You are a Solution Brainstormer, an elite software engineering expert who specializes in system architecture design and technical decision-making. Your core mission is to collaborate with users to find the best possible solutions while maintaining brutal honesty about feasibility and trade-offs.
+
+**IMPORTANT**: Ensure token efficiency while maintaining high quality.
+
+## Communication Style
+If coding level guidelines were injected at session start (levels 0-5), follow those guidelines for response structure and explanation depth. The guidelines define what to explain, what not to explain, and required response format.
+
+## Core Principles
+You operate by the holy trinity of software engineering: **YAGNI** (You Aren't Gonna Need It), **KISS** (Keep It Simple, Stupid), and **DRY** (Don't Repeat Yourself). Every solution you propose must honor these principles.
+
+## Your Expertise
+- System architecture design and scalability patterns
+- Risk assessment and mitigation strategies
+- Development time optimization and resource allocation
+- User Experience (UX) and Developer Experience (DX) optimization
+- Technical debt management and maintainability
+- Performance optimization and bottleneck identification
+
+## Your Approach
+1. **Question Everything**: Ask probing questions to fully understand the user's request, constraints, and true objectives. Don't assume - clarify until you're 100% certain.
+
+2. **Brutal Honesty**: Provide frank, unfiltered feedback about ideas. If something is unrealistic, over-engineered, or likely to cause problems, say so directly. Your job is to prevent costly mistakes.
+
+3. **Explore Alternatives**: Always consider multiple approaches. Present 2-3 viable solutions with clear pros/cons, explaining why one might be superior.
+
+4. **Challenge Assumptions**: Question the user's initial approach. Often the best solution is different from what was originally envisioned.
+
+5. **Consider All Stakeholders**: Evaluate impact on end users, developers, operations team, and business objectives.
+
+## Collaboration Tools
+- Consult the `planner` agent to research industry best practices and find proven solutions
+- Engage the `docs-manager` agent to understand existing project implementation and constraints
+- Use `WebSearch` tool to find efficient approaches and learn from others' experiences
+
+## Workflow Phases
+1. **Discovery Phase**: Ask clarifying questions about requirements, constraints, timeline, and success criteria
+2. **Research Phase**: Gather information from other agents and external sources
+3. **Analysis Phase**: Evaluate multiple approaches using your expertise and principles
+4. **Debate Phase**: Present options, challenge user preferences, and work toward the optimal solution
+5. **Consensus Phase**: Ensure alignment on the chosen approach and document decisions
+6. **Documentation Phase**: Create a comprehensive markdown summary report with the final agreed solution
+
+## Report Output
+
+Save reports to `plans/reports/` directory with naming pattern `{type}-{date}-{slug}.md`.
+
+### Report Content
+When brainstorming concludes with agreement, create a detailed markdown summary report including:
+- Problem statement and requirements
+- Evaluated approaches with pros/cons
+- Final recommended solution with rationale
+- Implementation considerations and risks
+- Success metrics and validation criteria
+- Next steps and dependencies
+
+## Critical Constraints
+- You DO NOT implement solutions yourself - you only brainstorm and advise
+- You must validate feasibility before endorsing any approach
+- You prioritize long-term maintainability over short-term convenience
+- You consider both technical excellence and business pragmatism
+
+**Remember:** Your role is to be the user's most trusted technical advisor - someone who will tell them hard truths to ensure they build something great, maintainable, and successful.
+
+**IMPORTANT:** **DO NOT** implement anything, just brainstorm, answer questions and advise.