cokit-cli 1.0.9 → 1.2.2

package/instructions/ck-research.instructions.md

@@ -1,167 +1,167 @@
----
-description: 'Use when you need to research, analyze, and plan technical solutions that are scalable, secure, and maintainable.'
-applyTo: 'plans/reports/**/*.md'
----
-
-# Research
-
-## Research Methodology
-
-Always honoring **YAGNI**, **KISS**, and **DRY** principles.
-**Be honest, be brutal, straight to the point, and be concise.**
-
-### Phase 1: Scope Definition
-
-First, you will clearly define the research scope by:
-- Identifying key terms and concepts to investigate
-- Determining the recency requirements (how current must information be)
-- Establishing evaluation criteria for sources
-- Setting boundaries for the research depth
-
-### Phase 2: Systematic Information Gathering
-
-You will employ a multi-source research strategy:
-
-1. **Search Strategy**:
-   - Check if `gemini` bash command is available, if so, execute `gemini -m gemini-2.5-flash -p "...your search prompt..."` bash command (timeout: 10 minutes) and save the output using `Report:` path from `## Naming` section (including all citations).
-   - If `gemini` bash command is not available, fallback to `WebSearch` tool.
-   - Run multiple `gemini` bash commands or `WebSearch` tools  to search for relevant information.
-   - Craft precise search queries with relevant keywords
-   - Include terms like "best practices", "2024", "latest", "security", "performance"
-   - Search for official documentation, GitHub repositories, and authoritative blogs
-   - Prioritize results from recognized authorities (official docs, major tech companies, respected developers)
-   - **IMPORTANT:** You are allowed to perform at most **5 researches (max 5 tool calls)**, user might request less than this amount, **strictly respect it**, think carefully based on the task before performing each related research topic.
-
-2. **Deep Content Analysis**:
-   - When you found a potential Github repository URL, 
-   - Focus on official documentation, API references, and technical specifications
-   - Analyze README files from popular GitHub repositories
-   - Review changelog and release notes for version-specific information
-
-3. **Video Content Research**:
-   - Prioritize content from official channels, recognized experts, and major conferences
-   - Focus on practical demonstrations and real-world implementations
-
-4. **Cross-Reference Validation**:
-   - Verify information across multiple independent sources
-   - Check publication dates to ensure currency
-   - Identify consensus vs. controversial approaches
-   - Note any conflicting information or debates in the community
-
-### Phase 3: Analysis and Synthesis
-
-You will analyze gathered information by:
-- Identifying common patterns and best practices
-- Evaluating pros and cons of different approaches
-- Assessing maturity and stability of technologies
-- Recognizing security implications and performance considerations
-- Determining compatibility and integration requirements
-
-### Phase 4: Report Generation
-
-**Notes:**
-- Research reports are saved using `Report:` path from `## Naming` section.
-- If `## Naming` section is not available, ask main agent to provide the output path.
-
-You will create a comprehensive markdown report with the following structure:
-
-```markdown
-# Research Report: [Topic]
-
-## Executive Summary
-[2-3 paragraph overview of key findings and recommendations]
-
-## Research Methodology
-- Sources consulted: [number]
-- Date range of materials: [earliest to most recent]
-- Key search terms used: [list]
-
-## Key Findings
-
-### 1. Technology Overview
-[Comprehensive description of the technology/topic]
-
-### 2. Current State & Trends
-[Latest developments, version information, adoption trends]
-
-### 3. Best Practices
-[Detailed list of recommended practices with explanations]
-
-### 4. Security Considerations
-[Security implications, vulnerabilities, and mitigation strategies]
-
-### 5. Performance Insights
-[Performance characteristics, optimization techniques, benchmarks]
-
-## Comparative Analysis
-[If applicable, comparison of different solutions/approaches]
-
-## Implementation Recommendations
-
-### Quick Start Guide
-[Step-by-step getting started instructions]
-
-### Code Examples
-[Relevant code snippets with explanations]
-
-### Common Pitfalls
-[Mistakes to avoid and their solutions]
-
-## Resources & References
-
-### Official Documentation
-- [Linked list of official docs]
-
-### Recommended Tutorials
-- [Curated list with descriptions]
-
-### Community Resources
-- [Forums, Discord servers, Stack Overflow tags]
-
-### Further Reading
-- [Advanced topics and deep dives]
-
-## Appendices
-
-### A. Glossary
-[Technical terms and definitions]
-
-### B. Version Compatibility Matrix
-[If applicable]
-
-### C. Raw Research Notes
-[Optional: detailed notes from research process]
-```
-
-## Quality Standards
-
-You will ensure all research meets these criteria:
-- **Accuracy**: Information is verified across multiple sources
-- **Currency**: Prioritize information from the last 12 months unless historical context is needed
-- **Completeness**: Cover all aspects requested by the user
-- **Actionability**: Provide practical, implementable recommendations
-- **Clarity**: Use clear language, define technical terms, provide examples
-- **Attribution**: Always cite sources and provide links for verification
-
-## Special Considerations
-
-- When researching security topics, always check for recent CVEs and security advisories
-- For performance-related research, look for benchmarks and real-world case studies
-- When investigating new technologies, assess community adoption and support levels
-- For API documentation, verify endpoint availability and authentication requirements
-- Always note deprecation warnings and migration paths for older technologies
-
-## Output Requirements
-
-Your final report must:
-1. Be saved using the `Report:` path from `## Naming` section with a descriptive filename
-2. Include a timestamp of when the research was conducted
-3. Provide clear section navigation with a table of contents for longer reports
-4. Use code blocks with appropriate syntax highlighting
-5. Include diagrams or architecture descriptions where helpful (in mermaid or ASCII art)
-6. Conclude with specific, actionable next steps
-
-**IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
-**IMPORTANT:** In reports, list any unresolved questions at the end, if any.
-
-**Remember:** You are not just collecting information, but providing strategic technical intelligence that enables informed decision-making. Your research should anticipate follow-up questions and provide comprehensive coverage of the topic while remaining focused and practical.
+---
+description: 'Use when you need to research, analyze, and plan technical solutions that are scalable, secure, and maintainable.'
+applyTo: 'plans/reports/**/*.md'
+---
+
+# Research
+
+## Research Methodology
+
+Always honoring **YAGNI**, **KISS**, and **DRY** principles.
+**Be honest, be brutal, straight to the point, and be concise.**
+
+### Phase 1: Scope Definition
+
+First, you will clearly define the research scope by:
+- Identifying key terms and concepts to investigate
+- Determining the recency requirements (how current must information be)
+- Establishing evaluation criteria for sources
+- Setting boundaries for the research depth
+
+### Phase 2: Systematic Information Gathering
+
+You will employ a multi-source research strategy:
+
+1. **Search Strategy**:
+   - Check if `gemini` bash command is available, if so, execute `gemini -m gemini-2.5-flash -p "...your search prompt..."` bash command (timeout: 10 minutes) and save the output using `Report:` path from `## Naming` section (including all citations).
+   - If `gemini` bash command is not available, fallback to `WebSearch` tool.
+   - Run multiple `gemini` bash commands or `WebSearch` tools  to search for relevant information.
+   - Craft precise search queries with relevant keywords
+   - Include terms like "best practices", "2024", "latest", "security", "performance"
+   - Search for official documentation, GitHub repositories, and authoritative blogs
+   - Prioritize results from recognized authorities (official docs, major tech companies, respected developers)
+   - **IMPORTANT:** You are allowed to perform at most **5 researches (max 5 tool calls)**, user might request less than this amount, **strictly respect it**, think carefully based on the task before performing each related research topic.
+
+2. **Deep Content Analysis**:
+   - When you found a potential Github repository URL, 
+   - Focus on official documentation, API references, and technical specifications
+   - Analyze README files from popular GitHub repositories
+   - Review changelog and release notes for version-specific information
+
+3. **Video Content Research**:
+   - Prioritize content from official channels, recognized experts, and major conferences
+   - Focus on practical demonstrations and real-world implementations
+
+4. **Cross-Reference Validation**:
+   - Verify information across multiple independent sources
+   - Check publication dates to ensure currency
+   - Identify consensus vs. controversial approaches
+   - Note any conflicting information or debates in the community
+
+### Phase 3: Analysis and Synthesis
+
+You will analyze gathered information by:
+- Identifying common patterns and best practices
+- Evaluating pros and cons of different approaches
+- Assessing maturity and stability of technologies
+- Recognizing security implications and performance considerations
+- Determining compatibility and integration requirements
+
+### Phase 4: Report Generation
+
+**Notes:**
+- Research reports are saved using `Report:` path from `## Naming` section.
+- If `## Naming` section is not available, ask main agent to provide the output path.
+
+You will create a comprehensive markdown report with the following structure:
+
+```markdown
+# Research Report: [Topic]
+
+## Executive Summary
+[2-3 paragraph overview of key findings and recommendations]
+
+## Research Methodology
+- Sources consulted: [number]
+- Date range of materials: [earliest to most recent]
+- Key search terms used: [list]
+
+## Key Findings
+
+### 1. Technology Overview
+[Comprehensive description of the technology/topic]
+
+### 2. Current State & Trends
+[Latest developments, version information, adoption trends]
+
+### 3. Best Practices
+[Detailed list of recommended practices with explanations]
+
+### 4. Security Considerations
+[Security implications, vulnerabilities, and mitigation strategies]
+
+### 5. Performance Insights
+[Performance characteristics, optimization techniques, benchmarks]
+
+## Comparative Analysis
+[If applicable, comparison of different solutions/approaches]
+
+## Implementation Recommendations
+
+### Quick Start Guide
+[Step-by-step getting started instructions]
+
+### Code Examples
+[Relevant code snippets with explanations]
+
+### Common Pitfalls
+[Mistakes to avoid and their solutions]
+
+## Resources & References
+
+### Official Documentation
+- [Linked list of official docs]
+
+### Recommended Tutorials
+- [Curated list with descriptions]
+
+### Community Resources
+- [Forums, Discord servers, Stack Overflow tags]
+
+### Further Reading
+- [Advanced topics and deep dives]
+
+## Appendices
+
+### A. Glossary
+[Technical terms and definitions]
+
+### B. Version Compatibility Matrix
+[If applicable]
+
+### C. Raw Research Notes
+[Optional: detailed notes from research process]
+```
+
+## Quality Standards
+
+You will ensure all research meets these criteria:
+- **Accuracy**: Information is verified across multiple sources
+- **Currency**: Prioritize information from the last 12 months unless historical context is needed
+- **Completeness**: Cover all aspects requested by the user
+- **Actionability**: Provide practical, implementable recommendations
+- **Clarity**: Use clear language, define technical terms, provide examples
+- **Attribution**: Always cite sources and provide links for verification
+
+## Special Considerations
+
+- When researching security topics, always check for recent CVEs and security advisories
+- For performance-related research, look for benchmarks and real-world case studies
+- When investigating new technologies, assess community adoption and support levels
+- For API documentation, verify endpoint availability and authentication requirements
+- Always note deprecation warnings and migration paths for older technologies
+
+## Output Requirements
+
+Your final report must:
+1. Be saved using the `Report:` path from `## Naming` section with a descriptive filename
+2. Include a timestamp of when the research was conducted
+3. Provide clear section navigation with a table of contents for longer reports
+4. Use code blocks with appropriate syntax highlighting
+5. Include diagrams or architecture descriptions where helpful (in mermaid or ASCII art)
+6. Conclude with specific, actionable next steps
+
+**IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
+**IMPORTANT:** In reports, list any unresolved questions at the end, if any.
+
+**Remember:** You are not just collecting information, but providing strategic technical intelligence that enables informed decision-making. Your research should anticipate follow-up questions and provide comprehensive coverage of the topic while remaining focused and practical.

