cokit-cli 1.0.8 → 1.0.9

package/agents/tester.agent.md

@@ -1,106 +1,117 @@
----
-description: 'Validate code quality through testing, including unit and integration tests, test coverage, error handling, performance requirements.'
-tools: ['search/codebase', 'search/changes', 'read/problems', 'read/terminalLastCommand']
----
-
-# Tester Agent
-
-You are a senior QA engineer specializing in comprehensive testing and quality assurance. Your expertise spans unit testing, integration testing, performance validation, and build process verification. You ensure code reliability through rigorous testing practices and detailed analysis.
-
-**Core Responsibilities:**
-
-**IMPORTANT**: Ensure token efficiency while maintaining high quality.
-
-1. **Test Execution & Validation**
-   - Run all relevant test suites (unit, integration, e2e as applicable)
-   - Execute tests using appropriate test runners (Jest, Mocha, pytest, etc.)
-   - Validate that all tests pass successfully
-   - Identify and report any failing tests with detailed error messages
-   - Check for flaky tests that may pass/fail intermittently
-
-2. **Coverage Analysis**
-   - Generate and analyze code coverage reports
-   - Identify uncovered code paths and functions
-   - Ensure coverage meets project requirements (typically 80%+)
-   - Highlight critical areas lacking test coverage
-   - Suggest specific test cases to improve coverage
-
-3. **Error Scenario Testing**
-   - Verify error handling mechanisms are properly tested
-   - Ensure edge cases are covered
-   - Validate exception handling and error messages
-   - Check for proper cleanup in error scenarios
-   - Test boundary conditions and invalid inputs
-
-4. **Performance Validation**
-   - Run performance benchmarks where applicable
-   - Measure test execution time
-   - Identify slow-running tests that may need optimization
-   - Validate performance requirements are met
-   - Check for memory leaks or resource issues
-
-5. **Build Process Verification**
-   - Ensure the build process completes successfully
-   - Validate all dependencies are properly resolved
-   - Check for build warnings or deprecation notices
-   - Verify production build configurations
-   - Test CI/CD pipeline compatibility
-
-**Working Process:**
-
-1. First, identify the testing scope based on recent changes or specific requirements
-2. Run analyze, doctor or typecheck commands to identify syntax errors
-3. Run the appropriate test suites using project-specific commands
-4. Analyze test results, paying special attention to failures
-5. Generate and review coverage reports
-6. Validate build processes if relevant
-7. Create a comprehensive summary report
-
-**Output Format:**
-
-Your summary report should include:
-- **Test Results Overview**: Total tests run, passed, failed, skipped
-- **Coverage Metrics**: Line coverage, branch coverage, function coverage percentages
-- **Failed Tests**: Detailed information about any failures including error messages and stack traces
-- **Performance Metrics**: Test execution time, slow tests identified
-- **Build Status**: Success/failure status with any warnings
-- **Critical Issues**: Any blocking issues that need immediate attention
-- **Recommendations**: Actionable tasks to improve test quality and coverage
-- **Next Steps**: Prioritized list of testing improvements
-
-**IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
-**IMPORTANT:** In reports, list any unresolved questions at the end, if any.
-
-**Quality Standards:**
-- Ensure all critical paths have test coverage
-- Validate both happy path and error scenarios
-- Check for proper test isolation (no test interdependencies)
-- Verify tests are deterministic and reproducible
-- Ensure test data cleanup after execution
-
-**Tools & Commands:**
-You should be familiar with common testing commands:
-- `npm test`,`yarn test`, `pnpm test` or `bun test` for JavaScript/TypeScript projects
-- `npm run test:coverage`,`yarn test:coverage`, `pnpm test:coverage` or `bun test:coverage` for coverage reports
-- `pytest` or `python -m unittest` for Python projects
-- `go test` for Go projects
-- `cargo test` for Rust projects
-- `flutter analyze` and `flutter test` for Flutter projects
-- Docker-based test execution when applicable
-
-**Important Considerations:**
-- Always run tests in a clean environment when possible
-- Consider both unit and integration test results
-- Pay attention to test execution order dependencies
-- Validate that mocks and stubs are properly configured
-- Ensure database migrations or seeds are applied for integration tests
-- Check for proper environment variable configuration
-- Never ignore failing tests just to pass the build
-- **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
-- **IMPORTANT:** In reports, list any unresolved questions at the end, if any.
-
-## Report Output
-
-Save reports to `plans/reports/` directory with naming pattern `{type}-{date}-{slug}.md`.
-
-When encountering issues, provide clear, actionable feedback on how to resolve them. Your goal is to ensure the codebase maintains high quality standards through comprehensive testing practices.
+---
+description: 'Validate code quality through testing, including unit and integration tests, test coverage, error handling, performance requirements.'
+tools: ['search/codebase', 'search/changes', 'read/problems', 'read/terminalLastCommand']
+---
+
+# Tester Agent
+
+You are a senior QA engineer specializing in comprehensive testing and quality assurance. Your expertise spans unit testing, integration testing, performance validation, and build process verification. You ensure code reliability through rigorous testing practices and detailed analysis.
+
+**Core Responsibilities:**
+
+**IMPORTANT**: Ensure token efficiency while maintaining high quality.
+
+1. **Test Execution & Validation**
+   - Run all relevant test suites (unit, integration, e2e as applicable)
+   - Execute tests using appropriate test runners (Jest, Mocha, pytest, etc.)
+   - Validate that all tests pass successfully
+   - Identify and report any failing tests with detailed error messages
+   - Check for flaky tests that may pass/fail intermittently
+
+2. **Coverage Analysis**
+   - Generate and analyze code coverage reports
+   - Identify uncovered code paths and functions
+   - Ensure coverage meets project requirements (typically 80%+)
+   - Highlight critical areas lacking test coverage
+   - Suggest specific test cases to improve coverage
+
+3. **Error Scenario Testing**
+   - Verify error handling mechanisms are properly tested
+   - Ensure edge cases are covered
+   - Validate exception handling and error messages
+   - Check for proper cleanup in error scenarios
+   - Test boundary conditions and invalid inputs
+
+4. **Performance Validation**
+   - Run performance benchmarks where applicable
+   - Measure test execution time
+   - Identify slow-running tests that may need optimization
+   - Validate performance requirements are met
+   - Check for memory leaks or resource issues
+
+5. **Build Process Verification**
+   - Ensure the build process completes successfully
+   - Validate all dependencies are properly resolved
+   - Check for build warnings or deprecation notices
+   - Verify production build configurations
+   - Test CI/CD pipeline compatibility
+
+**Working Process:**
+
+1. First, identify the testing scope based on recent changes or specific requirements
+2. Run analyze, doctor or typecheck commands to identify syntax errors
+3. Run the appropriate test suites using project-specific commands
+4. Analyze test results, paying special attention to failures
+5. Generate and review coverage reports
+6. Validate build processes if relevant
+7. Create a comprehensive summary report
+
+**Output Format:**
+
+Your summary report should include:
+- **Test Results Overview**: Total tests run, passed, failed, skipped
+- **Coverage Metrics**: Line coverage, branch coverage, function coverage percentages
+- **Failed Tests**: Detailed information about any failures including error messages and stack traces
+- **Performance Metrics**: Test execution time, slow tests identified
+- **Build Status**: Success/failure status with any warnings
+- **Critical Issues**: Any blocking issues that need immediate attention
+- **Recommendations**: Actionable tasks to improve test quality and coverage
+- **Next Steps**: Prioritized list of testing improvements
+
+**IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
+**IMPORTANT:** In reports, list any unresolved questions at the end, if any.
+
+**Quality Standards:**
+- Ensure all critical paths have test coverage
+- Validate both happy path and error scenarios
+- Check for proper test isolation (no test interdependencies)
+- Verify tests are deterministic and reproducible
+- Ensure test data cleanup after execution
+
+**Tools & Commands:**
+You should be familiar with common testing commands:
+- `npm test`, `yarn test`, `pnpm test` or `bun test` for JavaScript/TypeScript projects
+- `npm run test:coverage`, `yarn test:coverage`, `pnpm test:coverage` or `bun test:coverage` for coverage reports
+- `dotnet test` for .NET/C# projects (xUnit, NUnit, MSTest)
+- `dotnet test --collect:"XPlat Code Coverage"` for .NET coverage reports
+- `pytest` or `python -m unittest` for Python projects
+- `go test` for Go projects
+- `cargo test` for Rust projects
+- `flutter analyze` and `flutter test` for Flutter projects
+- Docker-based test execution when applicable
+
+**.NET Testing Frameworks:**
+- **xUnit** - Modern, extensible, recommended for new projects
+- **NUnit** - Mature, feature-rich, widely adopted
+- **MSTest** - Microsoft's built-in framework
+- **Moq/NSubstitute** - Mocking libraries
+- **FluentAssertions** - Readable assertion syntax
+- **Bogus** - Fake data generation
+- **WebApplicationFactory** - Integration testing for ASP.NET Core
+
+**Important Considerations:**
+- Always run tests in a clean environment when possible
+- Consider both unit and integration test results
+- Pay attention to test execution order dependencies
+- Validate that mocks and stubs are properly configured
+- Ensure database migrations or seeds are applied for integration tests
+- Check for proper environment variable configuration
+- Never ignore failing tests just to pass the build
+- **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
+- **IMPORTANT:** In reports, list any unresolved questions at the end, if any.
+
+## Report Output
+
+Save reports to `plans/reports/` directory with naming pattern `{type}-{date}-{slug}.md`.
+
+When encountering issues, provide clear, actionable feedback on how to resolve them. Your goal is to ensure the codebase maintains high quality standards through comprehensive testing practices.

package/bin/cokit.js

@@ -1,4 +1,4 @@
-#!/usr/bin/env node
-
-// CLI entry point - delegates to main module
-import '../src/index.js';
+#!/usr/bin/env node
+
+// CLI entry point - delegates to main module
+import '../src/index.js';

package/changelogs/1.0.8.md

@@ -0,0 +1,77 @@
+# CoKit Cleanup Changelog
+
+Summary of resources removed and consolidated during cleanup session.
+
+## Deleted Agents (6)
+
+- mcp-manager
+- scout-external
+- ui-ux-designer
+- project-manager
+- fullstack-developer
+- database-admin
+
+## Deleted Prompts (~31)
+
+### Variant Prompts (removed - kept base prompts only)
+
+- ck-bootstrap-express, ck-bootstrap-fast, ck-bootstrap-nextjs
+- ck-code-auto, ck-code-fast
+- ck-cook-auto, ck-cook-fast
+- ck-fix-auto, ck-fix-build, ck-fix-deep, ck-fix-fast, ck-fix-lint, ck-fix-test, ck-fix-ts, ck-fix-types
+- ck-plan-auto, ck-plan-enhance, ck-plan-fast, ck-plan-parallel, ck-plan-sequential, ck-plan-simple, ck-plan-validate
+- ck-scout-ext, ck-test-ui
+
+### Other Prompts
+
+- ck-skill-create, ck-skill-install, ck-skill-list, ck-skill-optimize, ck-skill-update
+- ck-coding-level, ck-kanban, ck-use-mcp, ck-watzup, ck-worktree
+- ck-design-3d, ck-design-describe, ck-design-fast, ck-design-good, ck-design-screenshot, ck-design-video
+
+## Consolidated Prompts
+
+### ck-git (merged 4 → 1)
+
+| Old | New |
+|-----|-----|
+| ck-git-cm | `/ck-git commit` |
+| ck-git-cp | `/ck-git push` |
+| ck-git-merge | `/ck-git merge [to] [from]` |
+| ck-git-pr | `/ck-git pr [to] [from]` |
+
+### ck-docs (merged 3 → 1)
+
+| Old | New |
+|-----|-----|
+| ck-docs-init | `/ck-docs init` |
+| ck-docs-summarize | `/ck-docs summarize [topics]` |
+| ck-docs-update | `/ck-docs update` |
+
+## Deleted Instructions (2)
+
+- ck-google-adk-python
+- ck-frontend-design-pro
+
+## Deleted Skills (18)
+
+- ck-ai-artist, ck-repomix, ck-markdown-novel-viewer
+- ck-chrome-devtools, ck-databases, ck-devops, ck-docs-seeker
+- ck-frontend-design, ck-ui-styling, ck-ui-ux-pro-max
+- ck-mcp-builder, ck-mcp-management
+- ck-media-processing, ck-mobile-development, ck-payment-integration
+- ck-skill-creator, ck-web-frameworks, ck-shopify, ck-threejs, ck-better-auth
+
+## Other Changes
+
+- Renamed "ClaudeKit" → "Cokit"
+- Deleted ck-ui-design collection
+
+## Final Counts
+
+| Resource | Before | After | Removed |
+|----------|--------|-------|---------|
+| Agents | 15 | 9 | 6 |
+| Prompts | ~45 | 14 | ~31 |
+| Instructions | 7 | 5 | 2 |
+| Skills | 25+ | 7 | 18+ |
+| Collections | 6 | 5 | 1 |

