cokit-cli 1.0.0 → 1.0.1

package/FAQ.md

@@ -28,7 +28,7 @@ Yes! Edit any `.prompt.md` file in `.github/prompts/`.
 
 Type the prompt name in Copilot Chat:
 ```
-/fix my login function throws an error
+/ck-fix my login function throws an error
 ```
 
 ### Why isn't Copilot responding to my prompts?
@@ -55,12 +55,12 @@ Your instructions here...
 **Repo-level (`.github/`):**
 - `copilot-instructions.md` - Project rules
 - `AGENTS.md` - Agent behavior
-- `prompts/*.prompt.md` - 6 prompt files
-- `skills/*/SKILL.md` - 2 skill files
-- `instructions/*.instructions.md` - 4 instruction files
+- `prompts/ck-*.prompt.md` - 6 prompt files (ck-fix, ck-plan, etc.)
+- `skills/ck-*/SKILL.md` - 2 skill files (ck-debugging, ck-code-review)
+- `instructions/ck-*.instructions.md` - 4 instruction files
 
 **User-level (`~/.copilot/skills/`):**
-- 5 skill directories with SKILL.md + references
+- 5 skill directories: ck-debugging, ck-code-review, ck-planning, ck-docs-seeker, ck-sequential-thinking
 
 ### Does CoKit modify my code?
 

package/QUICK-START.md

@@ -12,7 +12,7 @@ Open your project in VS Code.
 
 ## Step 3: Try It
 
-Type `/fix` in Copilot Chat.
+Type `/ck-fix` in Copilot Chat.
 
 ## Done!
 
@@ -24,9 +24,9 @@ You now have 6 prompts and 5 skills ready to use.
 
 Try these prompts in Copilot Chat:
 
-- `/fix` - Got a bug? Copilot will debug it
-- `/plan` - Need a feature? Copilot will plan it
-- `/review` - Ready to commit? Copilot will review it
+- `/ck-fix` - Got a bug? Copilot will debug it
+- `/ck-plan` - Need a feature? Copilot will plan it
+- `/ck-review` - Ready to commit? Copilot will review it
 
 ## Need Help?
 

package/README.md

@@ -11,7 +11,7 @@ Make GitHub Copilot smarter in 30 seconds.
 npx cokit init
 ```
 
-That's it! Now open VS Code and try `/fix` in Copilot Chat.
+That's it! Now open VS Code and try `/ck-fix` in Copilot Chat.
 
 ## What You Get
 
@@ -19,12 +19,14 @@ That's it! Now open VS Code and try `/fix` in Copilot Chat.
 
 | Command | What it does |
 |---------|--------------|
-| `/fix` | Debug and fix code issues |
-| `/plan` | Create implementation plans |
-| `/review` | Review code before committing |
-| `/test` | Write tests for your code |
-| `/code` | Implement from a plan |
-| `/docs` | Update documentation |
+| `/ck-fix` | Debug and fix code issues |
+| `/ck-plan` | Create implementation plans |
+| `/ck-review` | Review code before committing |
+| `/ck-test` | Write tests for your code |
+| `/ck-code` | Implement from a plan |
+| `/ck-docs` | Update documentation |
+
+> **Why `ck-` prefix?** Prevents conflicts with other tools. Easy to identify CoKit prompts.
 
 ### Skills (automatic)
 

package/docs/migration-guide.md

@@ -6,12 +6,12 @@ This guide helps Claude Code users adapt to GitHub Copilot with CoKit.
 
 | Feature | Claude Code | CoKit/Copilot |
 |---------|-------------|---------------|
-| Commands | `/fix:types`, `/plan:auto` | `/fix`, `/plan` |
+| Commands | `/fix:types`, `/plan:auto` | `/ck-fix`, `/ck-plan` |
 | Arguments | `$ARGUMENTS` variable | User provides in chat |
 | Subagents | Task tool with agents | Single Copilot agent |
 | Hooks | Pre/post execution | Not supported |
-| Skills | `~/.claude/skills/` | `~/.copilot/skills/` |
-| Prompts | `~/.claude/commands/` | `.github/prompts/` |
+| Skills | `~/.claude/skills/` | `~/.copilot/skills/ck-*/` |
+| Prompts | `~/.claude/commands/` | `.github/prompts/ck-*.prompt.md` |
 
 ## What's Different
 
@@ -25,8 +25,8 @@ This guide helps Claude Code users adapt to GitHub Copilot with CoKit.
 
 **Copilot:**
 ```
-/fix the type errors in auth.ts
-/fix the failing tests in user.test.ts
+/ck-fix the type errors in auth.ts
+/ck-fix the failing tests in user.test.ts
 ```
 
 Provide context directly in your message.
@@ -78,11 +78,11 @@ After fixing:
 
 | Claude Skill | CoKit Skill | Notes |
 |--------------|-------------|-------|
-| debugging | debugging | Same methodology |
-| code-review | code-review | Same principles |
-| planning | planning | Simplified workflow |
-| docs-seeker | docs-seeker | Same search patterns |
-| sequential-thinking | sequential-thinking | Same approach |
+| debugging | ck-debugging | Same methodology |
+| code-review | ck-code-review | Same principles |
+| planning | ck-planning | Simplified workflow |
+| docs-seeker | ck-docs-seeker | Same search patterns |
+| sequential-thinking | ck-sequential-thinking | Same approach |
 
 ## What Works the Same
 
@@ -100,8 +100,8 @@ After fixing:
 
 2. Use prompts directly:
    ```
