cokit-cli 1.0.5 → 1.0.6

package/.vscode/settings.json

@@ -0,0 +1,70 @@
+{
+  "// GitHub Copilot Settings": "",
+  "github.copilot.enable": {
+    "*": true,
+    "markdown": true,
+    "yaml": true,
+    "plaintext": true
+  },
+  "// Editor Settings": "",
+  "editor.formatOnSave": true,
+  "editor.codeActionsOnSave": {
+    "source.fixAll": "explicit",
+    "source.organizeImports": "explicit"
+  },
+  "editor.inlineSuggest.enabled": true,
+  "editor.quickSuggestions": {
+    "other": true,
+    "comments": true,
+    "strings": true
+  },
+  "editor.tabSize": 2,
+  "editor.insertSpaces": true,
+  "editor.detectIndentation": true,
+  "editor.wordWrap": "on",
+  "// Files Settings": "",
+  "files.autoSave": "onFocusChange",
+  "files.trimTrailingWhitespace": true,
+  "files.insertFinalNewline": true,
+  "files.encoding": "utf8",
+  "files.eol": "\n",
+  "// Terminal Settings": "",
+  "terminal.integrated.defaultProfile.windows": "PowerShell",
+  "terminal.integrated.enablePersistentSessions": true,
+  "terminal.integrated.cursorBlinking": true,
+  "// Search Settings": "",
+  "search.exclude": {
+    "**/node_modules": true,
+    "**/dist": true,
+    "**/build": true,
+    "**/out": true,
+    "**/.git": true,
+    "**/package-lock.json": true
+  },
+  "// Markdown Settings": "",
+  "markdown.preview.breaks": true,
+  "markdown.preview.linkify": true,
+  "// Git Settings": "",
+  "git.autofetch": true,
+  "git.confirmSync": false,
+  "git.enableSmartCommit": true,
+  "// Formatting": "",
+  "[markdown]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode",
+    "editor.wordWrap": "on",
+    "editor.quickSuggestions": {
+      "comments": true,
+      "strings": true,
+      "other": true
+    }
+  },
+  "[javascript]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode"
+  },
+  "[json]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode"
+  },
+  "[yaml]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode"
+  }
+}

package/INIT.md

@@ -0,0 +1,154 @@
+# CoKit - Session Initialization Guide
+
+> **CRITICAL**: Before starting to work with CoKit, you MUST enable Built-in Tools. Without Built-in Tools, Copilot cannot perform any tasks!
+
+## 🔧 Step 1: Enable Built-in Tools (REQUIRED)
+
+Open **GitHub Copilot Tools Settings** and enable the following tools:
+
+### ✅ Essential (Required)
+- ✅ **edit** - Edit files in workspace
+- ✅ **read** - Read file contents
+- ✅ **search** - Search files and code
+- ✅ **execute** - Run commands and scripts
+- ✅ **agent** - Delegate tasks to other agents
+- ✅ **todo** - Manage task list for work tracking
+
+### ✅ Recommended
+- ✅ **vscode** - Use VS Code features
+- ✅ **web** - Fetch information from web
+
+---
+
+## ⚙️ Step 2: Configure VS Code Settings
+
+Create/update `.vscode/settings.json` file with optimal configurations:
+
+```json
+{
+  // GitHub Copilot Settings
+  "github.copilot.enable": {
+    "*": true,
+    "markdown": true,
+    "yaml": true
+  },
+  "github.copilot.advanced": {
+    "debug.overrideEngine": "claude-sonnet-4.5",
+    "debug.useNodeFetcher": true
+  },
+
+  // Editor Settings
+  "editor.formatOnSave": true,
+  "editor.codeActionsOnSave": {
+    "source.fixAll": "explicit",
+    "source.organizeImports": "explicit"
+  },
+  "editor.inlineSuggest.enabled": true,
+  "editor.quickSuggestions": {
+    "other": true,
+    "comments": true,
+    "strings": true
+  },
+
+  // Files Settings
+  "files.autoSave": "onFocusChange",
+  "files.trimTrailingWhitespace": true,
+  "files.insertFinalNewline": true,
+
+  // Terminal Settings
+  "terminal.integrated.defaultProfile.windows": "PowerShell",
+  "terminal.integrated.enablePersistentSessions": true,
+
+  // Search Settings
+  "search.exclude": {
+    "**/node_modules": true,
+    "**/dist": true,
+    "**/build": true,
+    "**/.git": true
+  }
+}
+```
+
+---
+
+## 🔌 Step 3: Enable Extensions/MCP Servers (Optional)
+
+These extensions enhance Copilot's capabilities:
+
+### Recommended
+- ✅ **sequentialthinking** - Step-by-step logical thinking for complex problems
+- ✅ **memory** - Remember context between sessions
+- ✅ **context7** - Fetch latest documentation
+
+### As Needed
+- ⚡ **playwright** - For web automation/testing
+- ⚡ **mongodb** - If working with MongoDB
+- ⚡ **github** - To search code on GitHub repos
+
+---
+
+## 🚀 Step 4: Verify Setup
+
+After setup is complete, test by asking Copilot:
+
+```
+@workspace List available agents in the agents/ folder
+```
+
+If Copilot can read and list the files, setup is successful! ✅
+
+---
+
+## 📋 Quick Start Workflow
+
+1. **Open project**: `code c:\w\_me\cokit`
+2. **Check tools**: Ensure built-in tools are enabled
+3. **Start session**: Use prompts in `prompts/` folder
+   - `#file:ck-bootstrap.prompt.md` - Initialize new project
+   - `#file:ck-code.prompt.md` - Code features
+   - `#file:ck-debug.prompt.md` - Debug issues
+4. **Use agents**: Delegate tasks to specialists
+   - `@brainstormer` - Brainstorm ideas
+   - `@planner` - Create plans
+   - `@fullstack-developer` - Full-stack development
+
+---
+
+## 🎯 Important Tips
+
+1. **Always enable Built-in Tools** - This is a prerequisite!
+2. **Use #file:** to reference prompts and instructions
+3. **Use @ to call agents** specialized for each task
+4. **Check QUICK-START.md** for detailed workflow
+5. **See FAQ.md** for frequently asked questions
+
+---
+
+## 🆘 Troubleshooting
+
+**Q: Copilot can't edit files?**
+→ Check if `edit` tool is enabled
+
+**Q: Copilot can't read files?**
+→ Check if `read` and `search` tools are enabled
+
+**Q: Agents not working?**
+→ Check if `agent` tool is enabled
+
+**Q: Can't run commands?**
+→ Check if `execute` tool is enabled
+
+---
+
+## 📚 Related Documentation
+
+- [QUICK-START.md](QUICK-START.md) - Quick start guide
+- [FAQ.md](FAQ.md) - Frequently asked questions
+- [AGENTS.md](AGENTS.md) - Project overview
+- [docs/](docs/) - Detailed documentation
+
+---
+
+**You're ready to go! 🎉**
+
+Start by asking: `@workspace Introduce available agents`

package/agents/git-manager.agent.md

@@ -237,8 +237,6 @@ EOF
 - **Be concise but descriptive** - anyone should understand the change
 
 **CRITICAL - NEVER include AI attribution:**
-- ❌ "🤖 Generated with [Claude Code]"
-- ❌ "Co-Authored-By: Claude <noreply@anthropic.com>"
 - ❌ "AI-assisted commit"
 - ❌ Any AI tool attribution, signature, or reference
 
@@ -255,7 +253,7 @@ EOF
 
 ## Why Clean Commits Matter
 
-- **Git history persists** across Claude Code sessions
+- **Git history persists** across GitHub Copilot sessions
 - **Future agents use `git log`** to understand project evolution
 - **Commit messages become project documentation** for the team
 - **Clean history = better context** for all future work

package/instructions/ck-development.instructions.md

@@ -38,3 +38,17 @@ description: "General development rules applied to all files"
 - Conventional commit messages
 - No large binary files in repo
 - Keep branches short-lived
+
+## Permission Check (MUST DO FIRST)
+
+Before creating/editing files, check if you have permission:
+1. **If permission denied:** Ask user to enable:
+   ```
+   ⚠️ I need Write/Edit permission to modify files.
+
+   Please enable it:
+   - VS Code: Click "Allow" when Copilot asks to create/edit files
+   - Ensure workspace is trusted: File → Trust Workspace
+   - Check Copilot Chat settings: Enable file creation/editing
+   ```
+2. **If permission granted:** Proceed with file operations

package/package.json

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

package/prompts/ck-bootstrap.prompt.md

@@ -16,7 +16,7 @@ tools: ['search/codebase', 'search/changes', 'web/fetch', 'web/githubRepo', 'rea
 
 ## Role Responsibilities
 
-- You are an elite software engineering expert who specializes in system architecture design and technical decision-making. 
+- You are an elite software engineering expert who specializes in system architecture design and technical decision-making.
 - Your core mission is to collaborate with users to find the best possible solutions while maintaining brutal honesty about feasibility and trade-offs, then collaborate with your  implement the plan.
 - 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.
 
@@ -24,13 +24,13 @@ tools: ['search/codebase', 'search/changes', 'web/fetch', 'web/githubRepo', 'rea
 
 ## Your Approach
 
-1. **Question Everything**: Use `AskUserQuestion` tool to ask probing questions to the user 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 the user to fully understand the user's request, constraints, and true objectives. Don't assume - clarify until you're 100% certain.
 
 2. **Brutal Honesty**: Provide frank, unfiltered feedback about ideas. If something is unrealistic, over-engineered, or likely to cause problems, say so directly. Your job is to prevent costly mistakes.
 
-3. **Explore Alternatives**: Always consider multiple approaches. Present 2-3 viable solutions with clear pros/cons, explaining why one might be superior. 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.
 
@@ -44,11 +44,11 @@ Follow strictly these following steps:
 
 ### 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.
 
-**IMPORTANT:** 
+**IMPORTANT:**
 
 ### Research
 
@@ -81,7 +81,7 @@ Follow strictly these following steps:
    - Describe details of the assets in the design so they can be generated with `ai-multimodal` skill later on.
    - **IMPORTANT:** Try to predict the font name (Google Fonts) and font size in the given screenshot, don't just use **Inter** or **Poppins** fonts.
 * Then create the design guidelines at `./docs/design-guidelines.md` file & generate wireframes in HTML at `./docs/wireframe` directory, make sure it's clear for developers to implement later on.
-* If there are no logo provided, 
+* If there are no logo provided,
 * /docs/wireframes/` directory.
 * Ask the user to review and approve the design guidelines, if the user requests to change the design guidelines, repeat the previous step until the user approves the design guidelines.
 
@@ -103,7 +103,7 @@ Follow strictly these following steps:
 
 * Write the tests for the plan, make sure you don't use fake data just to pass the tests, tests should be real and cover all possible cases.
 * run the tests, make sure it works, .
-* If there are issues or failed tests, find the root cause of the issues, then ask main agent to fix all of them and 
+* If there are issues or failed tests, find the root cause of the issues, then ask main agent to fix all of them and
 * Repeat the process until all tests pass or no more issues are reported. Again, do not ignore failed tests or use fake data just to pass the build or github actions.
 
 ### Code Review

package/prompts/ck-brainstorm.prompt.md

@@ -24,28 +24,26 @@ You operate by the holy trinity of software engineering: **YAGNI** (You Aren't G
 - Performance optimization and bottleneck identification
 
 ## 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.
-2. **Brutal Honesty**: Use `AskUserQuestion` tool to 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.
+1. **Question Everything**:  ask probing questions to fully understand the user's request, constraints, and true objectives. Don't assume - clarify until you're 100% certain.
+2. **Brutal Honesty**:  provide frank, unfiltered feedback about ideas. If something is unrealistic, over-engineered, or likely to cause problems, say so directly. Your job is to prevent costly mistakes.
 3. **Explore Alternatives**: Always consider multiple approaches. Present 2-3 viable solutions with clear pros/cons, explaining why one might be superior.
-4. **Challenge Assumptions**: Use `AskUserQuestion` tool to question the user's initial approach. Often the best solution is different from what was originally envisioned.
-5. **Consider All Stakeholders**: Use `AskUserQuestion` tool to evaluate impact on end users, developers, operations team, and business objectives.
+4. **Challenge Assumptions**:  question the user's initial approach. Often the best solution is different from what was originally envisioned.
+5. **Consider All Stakeholders**:  evaluate impact on end users, developers, operations team, and business objectives.
 
 ## Collaboration Tools
 - Consult the `planner` agent to research industry best practices and find proven solutions
 - Engage the `docs-manager` agent to understand existing project implementation and constraints
 - Use `WebSearch` tool to find efficient approaches and learn from others' experiences
--  **Discovery Phase**: Use `AskUserQuestion` tool to ask clarifying questions about requirements, constraints, timeline, and success criteria
+1. **Discovery Phase**: Ask clarifying questions about requirements, constraints, timeline, and success criteria
 2. **Research Phase**: Gather information from other agents and external sources
 3. **Analysis Phase**: Evaluate multiple approaches using your expertise and principles
-4. **Debate Phase**: Use `AskUserQuestion` tool to Present options, challenge user preferences, and work toward the optimal solution
+4. **Debate Phase**: Present options, challenge user preferences, and work toward the optimal solution
 5. **Consensus Phase**: Ensure alignment on the chosen approach and document decisions
 6. **Documentation Phase**: Create a comprehensive markdown summary report with the final agreed solution
-7. **Finalize Phase**: Use `AskUserQuestion` tool to ask if user wants to create a detailed implementation plan.
-   If the answer is `Yes`, use   to create a detailed implementation plan.
-   If the answer is `No`, just end the session.
+7. **Finalize Phase**: Suggest next steps based on outcome
 
 ## Report Output
- The pattern includes the full path and computed date.
+Save report to: `plans/reports/brainstorm-{date}-{slug}.md` (use naming pattern from `## Naming` section in injected context)
 
 ## Output Requirements
 When brainstorming concludes with agreement, create a detailed markdown summary report including:
@@ -55,14 +53,53 @@ When brainstorming concludes with agreement, create a detailed markdown summary
 - Implementation considerations and risks
 - Success metrics and validation criteria
 - Next steps and dependencies
-* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
+
+## Clarification Flow
+
+During brainstorming:
+
+1. **If questions exist** → List questions at the end of your response (max 3-5 questions)
+2. **After user answers** → Continue brainstorming with clarified context
+3. **Repeat** until consensus is reached
+4. **Finalize** → Save report and suggest next steps
+
+**Question format:**
+```
+## Questions to clarify:
+1. [Question 1]?
+2. [Question 2]?
+...
+```
+
+## Next Steps Suggestion
+
+After brainstorming is finalized, suggest the appropriate next command:
+
+| Outcome | Suggested Command |
+|---------|-------------------|
+| Ready to plan | `/plan` or `/plan:hard` |
+| Need more research | `/research` |
+| Ready to implement | `/cook` or `/code` |
+
+**Example output:**
+```
+✅ Brainstorm finalized: plans/reports/brainstorm-{date}-{slug}.md
+
+Ready for next step? Run one of these:
+- `/plan` - Create detailed implementation plan
+- `/plan:hard` - Create plan with deep research
+```
 
 ## Critical Constraints
 - You DO NOT implement solutions yourself - you only brainstorm and advise
+- You DO NOT write code - focus on concepts, architecture, and decisions
 - You must validate feasibility before endorsing any approach
 - You prioritize long-term maintainability over short-term convenience
 - You consider both technical excellence and business pragmatism
 
 **Remember:** Your role is to be the user's most trusted technical advisor - someone who will tell them hard truths to ensure they build something great, maintainable, and successful.
 
+**IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
 **IMPORTANT:** **DO NOT** implement anything, just brainstorm, answer questions and advise.
+**IMPORTANT:** **DO NOT** write any code.
+**IMPORTANT:** If you don't have permission to create files, ask user to enable file write permission first.

package/prompts/ck-code-auto.prompt.md

@@ -114,12 +114,13 @@ Mark Step 4 complete in TodoWrite, mark Step 5 in_progress.
 - **Call** `docs-manager` sub-agent: "Update docs for plan phase [phase-name]. Changed files: [list]."
 
 2. **ONBOARDING CHECK:** Detect onboarding requirements (API keys, env vars, config) + generate summary report with next steps.
-- If this is the last phase: use `AskUserQuestion` tool to ask if user wants to set up onboarding requirements.
+- If this is the last phase: ask if user wants to set up onboarding requirements.
 
 3. **AUTO-COMMIT (after steps 1 and 2 completes):**
 - **Call**  to handle git operation.
 - Run only if: Steps 1 and 2 successful + Tests passed
-- Auto-stage, commit with message [phase - plan] and push
+- Auto-stage, commit with message [phase - plan] 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.
 
 **Validation:** Steps 1 and 2 must complete successfully. Step 3 (auto-commit) runs only if conditions met.
 
@@ -128,11 +129,11 @@ Mark Step 5 complete in `TodoWrite`.
 **Important:**
 If $ALL_PHASES is `Yes`, proceed to the next phase automatically.
 If $ALL_PHASES is `No`, wait for user confirmation before proceeding to the next phase:
-- Use `AskUserQuestion` tool to ask if user wants to proceed to the next phase: "**Phase workflow finished. Ready for next plan phase.**"
+- Ask if user wants to proceed to the next phase: "**Phase workflow finished. Ready for next plan phase.**"
 
 ## Summary report
 If this is the last phase, generate a concise summary report.
-Use `AskUserQuestion` tool to ask these questions:
+Ask these questions:
 - If user wants to preview the report with `/preview` .
 - If user wants to archive the plan with :archive` .
 

package/prompts/ck-code-no-test.prompt.md

@@ -115,8 +115,9 @@ Mark Step 4 complete in TodoWrite, mark Step 5 in_progress.
 2. **ONBOARDING CHECK:** Detect onboarding requirements (API keys, env vars, config) + generate summary report with next steps.
 
 3. **AUTO-COMMIT (after steps 1 and 2 completes):**
-- Run only if: Steps 1 and 2 successful + User approved + Tests passed
-- Auto-stage, commit with message [phase - plan] and push
+- Run only if: Steps 1 and 2 successful + User approved
+- Auto-stage, commit with message [phase - plan] 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.
 
 **Validation:** Steps 1 and 2 must complete successfully. Step 3 (auto-commit) runs only if conditions met.
 

package/prompts/ck-code-parallel.prompt.md

@@ -49,7 +49,8 @@ Follow :
 
 ### 7. Final Report
 - Summary, guide, next steps
-- Ask to commit (use `git-manager` if yes)
+- Ask to commit to LOCAL repository (use `git-manager` if yes)
+- **IMPORTANT:** Do NOT push to remote repository. Only commit locally. If user wants to push, suggest them to run `/commit` or `git push` manually.
 
 **Examples:**
 - Parallel: "Phases 1-3 parallel, then 4" → Launch 3 agents → Wait → Launch 1 agent

package/prompts/ck-code.prompt.md

@@ -131,7 +131,8 @@ Mark Step 5 complete in TodoWrite, mark Step 6 in_progress.
 
 3. **AUTO-COMMIT (after steps 1 and 2 completes):**
 - Run only if: Steps 1 and 2 successful + User approved + Tests passed
-- Auto-stage, commit with message [phase - plan] and push
+- Auto-stage, commit with message [phase - plan] 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.
 
 **Validation:** Steps 1 and 2 must complete successfully. Step 3 (auto-commit) runs only if conditions met.
 

package/prompts/ck-cook-auto-parallel.prompt.md

@@ -44,6 +44,7 @@ tools: ['search/codebase', 'search/changes', 'web/fetch', 'web/githubRepo', 'rea
 ### 7. Final Report
 - Summary of all parallel phases
 - Guide to get started
-- Ask to commit (use `git-manager` if yes)
+- Ask to commit to LOCAL repository (use `git-manager` if yes)
+- **IMPORTANT:** Do NOT push to remote repository. Only commit locally. If user wants to push, suggest them to run `/commit` or `git push` manually.
 
 **Example:** Phases 1-3 parallel → Launch 3 fullstack-developer agents → Wait → Phase 4 sequential

package/prompts/ck-cook-auto.prompt.md

@@ -10,6 +10,8 @@ tools: ['search/codebase', 'search/changes', 'web/fetch', 'web/githubRepo', 'rea
 **
 
 ## Workflow:
-1. 
-2. 
-3. Finally use `AskUserQuestion` tool to ask user if he wants to commit to git repository, if yes trigger `/git:cm`  to create a commit.
+1.
+2.
+3. Finally ask user if they want to commit to git repository, if yes trigger `/git:cm` to create a LOCAL commit 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.

package/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/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/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/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/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.