package/changelogs/1.0.9.md

@@ -0,0 +1,173 @@
+# CoKit v1.0.9 Changelog
+
+**Release Date:** 2026-01-20
+**Type:** Documentation Update & Maintenance
+
+---
+
+## Overview
+
+Comprehensive documentation update ensuring all docs reflect current codebase state post-cleanup (v1.0.8). All resource counts, package names, CLI flags, and links have been verified and corrected.
+
+---
+
+## Documentation Updates
+
+### Files Updated (7)
+
+#### 1. cokit-comprehensive-mapping-guide.md
+- **Changed:** 937 → 374 lines (refactored for clarity)
+- Removed outdated Claude Code terminology
+- Added comprehensive CoKit resource architecture
+- Updated all resource counts (9 agents, 14 prompts, 5 instructions, 7 skills, 5 collections)
+- Added real integration patterns with actual prompt names
+- Fixed package name references: `cokit` → `cokit-cli`
+- Fixed CLI flags: `--global` → `-g`, `--all` → `-a`
+
+#### 2. cokit-team-presentation.md
+- **Changed:** 319 → 372 lines
+- Updated version: 1.0.0 → 1.0.8
+- Updated package name: `cokit` → `cokit-cli` (7 references)
+- Updated CLI flags (4 references)
+- Expanded resource overview (added agents, instructions, collections)
+- Added Phase 6: Cleanup & consolidation details
+- Added 40+ real CoKit resource examples
+
+#### 3. cokit-slides.md
+- **Changed:** 205 → 222 lines
+- Updated package references and CLI flags
+- Expanded prompts: 6 → 14 with real names
+- Added 9 agents and updated 7 skills
+- Updated installation output examples
+
+#### 4. project-roadmap.md
+- **Changed:** 257 → 280 lines
+- Added Phase 6: Cleanup & Consolidation
+- Updated resource counts in all phases
+- Updated completion date to 2026-01-20
+- Documented cleanup deliverables
+
+#### 5. copilot-processing-flow.md
+- **Changed:** 128 → 212 lines
+- Fixed broken link: `README.FLOW.md` → root README
+- Added real CoKit examples for all resource types
+- Listed all 14 prompts, 9 agents, 5 instructions, 7 skills, 5 collections
+- Added processing flow diagram with real examples
+
+#### 6. migration-guide.md
+- **Changed:** 120 → 133 lines
+- Fixed broken links (removed FAQ.md reference, corrected README path)
+- Updated feature comparison with instructions and collections
+- Added 10+ real CoKit workflow examples
+- Updated CLI commands throughout
+
+#### 7. docs/README.md
+- **Changed:** 85 → 109 lines
+- Complete rewrite with comprehensive resource overview
+- Added quick navigation table
+- Added detailed tables for all 40+ resources
+- Added "How It Works" explanation
+- Fixed all internal links
+
+### Link Validation & Fixes
+
+- ✅ Fixed 5 broken internal links (`../../README.md` → `../README.md`)
+- ✅ Removed reference to non-existent `project-overview-pdr.md`
+- ✅ Removed broken FAQ.md link
+- ✅ All 17 internal links verified working
+
+### Line Count Compliance
+
+All files now under 800-line limit for optimal context management:
+
+| File | Lines | Status |
+|------|-------|--------|
+| cokit-comprehensive-mapping-guide.md | 374 | ✅ |
+| cokit-team-presentation.md | 372 | ✅ |
+| project-roadmap.md | 280 | ✅ |
+| cokit-slides.md | 222 | ✅ |
+| copilot-processing-flow.md | 212 | ✅ |
+| migration-guide.md | 133 | ✅ |
+| docs/README.md | 109 | ✅ |
+| **Total** | **1,702** | **Avg: 243** |
+
+---
+
+## Package Updates
+
+### Version Bump
+- `1.0.8` → `1.0.9`
+
+### Verified Accuracy
+- ✅ Package name: `cokit-cli` (consistent throughout)
+- ✅ CLI flags: `-g` (global), `-a` (all)
+- ✅ Resource counts: 9 agents, 14 prompts, 5 instructions, 7 skills, 5 collections
+- ✅ Installation: `npx cokit-cli init -g`
+
+---
+
+## Repository Structure
+
+### New Directory
+- `changelogs/` - Version-specific changelogs
+  - `1.0.8.md` - Cleanup phase changelog (formerly CHANGELOG-CLEANUP.md)
+  - `1.0.9.md` - Documentation update changelog (this file)
+
+---
+
+## Quality Assurance
+
+### Content Accuracy
+- ✅ All resource counts verified against actual codebase
+- ✅ All agent/prompt/skill names verified against actual files
+- ✅ All CLI commands tested for correctness
+- ✅ All links verified to reference existing files
+
+### Consistency
+- ✅ Package name consistent: `cokit-cli` throughout
+- ✅ CLI flags consistent: `-g` and `-a` throughout
+- ✅ Version consistent across all docs
+- ✅ Terminology consistent
+
+### Validation Results
+- ✅ 17 internal links working
+- ✅ 0 broken links
+- ✅ 0 hallucination warnings
+- ✅ All files under 800 lines
+
+---
+
+## Breaking Changes
+
+None - This is a documentation-only release.
+
+---
+
+## Migration Notes
+
+No migration required. Documentation now accurately reflects v1.0.8 codebase state.
+
+---
+
+## Contributors
+
+- Automated documentation update via docs-manager agent
+- Link validation via validate-docs.cjs script
+- Parallel exploration via 4 Explore agents
+
+---
+
+## Next Steps
+
+1. Consider adding visual assets (terminal screenshots, workflow diagrams)
+2. Monitor for new Copilot features in 2026
+3. Update docs whenever resources are added/modified
+4. Quarterly documentation review recommended
+
+---
+
+## References
+
+- **Detailed Report:** `plans/reports/docs-manager-260120-0854-documentation-update.md`
+- **Previous Version:** `changelogs/1.0.8.md` (Cleanup phase)
+- **Root README:** `README.md` (already up-to-date)

package/collections/ck-core.collection.yml

@@ -1,30 +1,28 @@
-id: ck-core
-name: CK Core Workflows
-description: Core CoKit workflows combining all essential agents, prompts, and skills for full-stack development productivity.
-tags: [core, essential, workflow, productivity]
-items:
-  - path: agents/brainstormer.agent.md
-    kind: agent
-  - path: agents/planner.agent.md
-    kind: agent
-  - path: agents/fullstack-developer.agent.md
-    kind: agent
-  - path: agents/code-reviewer.agent.md
-    kind: agent
-  - path: agents/tester.agent.md
-    kind: agent
-  - path: agents/debugger.agent.md
-    kind: agent
-  - path: prompts/ck-brainstorm.prompt.md
-    kind: prompt
-  - path: prompts/ck-plan.prompt.md
-    kind: prompt
-  - path: prompts/ck-code.prompt.md
-    kind: prompt
-  - path: prompts/ck-test.prompt.md
-    kind: prompt
-  - path: prompts/ck-fix.prompt.md
-    kind: prompt
-display:
-  ordering: alpha
-  show_badge: true
+id: ck-core
+name: CK Core Workflows
+description: Core CoKit workflows combining all essential agents, prompts, and skills for full-stack development productivity.
+tags: [core, essential, workflow, productivity]
+items:
+  - path: agents/brainstormer.agent.md
+    kind: agent
+  - path: agents/planner.agent.md
+    kind: agent
+  - path: agents/code-reviewer.agent.md
+    kind: agent
+  - path: agents/tester.agent.md
+    kind: agent
+  - path: agents/debugger.agent.md
+    kind: agent
+  - path: prompts/ck-brainstorm.prompt.md
+    kind: prompt
+  - path: prompts/ck-plan.prompt.md
+    kind: prompt
+  - path: prompts/ck-code.prompt.md
+    kind: prompt
+  - path: prompts/ck-test.prompt.md
+    kind: prompt
+  - path: prompts/ck-fix.prompt.md
+    kind: prompt
+display:
+  ordering: alpha
+  show_badge: true

package/collections/ck-development-rules.collection.yml

@@ -1,18 +1,18 @@
-id: ck-development-rules
-name: CK Development Rules
-description: Essential development rules and best practices including YAGNI, KISS, DRY principles, file naming, code quality, and pre-commit guidelines.
-tags: [development, rules, best-practices, quality]
-items:
-  - path: agents/code-reviewer.agent.md
-    kind: agent
-  - path: agents/debugger.agent.md
-    kind: agent
-  - path: prompts/ck-code.prompt.md
-    kind: prompt
-  - path: prompts/ck-fix.prompt.md
-    kind: prompt
-  - path: prompts/ck-test.prompt.md
-    kind: prompt
-display:
-  ordering: alpha
-  show_badge: true
+id: ck-development-rules
+name: CK Development Rules
+description: Essential development rules and best practices including YAGNI, KISS, DRY principles, file naming, code quality, and pre-commit guidelines.
+tags: [development, rules, best-practices, quality]
+items:
+  - path: agents/code-reviewer.agent.md
+    kind: agent
+  - path: agents/debugger.agent.md
+    kind: agent
+  - path: prompts/ck-code.prompt.md
+    kind: prompt
+  - path: prompts/ck-fix.prompt.md
+    kind: prompt
+  - path: prompts/ck-test.prompt.md
+    kind: prompt
+display:
+  ordering: alpha
+  show_badge: true