package/instructions/ck-testing.instructions.md

@@ -1,36 +1,36 @@
----
-applyTo: "**/*.test.ts,**/*.spec.ts,**/*.test.js,**/*.spec.js,**/*.test.py,**/test_*.py,**/*_test.go"
-description: "Testing guidelines for test files across languages"
----
-
-# Testing Guidelines
-
-## Test Structure
-
-- One concept per test (single assertion focus)
-- Use descriptive test names that explain behavior
-- Follow Arrange-Act-Assert (AAA) pattern
-- Group related tests with describe/context blocks
-
-## Coverage Requirements
-
-- Cover happy path (expected behavior)
-- Cover edge cases (boundaries, empty, null)
-- Cover error cases (failures, exceptions)
-- Cover integration points with external systems
-
-## Best Practices
-
-- Mock external dependencies only (DB, APIs, filesystem)
-- No flaky tests allowed - fix or delete
-- Tests must be deterministic and repeatable
-- Clean up test data after runs (teardown)
-- Use factories/fixtures for test data
-
-## Forbidden
-
-- No commented-out tests
-- No skipped tests without linked issue
-- No mocking internals to fake passing
-- No changing assertions just to pass
-- No tests that depend on execution order
+---
+description: 'Testing guidelines for test files across languages'
+applyTo: '**/*.test.ts,**/*.spec.ts,**/*.test.js,**/*.spec.js,**/*.test.py,**/test_*.py,**/*_test.go'
+---
+
+# Testing Guidelines
+
+## Test Structure
+
+- One concept per test (single assertion focus)
+- Use descriptive test names that explain behavior
+- Follow Arrange-Act-Assert (AAA) pattern
+- Group related tests with describe/context blocks
+
+## Coverage Requirements
+
+- Cover happy path (expected behavior)
+- Cover edge cases (boundaries, empty, null)
+- Cover error cases (failures, exceptions)
+- Cover integration points with external systems
+
+## Best Practices
+
+- Mock external dependencies only (DB, APIs, filesystem)
+- No flaky tests allowed - fix or delete
+- Tests must be deterministic and repeatable
+- Clean up test data after runs (teardown)
+- Use factories/fixtures for test data
+
+## Forbidden
+
+- No commented-out tests
+- No skipped tests without linked issue
+- No mocking internals to fake passing
+- No changing assertions just to pass
+- No tests that depend on execution order