-   /fix (describe your issue)
-   /plan (describe your feature)
+   /ck-fix (describe your issue)
+   /ck-plan (describe your feature)
    ```
 
 3. Skills work automatically - no changes needed.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cokit-cli",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "description": "Make GitHub Copilot smarter in 30 seconds",
   "main": "src/index.js",
   "bin": {

package/src/commands/init.js

@@ -88,7 +88,7 @@ export const initCommand = new Command('init')
 
       // Success message
       done('Done! Open VS Code and start using Copilot.');
-      hint('Try typing /fix in Copilot Chat.');
+      hint('Try typing /ck-fix in Copilot Chat.');
       console.log();
 
     } catch (err) {

package/templates/repo/prompts/code.prompt.md

@@ -1,40 +0,0 @@
----
-mode: agent
-description: Implement from existing plan
----
-# Implement Plan
-
-Implement the specified plan phase.
-
-## Process
-
-1. **Read Plan**
-   - Load plan.md completely
-   - Identify current phase
-   - List tasks to complete
-
-2. **Implement**
-   - Work through tasks sequentially
-   - Follow existing patterns
-   - Run type checks frequently
-
-3. **Test**
-   - Write tests for new code
-   - Run full test suite
-   - Fix any failures
-
-4. **Review**
-   - Check for security issues
-   - Verify error handling
-   - Ensure code quality
-
-5. **Complete**
-   - Update plan status
-   - Summarize changes
-   - List remaining work
-
-## Guidelines
-- Follow YAGNI/KISS/DRY
-- Keep files under 200 lines
-- Document complex logic
-- No TODO without issue tracking

package/templates/repo/prompts/docs.prompt.md

@@ -1,29 +0,0 @@
----
-mode: agent
-description: Update project documentation
----
-# Update Documentation
-
-Update documentation for recent changes.
-
-## Process
-
-1. **Identify Changes**
-   - Review recent commits
-   - List new features
-   - Note API changes
-
-2. **Update Docs**
-   - README.md for user-facing changes
-   - API docs for endpoint changes
-   - Architecture docs for structural changes
-
-3. **Verify**
-   - Links work
-   - Examples accurate
-   - No outdated references
-
-## Guidelines
-- Keep concise
-- Use examples
-- Update table of contents

package/templates/repo/prompts/fix.prompt.md

@@ -1,35 +0,0 @@
----
-mode: agent
-description: Debug and fix code issues
----
-# Fix Issue
-
-Analyze the described issue and fix it systematically.
-
-## Process
-
-1. **Identify Issue Type**
-   - Type errors → Check TypeScript config, type definitions
-   - UI/UX issues → Check styles, layout, responsiveness
-   - Test failures → Run tests, analyze failures
-   - Build errors → Check dependencies, config
-
-2. **Investigate Root Cause**
-   - Read error messages completely
-   - Find working examples in codebase
-   - Trace back to source of problem
-
-3. **Apply Fix**
-   - Make minimal changes
-   - Follow existing patterns
-   - Update related tests
-
-4. **Verify**
-   - Run tests
-   - Check types compile
-   - Confirm issue resolved
-
-## Guidelines
-- No fixes without understanding root cause
-- One fix at a time
-- Verify before claiming done

package/templates/repo/prompts/plan.prompt.md

@@ -1,41 +0,0 @@
----
-mode: agent
-description: Create implementation plan for features
----
-# Create Plan
-
-Create a detailed implementation plan for the described task.
-
-## Process
-
-1. **Understand Requirements**
-   - Clarify scope and constraints
-   - Identify dependencies
-   - Note assumptions
-
-2. **Research**
-   - Review relevant codebase areas
-   - Check existing patterns
-   - Identify technical approach
-
-3. **Design Solution**
-   - Break into phases
-   - List tasks per phase
-   - Estimate effort
-
-4. **Document Plan**
-   - Create plan file in ./plans/
-   - Include success criteria
-   - List open questions
-
-## Output
-Create `./plans/{date}-{name}/plan.md` with:
-- Overview (1-3 sentences)
-- Phases table
-- Success criteria checklist
-- Unresolved questions
-
-## Principles
-- YAGNI: Don't over-engineer
-- KISS: Prefer simple solutions
-- DRY: Identify reusable patterns

package/templates/repo/prompts/review.prompt.md

@@ -1,38 +0,0 @@
----
-mode: agent
-description: Review code for issues
----
-# Code Review
-
-Review the specified code for quality and issues.
-
-## Check Categories
-
-### Security
-- [ ] Input validation
-- [ ] No hardcoded secrets
-- [ ] SQL injection prevention
-- [ ] XSS prevention
-
-### Performance
-- [ ] No N+1 queries
-- [ ] Appropriate caching
-- [ ] No memory leaks
-
-### Quality
-- [ ] YAGNI compliance
-- [ ] KISS compliance
-- [ ] DRY compliance
-- [ ] Error handling
-- [ ] Test coverage
-
-### Maintainability
-- [ ] Clear naming
-- [ ] Reasonable file size
-- [ ] Documentation for complex logic
-
-## Output
-List issues by severity:
-- **Critical**: Must fix before merge
-- **Important**: Should fix soon
-- **Minor**: Nice to have

package/templates/repo/prompts/test.prompt.md

@@ -1,29 +0,0 @@
----
-mode: agent
-description: Run tests and analyze results
----
-# Run Tests
-
-Run the test suite and analyze results.
-
-## Process
-
-1. **Run Tests**
-   - Execute test command (npm test, pytest, etc.)
-   - Capture full output
-
-2. **Analyze Results**
-   - Count passed/failed/skipped
-   - Identify failure patterns
-   - Check for flaky tests
-
-3. **Report**
-   - Summary: X passed, Y failed, Z skipped
-   - List failing tests with error messages
-   - Suggest fixes for failures
-
-## If Tests Fail
-- Read error message completely
-- Find root cause before fixing
-- Fix one issue at a time
-- Re-run to verify fix