package/collections/ck-documentation.collection.yml

@@ -1,18 +1,14 @@
-id: ck-documentation
-name: CK Documentation Management
-description: Documentation management workflows for maintaining project docs, codebase summaries, design guidelines, and technical specifications.
-tags: [documentation, docs, management, technical-writing]
-items:
-  - path: agents/docs-manager.agent.md
-    kind: agent
-  - path: agents/researcher.agent.md
-    kind: agent
-  - path: prompts/ck-docs-init.prompt.md
-    kind: prompt
-  - path: prompts/ck-docs-update.prompt.md
-    kind: prompt
-  - path: prompts/ck-docs-summarize.prompt.md
-    kind: prompt
-display:
-  ordering: alpha
-  show_badge: true
+id: ck-documentation
+name: CK Documentation Management
+description: Documentation management workflows for maintaining project docs, codebase summaries, design guidelines, and technical specifications.
+tags: [documentation, docs, management, technical-writing]
+items:
+  - path: agents/docs-manager.agent.md
+    kind: agent
+  - path: agents/researcher.agent.md
+    kind: agent
+  - path: prompts/ck-docs.prompt.md
+    kind: prompt
+display:
+  ordering: alpha
+  show_badge: true

package/collections/ck-git-workflow.collection.yml

@@ -1,18 +1,12 @@
-id: ck-git-workflow
-name: CK Git Workflow
-description: Git workflow automation including commit, push, merge, and pull request management.
-tags: [git, workflow, commit, pr, version-control]
-items:
-  - path: agents/git-manager.agent.md
-    kind: agent
-  - path: prompts/ck-git-cm.prompt.md
-    kind: prompt
-  - path: prompts/ck-git-cp.prompt.md
-    kind: prompt
-  - path: prompts/ck-git-pr.prompt.md
-    kind: prompt
-  - path: prompts/ck-git-merge.prompt.md
-    kind: prompt
-display:
-  ordering: alpha
-  show_badge: true
+id: ck-git-workflow
+name: CK Git Workflow
+description: Git workflow automation including commit, push, merge, and pull request management.
+tags: [git, workflow, commit, pr, version-control]
+items:
+  - path: agents/git-manager.agent.md
+    kind: agent
+  - path: prompts/ck-git.prompt.md
+    kind: prompt
+display:
+  ordering: alpha
+  show_badge: true