cokit-cli 1.0.5 → 1.0.6

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

@@ -18,13 +18,13 @@ Think harder to plan & start working on these tasks follow the Orchestration Pro
 
 ## Your Approach
 
-1. **Question Everything**: Use `AskUserQuestion` tool to ask probing questions to fully understand the user's request, constraints, and true objectives. Don't assume - clarify until you're 100% certain.
+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. Use `AskUserQuestion` tool to ask the user for their preferences.
+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. Ask the user for their preferences.
 
-3. **Explore Alternatives**: Always consider multiple approaches. Present 2-3 viable solutions with clear pros/cons, explaining why one might be superior. Use `AskUserQuestion` tool to ask the user for their preferences.
+3. **Explore Alternatives**: Always consider multiple approaches. Present 2-3 viable solutions with clear pros/cons, explaining why one might be superior. Ask the user for their preferences.
 
-4. **Challenge Assumptions**: Question the user's initial approach. Often the best solution is different from what was originally envisioned. Use `AskUserQuestion` tool to ask the user for their preferences.
+4. **Challenge Assumptions**: Question the user's initial approach. Often the best solution is different from what was originally envisioned. Ask the user for their preferences.
 
 5. **Consider All Stakeholders**: Evaluate impact on end users, developers, operations team, and business objectives.
 
@@ -34,7 +34,7 @@ Think harder to plan & start working on these tasks follow the Orchestration Pro
 
 ### Fullfill the request
 
-* If you have any questions, use `AskUserQuestion` tool to ask the user to clarify them.
+* If you have any questions, ask the user to clarify them.
 * Ask 1 question at a time, wait for the user to answer before moving to the next question.
 * If you don't have any questions, start the next step.
 
@@ -86,7 +86,8 @@ Think harder to plan & start working on these tasks follow the Orchestration Pro
 
 ### Final Report
 * Report back to user with a summary of the changes and explain everything briefly, guide user to get started and suggest the next steps.
-* Ask the user if they want to commit and push to git repository, if yes, commit and push to git repository.
+* Ask the user if they want to commit changes to git repository, if yes, commit 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.
 - **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
 - **IMPORTANT:** In reports, list any unresolved questions at the end, if any.
 

package/templates/repo/.github/prompts/ck-fix-hard.prompt.md