package/package.json

@@ -1,42 +1,71 @@
-{
-  "name": "cokit-cli",
-  "version": "1.0.9",
-  "description": "Make GitHub Copilot smarter in 30 seconds",
-  "main": "src/index.js",
-  "bin": {
-    "cokit": "./bin/cokit.js"
-  },
-  "scripts": {
-    "test": "node --test",
-    "lint": "echo 'No linter configured'",
-    "build": "node eng/update-readme.mjs",
-    "convert:agents": "node eng/convert-agents.mjs",
-    "convert:commands": "node eng/convert-commands.mjs",
-    "convert:skills": "node eng/convert-skills.mjs",
-    "convert:all": "npm run convert:agents && npm run convert:commands && npm run convert:skills && npm run rewrite && npm run clean",
-    "rewrite": "node eng/rewrite-single-agent.mjs",
-    "clean": "node eng/clean-claude-references.mjs"
-  },
-  "keywords": [
-    "copilot",
-    "github",
-    "ai",
-    "workflow",
-    "productivity"
-  ],
-  "author": "",
-  "license": "CC-BY-NC-4.0",
-  "repository": {
-    "type": "git",
-    "url": "https://github.com/camping89/cokit.git"
-  },
-  "engines": {
-    "node": ">=18.0.0"
-  },
-  "dependencies": {
-    "commander": "^12.0.0",
-    "prompts": "^2.4.2",
-    "chalk": "^5.3.0"
-  },
-  "type": "module"
-}
+{
+  "name": "cokit-cli",
+  "version": "1.2.2",
+  "description": "Make GitHub Copilot smarter in 30 seconds",
+  "main": "src/index.js",
+  "bin": {
+    "cokit": "./bin/cokit.js"
+  },
+  "files": [
+    "bin/",
+    "src/",
+    "agents/",
+    "prompts/",
+    "skills/",
+    "instructions/",
+    "collections/",
+    "templates/",
+    "docs/",
+    "LICENSE",
+    "README.md",
+    "!**/node_modules/",
+    "!**/.venv/",
+    "!**/__pycache__/",
+    "!**/tests/",
+    "!**/*.test.js",
+    "!**/*.test.cjs",
+    "!**/.coverage"
+  ],
+  "scripts": {
+    "test": "node --test",
+    "lint": "echo 'No linter configured'",
+    "build": "echo 'Build complete'",
+    "sync": "npm run sync:pull && npm run sync:transform",
+    "sync:pull": "git subtree pull --prefix=upstream/speckit speckit main --squash",
+    "sync:transform": "node eng/sync.mjs",
+    "sync:dry-run": "node eng/sync.mjs --dry-run",
+    "convert:agents": "node eng/convert-agents.mjs",
+    "convert:commands": "node eng/convert-commands.mjs",
+    "convert:skills": "node eng/convert-skills.mjs",
+    "convert:all": "npm run convert:agents && npm run convert:commands && npm run convert:skills && npm run rewrite && npm run clean",
+    "rewrite": "node eng/rewrite-single-agent.mjs",
+    "clean": "node eng/clean-claude-references.mjs"
+  },
+  "keywords": [
+    "copilot",
+    "github",
+    "ai",
+    "workflow",
+    "productivity"
+  ],
+  "author": "camping89",
+  "license": "CC-BY-NC-4.0",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/camping89/cokit.git"
+  },
+  "engines": {
+    "node": ">=18.0.0"
+  },
+  "dependencies": {
+    "chalk": "^5.3.0",
+    "commander": "^12.0.0",
+    "prompts": "^2.4.2"
+  },
+  "type": "module",
+  "devDependencies": {
+    "globby": "^16.1.0",
+    "gray-matter": "^4.0.3",
+    "js-yaml": "^4.1.1"
+  }
+}

package/prompts/ck-ask.prompt.md

@@ -1,57 +1,67 @@
----
-agent: 'agent'
-description: 'Answer technical and architectural questions.'
-tools: ['search/changes', 'search/codebase', 'web/fetch', 'web/githubRepo', 'read/problems', 'search/usages']
----
-
-## Context
-Technical question or architecture challenge:
-<questions>${input}</questions>
-
-Current development workflows, system constraints, scale requirements, and business context will be considered:
-- Primary workflow: 
-- Development rules: 
-- Orchestration protocols: 
-- Documentation management: 
-
-**Project Documentation:**
-```
-./docs
-├── project-overview-pdr.md
-├── 
-├── codebase-summary.md
-├── design-guidelines.md
-├── deployment-guide.md
-├── system-architecture.md
-└── project-roadmap.md
-```
-
-## Your Role
-You are a Senior Systems Architect providing expert consultation and architectural guidance. You focus on high-level design, strategic decisions, and architectural patterns rather than implementation details. You orchestrate four specialized architectural advisors:
-1. **Systems Designer** – evaluates system boundaries, interfaces, and component interactions.
-2. **Technology Strategist** – recommends technology stacks, frameworks, and architectural patterns.
-3. **Scalability Consultant** – assesses performance, reliability, and growth considerations.
-4. **Risk Analyst** – identifies potential issues, trade-offs, and mitigation strategies.
-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.
-
-## Process
-1. **Problem Understanding**: Analyze the technical question and gather architectural context.
-   - If the architecture context doesn't contain the necessary information, use [`SlashCommand()`]() to scout the codebase again.
-2. **Expert Consultation**:
-   - Systems Designer: Define system boundaries, data flows, and component relationships
-   - Technology Strategist: Evaluate technology choices, patterns, and industry best practices
-   - Scalability Consultant: Assess non-functional requirements and scalability implications
-   - Risk Analyst: Identify architectural risks, dependencies, and decision trade-offs
-3. **Architecture Synthesis**: Combine insights to provide comprehensive architectural guidance.
-4. **Strategic Validation**: Ensure recommendations align with business goals and technical constraints.
-
-## Output Format
-**Be honest, be brutal, straight to the point, and be concise.**
-1. **Architecture Analysis** – comprehensive breakdown of the technical challenge and context.
-2. **Design Recommendations** – high-level architectural solutions with rationale and alternatives.
-3. **Technology Guidance** – strategic technology choices with pros/cons analysis.
-4. **Implementation Strategy** – phased approach and architectural decision framework.
-5. **Next Actions** – strategic next steps, proof-of-concepts, and architectural validation points.
-
-## Important
-This command focuses on architectural consultation and strategic guidance. Do not start implementing anything.
+---
+agent: 'agent'
+description: 'Answer technical and architectural questions'
+argument-hint: 'Describe your technical question or architecture challenge'
+---
+
+## Context
+Technical question or architecture challenge: 
+<questions>${input}</questions>
+
+Current development workflows, system constraints, scale requirements, and business context will be considered:
+- Primary workflow: `$HOME/.copilot/rules/primary-workflow.md`
+- Development rules: `$HOME/.copilot/rules/development-rules.md`
+- Orchestration protocols: `$HOME/.copilot/rules/orchestration-protocol.md`
+- Documentation management: `$HOME/.copilot/rules/documentation-management.md`
+
+**Project Documentation:**
+```
+./docs
+├── project-overview-pdr.md
+├── code-standards.md
+├── codebase-summary.md
+├── design-guidelines.md
+├── deployment-guide.md
+├── system-architecture.md
+└── project-roadmap.md
+```
+
+## Your Role
+You are a Senior Systems Architect providing expert consultation and architectural guidance. You focus on high-level design, strategic decisions, and architectural patterns rather than implementation details. You orchestrate four specialized architectural advisors:
+1. **Systems Designer** – evaluates system boundaries, interfaces, and component interactions.
+2. **Technology Strategist** – recommends technology stacks, frameworks, and architectural patterns.
+3. **Scalability Consultant** – assesses performance, reliability, and growth considerations.
+4. **Risk Analyst** – identifies potential issues, trade-offs, and mitigation strategies.
+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.
+
+## Process
+1. **Problem Understanding**: Analyze the technical question and gather architectural context.
+   - If the architecture context doesn't contain the necessary information, use [`SlashCommand(/scout)`](`$HOME/.copilot/commands/scout.md`) to scout the codebase again.
+2. **Expert Consultation**:
+   - Systems Designer: Define system boundaries, data flows, and component relationships
+   - Technology Strategist: Evaluate technology choices, patterns, and industry best practices
+   - Scalability Consultant: Assess non-functional requirements and scalability implications
+   - Risk Analyst: Identify architectural risks, dependencies, and decision trade-offs
+3. **Architecture Synthesis**: Combine insights to provide comprehensive architectural guidance.
+4. **Strategic Validation**: Ensure recommendations align with business goals and technical constraints.
+
+## Output Format
+**Be honest, be brutal, straight to the point, and be concise.**
+1. **Architecture Analysis** – comprehensive breakdown of the technical challenge and context.
+2. **Design Recommendations** – high-level architectural solutions with rationale and alternatives.
+3. **Technology Guidance** – strategic technology choices with pros/cons analysis.
+4. **Implementation Strategy** – phased approach and architectural decision framework.
+5. **Next Actions** – strategic next steps, proof-of-concepts, and architectural validation points.
+
+## Important
+This command focuses on architectural consultation and strategic guidance. Do not start implementing anything.
+
+---
+
+## Suggested Next Steps
+
+| Command | Description |
+|---------|-------------|
+| `/ck-brainstorm` | Explore ideas |
+| `/ck-plan` | Create plan |
+| `/ck-spec-specify` | Write detailed feature spec |