@@ -12,9 +12,9 @@ tools: ['search/codebase', 'search/changes', 'read/problems', 'read/terminalLast
 If the user provides a screenshots or videos, 
 
 ### Fullfill the request
-**Question Everything**: Use `AskUserQuestion` tool to ask probing questions to fully understand the user's request, constraints, and true objectives. Don't assume - clarify until you're 100% certain.
+**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.
 
-* If you have any questions, use `AskUserQuestion` tool to ask the user to clarify them.
+* If you have any questions, ask the user to clarify them.
 * Ask 1 question at a time, wait for the user to answer before moving to the next question.
 * If you don't have any questions, start the next step.
 

package/templates/repo/.github/prompts/ck-git-merge.prompt.md

@@ -37,5 +37,5 @@ git push origin {TO_BRANCH}
 
 ## Notes
 - If `gh` command is not available, instruct the user to install and authorize GitHub CLI first.
-- If you need more clarifications, use `AskUserQuestion` tool to ask the user for more details.
+- If you need more clarifications, ask the user for more details.
 - Always fetch and pull latest remote state before merging to avoid stale conflicts.

package/templates/repo/.github/prompts/ck-plan-archive.prompt.md

@@ -20,7 +20,7 @@ Read the plan directory:
 - `phase-*.md` - 20 first lines of each phase file to understand the progress and status
 
 ### Step 2: Summarize the plans and document them with `/journal` 
-Use `AskUserQuestion` tool to ask if user wants to document journal entries or not.
+Ask if user wants to document journal entries or not.
 Skip this step if user selects "No".
 If user selects "Yes":
 - Analyze the information in previous steps.
@@ -29,8 +29,8 @@ If user selects "Yes":
 - Keep journal entries in the `./docs/journals/` directory.
 
 ### Step 3: Ask user to confirm the action before archiving these plans
-Use `AskUserQuestion` tool to ask if user wants to proceed with archiving these plans, select specific plans to archive or all completed plans only.
-Use `AskUserQuestion` tool to ask if user wants to delete permanently or move to the `.s/archive` directory.
+Ask if user wants to proceed with archiving these plans, select specific plans to archive or all completed plans only.
+Ask if user wants to delete permanently or move to the `.s/archive` directory.
 
 ### Step 4: Archive the plans
 Start archiving the plans based on the user's choice:
@@ -38,7 +38,7 @@ Start archiving the plans based on the user's choice:
 - Delete the plans permanently: `rm -rf .s/<plan-1> .s/<plan-2> ...`
 
 ### Step 5: Ask if user wants to commit the changes
-Use `AskUserQuestion` tool to ask if user wants to commit the changes with these options:
+Ask if user wants to commit the changes with these options:
 - Stage and commit the changes (Use `/git:cm` )
 - Commit and push the changes (Use `/git:cp` )
 - Nah, I'll do it later
@@ -51,8 +51,7 @@ After archiving the plans, provide summary:
 - Table of journal entries that are created (title, status, created date, LOC)
 
 ## Important Notes
-
-**IMPORTANT:** Only ask questions about genuine decision points - don't manufacture artificial choices.
-**IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
-**IMPORTANT:** In the last summary report, list any unresolved questions at the end, if any.
-**IMPORTANT:** Ensure token efficiency while maintaining high quality.
+- **IMPORTANT:** Only ask questions about genuine decision points - don't manufacture artificial choices.
+- **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
+- **IMPORTANT:** In the last summary report, list any unresolved questions at the end, if any.
+- **IMPORTANT:** Ensure token efficiency while maintaining high quality.

package/templates/repo/.github/prompts/ck-plan-ci.prompt.md

@@ -29,6 +29,7 @@ read the github actions logs, analyze and find the root causes of the issues, th
 **Output:**
 Provide at least 2 implementation approaches with clear trade-offs, and explain the pros and cons of each approach, and provide a recommended approach.
 
-**IMPORTANT:** Ask the user for confirmation before implementing.
-**IMPORTANT:** 
-**IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
+## Important Notes
+- **IMPORTANT:** Ask the user for confirmation before implementing.
+- **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
+- **IMPORTANT:** **Do not** start implementing.

package/templates/repo/.github/prompts/ck-plan-fast.prompt.md

@@ -59,9 +59,45 @@ Use  to:
 - Save the overview access point at `{plan-dir}.md`. Keep it generic, under 80 lines, and list each implementation phase with status and progress plus links to phase files.
 - For each phase, create `{plan-dir}/phase-XX-phase-name-here.md` containing the following sections in order: Context links (reference parent plan, dependencies, docs), Overview (date, description, priority, implementation status, review status), Key Insights, Requirements, Architecture, Related code files, Implementation Steps, Todo list, Success Criteria, Risk Assessment, Security Considerations, Next steps.
 
+## Clarification & Finalization Flow
+
+After creating the initial plan:
+
+1. **If questions exist** → List questions at the end of your response (max 3-5 questions)
+2. **After user answers** → Update `plan.md` with clarified requirements
+3. **Repeat** until no ambiguities remain
+4. **Finalize** → Confirm plan is complete and ready for implementation
+
+**Question format:**
+```
+## Questions before finalizing:
+1. [Question 1]?
+2. [Question 2]?
+...
+```
+
+## Next Steps Suggestion
+
+After plan is finalized, suggest the appropriate implementation command:
+
+| Task Type | Suggested Command |
+|-----------|-------------------|
+| Feature development | `/cook` or `/code` |
+| Bug fix | `/fix` |
+| Refactoring | `/refactor` |
+| Documentation | `/docs` |
+
+**Example output:**
+```
+✅ Plan finalized: {plan-dir}/plan.md
+
+Ready to implement? Run one of these:
+- `/cook` - Full-featured implementation with tests
+- `/code` - Quick implementation
+```
+
 ## Important Notes
 - **IMPORTANT:** Ensure token consumption efficiency while maintaining high quality.
-- **IMPORTANT:** 
 - **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
 - **IMPORTANT:** In reports, list any unresolved questions at the end, if any.
-- **IMPORTANT**: **Do not** start implementing.
+- **IMPORTANT:** **Do not** start implementing.

package/templates/repo/.github/prompts/ck-plan-hard.prompt.md

@@ -39,7 +39,7 @@ Check the `## Plan Context` section in the injected context:
 | `auto` | Automatically execute :validate {plan-path}` |
 | `off` | Skip validation step entirely |
 
-**If mode is `prompt`:** Use `AskUserQuestion` tool with options above.
+**If mode is `prompt`:** Ask user with options above.
 **If user chooses validation or mode is `auto`:** Execute :validate {plan-path}` SlashCommand.
 
 ## Output Requirements
@@ -81,9 +81,45 @@ Check the `## Plan Context` section in the injected context:
 - Save the overview access point at `{plan-dir}.md`. Keep it generic, under 80 lines, and list each implementation phase with status and progress plus links to phase files.
 - For each phase, create `{plan-dir}/phase-XX-phase-name-here.md` containing the following sections in order: Context links (reference parent plan, dependencies, docs), Overview (date, description, priority, implementation status, review status), Key Insights, Requirements, Architecture, Related code files, Implementation Steps, Todo list, Success Criteria, Risk Assessment, Security Considerations, Next steps.
 
+## Clarification & Finalization Flow
+
+After creating the initial plan:
+
+1. **If questions exist** → List questions at the end of your response (max 3-5 questions)
+2. **After user answers** → Update `plan.md` with clarified requirements
+3. **Repeat** until no ambiguities remain
+4. **Finalize** → Confirm plan is complete and ready for implementation
+
+**Question format:**
+```
+## Questions before finalizing:
+1. [Question 1]?
+2. [Question 2]?
+...
+```
+
+## Next Steps Suggestion
+
+After plan is finalized, suggest the appropriate implementation command:
+
+| Task Type | Suggested Command |
+|-----------|-------------------|
+| Feature development | `/cook` or `/code` |
+| Bug fix | `/fix` |
+| Refactoring | `/refactor` |
+| Documentation | `/docs` |
+
+**Example output:**
+```
+✅ Plan finalized: {plan-dir}/plan.md
+
+Ready to implement? Run one of these:
+- `/cook` - Full-featured implementation with tests
+- `/code` - Quick implementation
+```
+
 ## Important Notes
-**IMPORTANT:** 
-**IMPORTANT:** Ensure token efficiency while maintaining high quality.
-**IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
-**IMPORTANT:** In reports, list any unresolved questions at the end, if any.
-**IMPORTANT**: **Do not** start implementing.
+- **IMPORTANT:** Ensure token efficiency while maintaining high quality.
+- **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
+- **IMPORTANT:** In reports, list any unresolved questions at the end, if any.
+- **IMPORTANT:** **Do not** start implementing.

package/templates/repo/.github/prompts/ck-plan-parallel.prompt.md

@@ -31,7 +31,7 @@ ${input}
 | `auto` | Automatically execute :validate {plan-path}` |
 | `off` | Skip validation step entirely |
 
-**If mode is `prompt`:** Use `AskUserQuestion` tool with options above.
+**If mode is `prompt`:** Ask user with options above.
 **If user chooses validation or mode is `auto`:** Execute :validate {plan-path}` SlashCommand.
 
 ## Special Requirements for Parallel Execution
@@ -117,10 +117,43 @@ Phase 04: Integration Tests (depends on 01, 02, 03)
 - Execution strategy (e.g., "Phases 1-3 parallel, then Phase 4")
 - File ownership matrix (which phase owns which files)
 
+## Clarification & Finalization Flow
+
+After creating the initial plan:
+
+1. **If questions exist** → List questions at the end of your response (max 3-5 questions)
+2. **After user answers** → Update `plan.md` with clarified requirements
+3. **Repeat** until no ambiguities remain
+4. **Finalize** → Confirm plan is complete and ready for implementation
+
+**Question format:**
+```
+## Questions before finalizing:
+1. [Question 1]?
+2. [Question 2]?
+...
+```
+
+## Next Steps Suggestion
+
+After plan is finalized, suggest the parallel execution command:
+
+**Example output:**
+```
+✅ Plan finalized: {plan-dir}/plan.md
+
+Parallel execution strategy:
+- Phases 1-3: Can run in parallel
+- Phase 4: Depends on 1-3
+
+Ready to implement? Run:
+- `/cook:parallel` - Execute phases in parallel
+- `/cook` - Execute phases sequentially
+```
+
 ## Important Notes
-**IMPORTANT:** 
-**IMPORTANT:** Ensure token efficiency while maintaining high quality.
-**IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
-**IMPORTANT:** In reports, list any unresolved questions at the end, if any.
-**IMPORTANT:** Do not start implementing.
-**IMPORTANT:** Each phase MUST have exclusive file ownership - no file can be modified by multiple phases.
+- **IMPORTANT:** Ensure token efficiency while maintaining high quality.
+- **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
+- **IMPORTANT:** In reports, list any unresolved questions at the end, if any.
+- **IMPORTANT:** Do not start implementing.
+- **IMPORTANT:** Each phase MUST have exclusive file ownership - no file can be modified by multiple phases.

package/templates/repo/.github/prompts/ck-plan-two.prompt.md

@@ -35,9 +35,44 @@ create 2 detailed implementation plans for this following task:
   ---
   ```
 
+## Clarification & Finalization Flow
+
+After creating the initial plans:
+
+1. **If questions exist** → List questions at the end of your response (max 3-5 questions)
+2. **After user chooses approach** → Update selected `plan.md` with clarified requirements
+3. **Finalize** → Confirm plan is complete and ready for implementation
+
+**Question format:**
+```
+## Questions before finalizing:
+1. Which approach do you prefer? (A or B)
+2. [Other questions]?
+...
+```
+
+## Next Steps Suggestion
+
+After plan is finalized, suggest the appropriate implementation command:
+
+| Task Type | Suggested Command |
+|-----------|-------------------|
+| Feature development | `/cook` or `/code` |
+| Bug fix | `/fix` |
+| Refactoring | `/refactor` |
+| Documentation | `/docs` |
+
+**Example output:**
+```
+✅ Plan finalized: {plan-dir}/plan.md (Approach A selected)
+
+Ready to implement? Run one of these:
+- `/cook` - Full-featured implementation with tests
+- `/code` - Quick implementation
+```
+
 ## Important Notes
-**IMPORTANT:** 
-**IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
-**IMPORTANT:** Ensure token efficiency while maintaining high quality.
-**IMPORTANT:** In reports, list any unresolved questions at the end, if any.
-**IMPORTANT**: **Do not** start implementing.
+- **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
+- **IMPORTANT:** Ensure token efficiency while maintaining high quality.
+- **IMPORTANT:** In reports, list any unresolved questions at the end, if any.
+- **IMPORTANT:** **Do not** start implementing.

package/templates/repo/.github/prompts/ck-plan-validate.prompt.md

@@ -75,7 +75,7 @@ Options:
 
 ### Step 4: Interview User
 
-Use `AskUserQuestion` tool to present questions.
+Present questions to user.
 
 **Rules:**
 - Use question count from `## Plan Context` → `Validation: mode=X, questions=MIN-MAX`
@@ -112,7 +112,6 @@ After validation completes, provide summary:
 - Recommendation: proceed to implementation or revise plan first
 
 ## Important Notes
-
-**IMPORTANT:** Only ask questions about genuine decision points - don't manufacture artificial choices.
-**IMPORTANT:** If plan is simple with few decisions, it's okay to ask fewer than min questions.
-**IMPORTANT:** Prioritize questions that could change implementation significantly.
+- **IMPORTANT:** Only ask questions about genuine decision points - don't manufacture artificial choices.
+- **IMPORTANT:** If plan is simple with few decisions, it's okay to ask fewer than min questions.
+- **IMPORTANT:** Prioritize questions that could change implementation significantly.

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

@@ -1,29 +1,80 @@
----
-agent: 'agent'
-description: 'Intelligent plan creation with prompt enhancement'
-tools: ['search/codebase', 'search/changes', 'web/fetch', 'read/problems']
----
-
-## Your mission
-<task>
-${input}
-</task>
-
-## Pre-Creation Check (Active vs Suggested Plan Detection)
-
-Check the `## Plan Context` section in the injected context:
-- If "Plan:" shows a path → Active plan exists. Ask user: "Active plan found: {path}. Continue with this? [Y/n]"
-- If "Suggested:" shows a path → Branch-matched plan hint only. Ask user if they want to activate it or create new.
-- If "Plan: none" → Proceed to create new plan using naming pattern from `## Naming` section.
-
-## Workflow
-- Analyze the given task and use `AskUserQuestion` tool to ask for more details if needed.
-- Decide to use :fast` or :hard` SlashCommands based on the complexity.
-- Execute SlashCommand: :fast <detailed-instructions-prompt>` or :hard <detailed-instructions-prompt>`
- Note: `detailed-instructions-prompt` is **an enhanced prompt** that describes the task in detail based on the provided task description.
-
-## Important Notes
-**IMPORTANT:** 
-**IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
-**IMPORTANT:** Ensure token efficiency while maintaining high quality.
-**IMPORTANT:** In reports, list any unresolved questions at the end, if any.
-**IMPORTANT**: **Do not** start implementing.
+---
+agent: 'agent'
+description: 'Intelligent plan creation with prompt enhancement'
+tools: ['search/codebase', 'search/changes', 'web/fetch', 'read/problems']
+---
+
+## Your mission
+<task>
+${input}
+</task>
+
+## Pre-Creation Check (Active vs Suggested Plan Detection)
+
+Check the `## Plan Context` section in the injected context:
+- If "Plan:" shows a path → Active plan exists. Ask user: "Active plan found: {path}. Continue with this? [Y/n]"
+- If "Suggested:" shows a path → Branch-matched plan hint only. Ask user if they want to activate it or create new.
+- If "Plan: none" → Proceed to create new plan using naming pattern from `## Naming` section.
+
+## Workflow
+- Analyze the given task and ask user for more details if needed.
+- Decide complexity:
+  - **Simple task** (clear scope, no research needed) → Use `/plan:fast`
+  - **Complex task** (needs research, multiple aspects) → Use `/plan:hard`
+- Execute the chosen SlashCommand with an **enhanced detailed prompt**:
+  - `/plan:fast <detailed-instructions-prompt>`
+  - `/plan:hard <detailed-instructions-prompt>`
+
+**Note:** The `detailed-instructions-prompt` must describe the task in detail based on user's input.
+
+## Output
+The output MUST be markdown plan files saved to `plans/` directory:
+```
+{plan-dir}/
+├── plan.md              ← Main plan with YAML frontmatter
+├── phase-XX-*.md        ← Implementation phases
+└── reports/             ← Any analysis reports
+```
+
+## Clarification & Finalization Flow
+
+After creating the initial plan:
+
+1. **If questions exist** → List questions at the end of your response (max 3-5 questions)
+2. **After user answers** → Update `plan.md` with clarified requirements
+3. **Repeat** until no ambiguities remain
+4. **Finalize** → Confirm plan is complete and ready for implementation
+
+**Question format:**
+```
+## Questions before finalizing:
+1. [Question 1]?
+2. [Question 2]?
+...
+```
+
+## Next Steps Suggestion
+
+After plan is finalized, suggest the appropriate implementation command:
+
+| Task Type | Suggested Command |
+|-----------|-------------------|
+| Feature development | `/cook` or `/code` |
+| Bug fix | `/fix` |
+| Refactoring | `/refactor` |
+| Documentation | `/docs` |
+
+**Example output:**
+```
+✅ Plan finalized: {plan-dir}/plan.md
+
+Ready to implement? Run one of these:
+- `/cook` - Full-featured implementation with tests
+- `/code` - Quick implementation
+```
+
+## Important Notes
+- **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
+- **IMPORTANT:** Ensure token efficiency while maintaining high quality.
+- **IMPORTANT:** In reports, list any unresolved questions at the end, if any.
+- **IMPORTANT:** **Do not** start implementing.

package/templates/repo/.github/prompts/ck-skill-add.prompt.md

@@ -5,7 +5,7 @@ tools: ['search/codebase', 'search/changes', 'web/fetch', 'read/problems']
 ---
 
 Think harder.
-Use `skill-creator` and `claude-code` skills.
+Use `skill-creator` skill.
 
 ## Arguments
 $1: skill name (required, default: "")
@@ -24,13 +24,13 @@ $2
 Base on the requirements:
 - Always keep in mind that `SKILL.md` and reference files should be token consumption efficient, so that **progressive disclosure** can be leveraged at best.
 - `SKILL.md` is always short and concise, straight to the point, treat it as a quick reference guide.
-- If you're given nothing, use `AskUserQuestion` tool for clarifications and  to research about the topic.
+- If you're given nothing, ask for clarifications and  to research about the topic.
 - If you're given an URL, it's documentation page, explore every internal link and .
 - If you receive a lot of URLs, use multiple s to explore them , .
 - If you receive a lot of files, use multiple s to explore them , .
 - If you're given a Github URL, use [](https://repomix.com/guide/usage) command to summarize ([install it](https://repomix.com/guide/installation) if needed) and spawn multiple s to explore it , .
 
 **IMPORTANT:**
-- Skills are not documentation, they are practical instructions for Claude Code to use the tools, packages, plugins or APIs to achieve the tasks.
-- Each skill teaches Claude how to perform a specific development task, not what a tool does.
-- Claude Code can activate multiple skills automatically to achieve the user's request.
+- Skills are not documentation, they are practical instructions for GitHub Copilot to use the tools, packages, plugins or APIs to achieve the tasks.
+- Each skill teaches GitHub Copilot how to perform a specific development task, not what a tool does.
+- GitHub Copilot can activate multiple skills automatically to achieve the user's request.

package/templates/repo/.github/prompts/ck-skill-create.prompt.md

@@ -5,7 +5,7 @@ tools: ['search/codebase', 'search/changes', 'web/fetch', 'read/problems']
 ---
 
 Ultrathink.
-Use `skill-creator` and `claude-code` skills.
+Use `skill-creator` skill.
 
 ## Your mission
 Create a new skill in  directory.
@@ -17,13 +17,13 @@ Create a new skill in  directory.
 Base on the requirements:
 - Always keep in mind that `SKILL.md` and reference files should be token consumption efficient, so that **progressive disclosure** can be leveraged at best.
 - `SKILL.md` is always short and concise, straight to the point, treat it as a quick reference guide.
-- If you're given nothing, use `AskUserQuestion` tool for clarifications and  to research about the topic.
+- If you're given nothing, ask for clarifications and  to research about the topic.
 - If you're given an URL, it's documentation page, explore every internal link and .
 - If you receive a lot of URLs, use multiple s to explore them , .
 - If you receive a lot of files, use multiple s to explore them , .
 - If you're given a Github URL, use [](https://repomix.com/guide/usage) command to summarize ([install it](https://repomix.com/guide/installation) if needed) and spawn multiple s to explore it , .
 
 **IMPORTANT:**
-- Skills are not documentation, they are practical instructions for Claude Code to use the tools, packages, plugins or APIs to achieve the tasks.
-- Each skill teaches Claude how to perform a specific development task, not what a tool does.
-- Claude Code can activate multiple skills automatically to achieve the user's request.
+- Skills are not documentation, they are practical instructions for GitHub Copilot to use the tools, packages, plugins or APIs to achieve the tasks.
+- Each skill teaches GitHub Copilot how to perform a specific development task, not what a tool does.
+- GitHub Copilot can activate multiple skills automatically to achieve the user's request.

package/templates/repo/.github/prompts/ck-skill-fix-logs.prompt.md

@@ -5,7 +5,7 @@ tools: ['search/codebase', 'search/changes', 'web/fetch', 'read/problems', 'read
 ---
 
 Think harder.
-Use `skill-creator` and `claude-code` skills.
+Use `skill-creator` skill.
 
 ## Your mission
 Fix the agent skill based on the current `logs.txt` file (in the project root directory).
@@ -15,7 +15,7 @@ Fix the agent skill based on the current `logs.txt` file (in the project root di
 
 ## Rules of Skill Fixing:
 Base on the requirements:
-- If you're given nothing, use `AskUserQuestion` tool for clarifications and  to research about the topic.
+- If you're given nothing, ask for clarifications and  to research about the topic.
 - If you're given an URL, it's documentation page, explore every internal link and .
 - If you receive a lot of URLs, use multiple s to explore them , .
 - If you receive a lot of files, use multiple s to explore them , .

package/templates/repo/.github/prompts/ck-skill-optimize-auto.prompt.md

@@ -5,21 +5,21 @@ tools: ['search/codebase', 'search/changes', 'web/fetch', 'read/problems']
 ---
 
 Think harder.
-Use `skill-creator` and `claude-code` skills.
+Use `skill-creator` skill.
 
 ## Arguments
 SKILL: $1 (default: `*`)
 PROMPT: $2 (default: empty)
 
 ## Your mission
-Optimize an existing skill in  directory. 
+Optimize an existing skill in  directory.
 Always keep in mind that `SKILL.md` and reference files should be token consumption efficient, so that **progressive disclosure** can be leveraged at best.
 `SKILL.md` is always short and concise, straight to the point, treat it as a quick reference guide.
 
 **IMPORTANT:**
-- Skills are not documentation, they are practical instructions for Claude Code to use the tools, packages, plugins or APIs to achieve the tasks.
-- Each skill teaches Claude how to perform a specific development task, not what a tool does.
-- Claude Code can activate multiple skills automatically to achieve the user's request.
+- Skills are not documentation, they are practical instructions for GitHub Copilot to use the tools, packages, plugins or APIs to achieve the tasks.
+- Each skill teaches GitHub Copilot how to perform a specific development task, not what a tool does.
+- GitHub Copilot can activate multiple skills automatically to achieve the user's request.
 
 ## Additional instructions
 <additional-instructions>$PROMPT</additional-instructions>

package/templates/repo/.github/prompts/ck-skill-optimize.prompt.md

@@ -5,14 +5,14 @@ tools: ['search/codebase', 'search/changes', 'web/fetch', 'read/problems']
 ---
 
 Think harder.
-Use `skill-creator` and `claude-code` skills.
+Use `skill-creator` skill.
 
 ## Arguments
 SKILL: $1 (default: `*`)
 PROMPT: $2 (default: empty)
 
 ## Your mission
-Propose a plan to optimize an existing skill in  directory. 
+Propose a plan to optimize an existing skill in  directory.
 When you finish, ask user to review your plan:
 - If the user approve: Write down a plan follow "Output Requirements", then ask user if they want to start implementing.
 - If the user reject: Revise the plan or ask more questions to clarify more about the user's request (ask one question at the time), then repeat the review process.
@@ -29,6 +29,6 @@ An output implementation plan must also follow the progressive disclosure struct
 - For each phase, add `phase-XX-phase-name.md` files containing sections (Context links, Overview with date/priority/statuses, Key Insights, Requirements, Architecture, Related code files, Implementation Steps, Todo list, Success Criteria, Risk Assessment, Security Considerations, Next steps).
 
 **IMPORTANT:**
-- Skills are not documentation, they are practical instructions for Claude Code to use the tools, packages, plugins or APIs to achieve the tasks.
-- Each skill teaches Claude how to perform a specific development task, not what a tool does.
-- Claude Code can activate multiple skills automatically to achieve the user's request.
+- Skills are not documentation, they are practical instructions for GitHub Copilot to use the tools, packages, plugins or APIs to achieve the tasks.
+- Each skill teaches GitHub Copilot how to perform a specific development task, not what a tool does.
+- GitHub Copilot can activate multiple skills automatically to achieve the user's request.

package/templates/repo/.github/prompts/ck-skill-plan.prompt.md

@@ -5,17 +5,17 @@ tools: ['search/codebase', 'search/changes', 'web/fetch', 'read/problems']
 ---
 
 Think harder.
-First: Activate `skill-creator` and `claude-code` skills.
+First: Activate `skill-creator` skill.
 
 Employ `sequential-thinking` or `problem-solving` skills for complex problem-solving that requires structured analysis
-Finally, when creating a plan, 
+Finally, when creating a plan,
 
 ## Arguments
 SKILL: $1 (default: `*`)
 PROMPT: $2 (default: empty)
 
 ## Your mission
-Propose a plan to create a new skill in  directory. 
+Propose a plan to create a new skill in  directory.
 When you finish, ask user to review your plan:
 - If the user approve: Write down a plan follow "Output Requirements", then ask user if they want to start implementing.
 - If the user reject: Revise the plan or ask more questions to clarify more about the user's request (ask one question at the time), then repeat the review process.
@@ -39,8 +39,8 @@ An output implementation plan must also follow the progressive disclosure struct
 - For each phase, add `phase-XX-phase-name.md` files containing sections (Context links, Overview with date/priority/statuses, Key Insights, Requirements, Architecture, Related code files, Implementation Steps, Todo list, Success Criteria, Risk Assessment, Security Considerations, Next steps).
 
 **IMPORTANT:**
-- Analyze the given task and use `AskUserQuestion` tool to ask for more details if needed.
+- Analyze the given task and ask for more details if needed.
 - Ensure token consumption efficiency while maintaining high quality.
-- Skills are not documentation, they are practical instructions for Claude Code to use the tools, packages, plugins or APIs to achieve the tasks.
-- Each skill teaches Claude how to perform a specific development task, not what a tool does.
-- Claude Code can activate multiple skills automatically to achieve the user's request.
+- Skills are not documentation, they are practical instructions for GitHub Copilot to use the tools, packages, plugins or APIs to achieve the tasks.
+- Each skill teaches GitHub Copilot how to perform a specific development task, not what a tool does.
+- GitHub Copilot can activate multiple skills automatically to achieve the user's request.

package/templates/repo/.github/prompts/ck-test-ui.prompt.md

@@ -78,7 +78,7 @@ node screenshot.js --url https://example.com/settings --output settings.png --cl
 - Use `ai-multimodal` to analyze all screenshots and visual elements.
 - Generate a comprehensive report in Markdown format, embedding all screenshots directly in the report.
 - Finally respond to the user with a concise summary of findings and recommendations.
-- Use `AskUserQuestion` tool to ask if user wants to preview the report with `/preview` .
+- Ask if user wants to preview the report with `/preview` .
 
 ## Output Requirements
 How to write reports: