cokit-cli 1.0.8 → 1.0.9

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

@@ -1,97 +1,97 @@
----
-agent: 'agent'
-description: 'Implement a feature [step by step]'
-tools: ['search/codebase', 'search/changes', 'web/fetch', 'web/githubRepo', 'read/terminalLastCommand']
----
-
-Think harder to plan & start working on these tasks follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules:
-<tasks>${input}</tasks>
-
----
-
-## Role Responsibilities
-- 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.
-
----
-
-## Your Approach
-
-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. 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. Ask the user for their preferences.
-
-5. **Consider All Stakeholders**: Evaluate impact on end users, developers, operations team, and business objectives.
-
----
-
-## Workflow:
-
-### Fullfill the request
-
-* 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.
-
-
-* Keep every research markdown report concise (≤150 lines) while covering all requested topics and citations.
-*  analyze reports from `researcher` and s to create an implementation plan using the progressive disclosure structure:
-  - Create a directory using naming pattern from `## Naming` section.
-  - Save the overview access point at `plan.md`, keep it generic, under 80 lines, and list each phase with status/progress and links.
-  - 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).
-
-### Implementation
-
-* Use   to implement the plan step by step, follow the implementation plan in `.s` directory.
-* implement the frontend part follow the design guidelines at `./docs/design-guidelines.md` file.
-  * Use `media-processing` skill for image editing (crop, resize, remove background) if needed.
-* Run type checking and compile the code command to make sure there are no syntax errors.
-
-### Testing
-
-* Write the tests for the plan, **make sure you don't use fake data, mocks, cheats, tricks, temporary solutions, just to pass the build or github actions**, 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 
-* 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
-
-* After finishing, review code. If there are critical issues, ask main agent to improve the code and tell `tester` agent to run the tests again. 
-* Repeat the "Testing" process until all tests pass.
-* When all tests pass, code is reviewed, the tasks are completed, report back to user with a summary of the changes and explain everything briefly, ask user to review the changes and approve them.
-* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
-
-### Project Management & Documentation
-
-**If user approves the changes:**
-* Use `project-manager` and s  to update the project progress and documentation:
-  * update the project progress and task status in the given plan file.
-  * update the docs in `./docs` directory if needed.
-  * create a project roadmap at `./docs/project-roadmap.md` file.
-* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
-
-**If user rejects the changes:**
-* Ask user to explain the issues and ask main agent to fix all of them and repeat the process.
-
-### Onboarding
-
-* Instruct the user to get started with the feature if needed (for example: grab the API key, set up the environment variables, etc).
-* Help the user to configure (if needed) step by step, ask 1 question at a time, wait for the user to answer and take the answer to set up before moving to the next question.
-* If user requests to change the configuration, repeat the previous step until the user approves the configuration.
-
-### 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 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.
-
-**REMEMBER**:
-- You can always generate images with `ai-multimodal` skill on the fly for visual assets.
-- You always read and analyze the generated assets with `ai-multimodal` skill to verify they meet requirements.
-- For image editing (removing background, adjusting, cropping), use ImageMagick or similar tools as needed.
+---
+agent: 'agent'
+description: 'Implement a feature [step by step]'
+tools: ['search/codebase', 'search/changes', 'web/fetch', 'web/githubRepo', 'read/terminalLastCommand']
+---
+
+Think harder to plan & start working on these tasks follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules:
+<tasks>${input}</tasks>
+
+---
+
+## Role Responsibilities
+- 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.
+
+---
+
+## Your Approach
+
+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. 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. Ask the user for their preferences.
+
+5. **Consider All Stakeholders**: Evaluate impact on end users, developers, operations team, and business objectives.
+
+---
+
+## Workflow:
+
+### Fullfill the request
+
+* 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.
+
+
+* Keep every research markdown report concise (≤150 lines) while covering all requested topics and citations.
+*  analyze reports from `researcher` and s to create an implementation plan using the progressive disclosure structure:
+  - Create a directory using naming pattern from `## Naming` section.
+  - Save the overview access point at `plan.md`, keep it generic, under 80 lines, and list each phase with status/progress and links.
+  - 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).
+
+### Implementation
+
+* Use   to implement the plan step by step, follow the implementation plan in `.s` directory.
+* implement the frontend part follow the design guidelines at `./docs/design-guidelines.md` file.
+  * Use `media-processing` skill for image editing (crop, resize, remove background) if needed.
+* Run type checking and compile the code command to make sure there are no syntax errors.
+
+### Testing
+
+* Write the tests for the plan, **make sure you don't use fake data, mocks, cheats, tricks, temporary solutions, just to pass the build or github actions**, 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 
+* 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
+
+* After finishing, review code. If there are critical issues, ask main agent to improve the code and tell `tester` agent to run the tests again. 
+* Repeat the "Testing" process until all tests pass.
+* When all tests pass, code is reviewed, the tasks are completed, report back to user with a summary of the changes and explain everything briefly, ask user to review the changes and approve them.
+* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
+
+### Project Management & Documentation
+
+**If user approves the changes:**
+* Use `project-manager` and s  to update the project progress and documentation:
+  * update the project progress and task status in the given plan file.
+  * update the docs in `./docs` directory if needed.
+  * create a project roadmap at `./docs/project-roadmap.md` file.
+* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
+
+**If user rejects the changes:**
+* Ask user to explain the issues and ask main agent to fix all of them and repeat the process.
+
+### Onboarding
+
+* Instruct the user to get started with the feature if needed (for example: grab the API key, set up the environment variables, etc).
+* Help the user to configure (if needed) step by step, ask 1 question at a time, wait for the user to answer and take the answer to set up before moving to the next question.
+* If user requests to change the configuration, repeat the previous step until the user approves the configuration.
+
+### 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 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.
+
+**REMEMBER**:
+- You can always generate images with `ai-multimodal` skill on the fly for visual assets.
+- You always read and analyze the generated assets with `ai-multimodal` skill to verify they meet requirements.
+- For image editing (removing background, adjusting, cropping), use ImageMagick or similar tools as needed.

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

@@ -1,14 +1,14 @@
----
-agent: 'agent'
-description: 'Debugging technical issues and providing solutions.'
-tools: ['search/codebase', 'search/changes', 'read/problems', 'read/terminalLastCommand']
----
-
-**Reported Issues**:
-${input}
-
-find the root cause of the issues, then analyze and explain the reports to the user.
-
-**IMPORTANT**: **Do not** implement the fix automatically.
-**IMPORTANT:** 
-**IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
+---
+agent: 'agent'
+description: 'Debugging technical issues and providing solutions.'
+tools: ['search/codebase', 'search/changes', 'read/problems', 'read/terminalLastCommand']
+---
+
+**Reported Issues**:
+${input}
+
+find the root cause of the issues, then analyze and explain the reports to the user.
+
+**IMPORTANT**: **Do not** implement the fix automatically.
+**IMPORTANT:** 
+**IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.

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

@@ -0,0 +1,51 @@
+---
+agent: 'agent'
+description: 'Documentation workflow - init, summarize, or update docs'
+tools: ['search/codebase', 'search/changes']
+---
+
+# Documentation Workflow
+
+## Usage
+
+- `/ck-docs` or `/ck-docs init` - Create initial documentation
+- `/ck-docs summarize [topics]` - Summarize codebase documentation
+- `/ck-docs update` - Update existing documentation
+
+## Commands
+
+### init (default)
+Analyze codebase and create initial documentation:
+
+1. **Scout codebase** - Run `ls -la` to identify project directories
+2. **Create docs** in `docs/` directory:
+   - `project-overview-pdr.md` - Project overview and PDR
+   - `codebase-summary.md` - Codebase summary
+   - `code-standards.md` - Code structure and standards
+   - `system-architecture.md` - System architecture
+3. **Update** `README.md` (keep under 300 lines)
+
+### summarize [topics]
+Analyze codebase based on `./docs/codebase-summary.md` and respond with summary report.
+
+Arguments:
+- `topics` - Focused topics (default: all)
+
+### update
+Analyze codebase and update existing documentation:
+
+1. **Scout codebase** for changes
+2. **Update docs** in `docs/` directory:
+   - `README.md` (keep under 300 lines)
+   - `project-overview-pdr.md`
+   - `codebase-summary.md`
+   - `code-standards.md`
+   - `system-architecture.md`
+   - `project-roadmap.md`
+   - `deployment-guide.md` [optional]
+   - `design-guidelines.md` [optional]
+
+## Notes
+- Use `docs/` directory as source of truth
+- Do not scan entire codebase unless explicitly requested
+- **DO NOT** start implementing - documentation only

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

@@ -1,44 +1,44 @@
----
-agent: 'agent'
-description: 'Analyze and fix issues [INTELLIGENT ROUTING]'
-tools: ['search/codebase', 'search/changes', 'read/problems', 'read/terminalLastCommand']
----
-
-**Analyze issues and route to specialized fix command:**
-<issues>${input}</issues>
-
-## Decision Tree
-
-**1. Check for existing plan:**
-- If markdown plan exists →  <path-to-plan>`
-
-**2. Route by issue type:**
-
-**A) Type Errors** (keywords: type, typescript, tsc, type error)
-→ `/fix:types`
-
-**B) UI/UX Issues** (keywords: ui, ux, design, layout, style, visual, button, component, css, responsive)
-→ `/fix:ui <detailed-description>`
-
-**C) CI/CD Issues** (keywords: github actions, pipeline, ci/cd, workflow, deployment, build failed)
-→ `/fix:ci <github-actions-url-or-description>`
-
-**D) Test Failures** (keywords: test, spec, jest, vitest, failing test, test suite)
-→ `/fix:test <detailed-description>`
-
-**E) Log Analysis** (keywords: logs, error logs, log file, stack trace)
-→ `/fix:logs <detailed-description>`
-
-**F) Multiple Independent Issues** (2+ unrelated issues in different areas)
-→ `/fix:parallel <detailed-description>`
-
-**G) Complex Issues** (keywords: complex, architecture, refactor, major, system-wide, multiple components)
-→ `/fix:hard <detailed-description>`
-
-**H) Simple/Quick Fixes** (default: small bug, single file, straightforward)
-→ `/fix:fast <detailed-description>`
-
-## Notes
-- `detailed-description` = enhanced prompt describing issue in detail
-- If unclear, ask user for clarification before routing
-- Can combine routes: e.g., multiple type errors + UI issue → `/fix:parallel`
+---
+agent: 'agent'
+description: 'Analyze and fix issues [INTELLIGENT ROUTING]'
+tools: ['search/codebase', 'search/changes', 'read/problems', 'read/terminalLastCommand']
+---
+
+**Analyze issues and route to specialized fix command:**
+<issues>${input}</issues>
+
+## Decision Tree
+
+**1. Check for existing plan:**
+- If markdown plan exists →  <path-to-plan>`
+
+**2. Route by issue type:**
+
+**A) Type Errors** (keywords: type, typescript, tsc, type error)
+→ `/fix:types`
+
+**B) UI/UX Issues** (keywords: ui, ux, design, layout, style, visual, button, component, css, responsive)
+→ `/fix:ui <detailed-description>`
+
+**C) CI/CD Issues** (keywords: github actions, pipeline, ci/cd, workflow, deployment, build failed)
+→ `/fix:ci <github-actions-url-or-description>`
+
+**D) Test Failures** (keywords: test, spec, jest, vitest, failing test, test suite)
+→ `/fix:test <detailed-description>`
+
+**E) Log Analysis** (keywords: logs, error logs, log file, stack trace)
+→ `/fix:logs <detailed-description>`
+
+**F) Multiple Independent Issues** (2+ unrelated issues in different areas)
+→ `/fix:parallel <detailed-description>`
+
+**G) Complex Issues** (keywords: complex, architecture, refactor, major, system-wide, multiple components)
+→ `/fix:hard <detailed-description>`
+
+**H) Simple/Quick Fixes** (default: small bug, single file, straightforward)
+→ `/fix:fast <detailed-description>`
+
+## Notes
+- `detailed-description` = enhanced prompt describing issue in detail
+- If unclear, ask user for clarification before routing
+- Can combine routes: e.g., multiple type errors + UI issue → `/fix:parallel`

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

@@ -0,0 +1,79 @@
+---
+agent: 'agent'
+description: 'Git workflow - commit, push, merge, or create PR'
+tools: ['search/changes', 'web/githubRepo']
+---
+
+# Git Workflow
+
+## Usage
+
+- `/ck-git` or `/ck-git commit` - Stage all files and create a commit (no push)
+- `/ck-git push` - Stage, commit, and push to remote
+- `/ck-git merge [to] [from]` - Merge from one branch to another
+- `/ck-git pr [to] [from]` - Create a pull request
+
+## Commands
+
+### commit (default)
+Stage all files and create a commit.
+**DO NOT push the changes to remote repository**
+
+### push
+Stage all files, create a meaningful commit based on the changes and push to remote repository.
+
+### merge [TO_BRANCH] [FROM_BRANCH]
+- TO_BRANCH: defaults to `main`
+- FROM_BRANCH: defaults to current branch
+
+**Workflow:**
+1. Sync with remote
+```bash
+git fetch origin
+git checkout {TO_BRANCH}
+git pull origin {TO_BRANCH}
+```
+
+2. Merge from REMOTE tracking branch
+```bash
+git merge origin/{FROM_BRANCH} --no-ff -m "merge: {FROM_BRANCH} into {TO_BRANCH}"
+```
+
+3. Resolve conflicts if any, then `git add . && git commit`
+
+4. Push merged result
+```bash
+git push origin {TO_BRANCH}
+```
+
+### pr [TO_BRANCH] [FROM_BRANCH]
+- TO_BRANCH: defaults to `main`
+- FROM_BRANCH: defaults to current branch
+
+**Workflow:**
+1. Ensure remote is synced
+```bash
+git fetch origin
+git push -u origin HEAD
+```
+
+2. Analyze REMOTE diff (CRITICAL)
+```bash
+git log origin/{TO_BRANCH}...origin/{FROM_BRANCH} --oneline
+git diff origin/{TO_BRANCH}...origin/{FROM_BRANCH} --stat
+git diff origin/{TO_BRANCH}...origin/{FROM_BRANCH}
+```
+
+3. Generate PR content from remote diff
+- Title: Conventional commit format
+- Body: Summary of changes on REMOTE
+
+4. Create PR
+```bash
+gh pr create --base {TO_BRANCH} --head {FROM_BRANCH} --title "..." --body "..."
+```
+
+## Notes
+- If `gh` command not available, instruct user to install GitHub CLI first
+- Always fetch and pull latest remote state before operations
+- PR content must reflect REMOTE state since PRs are based on remote branches

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

@@ -1,80 +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 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.
+---
+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-test.prompt.md

@@ -1,10 +1,10 @@
----
-agent: 'agent'
-description: 'Run tests locally and analyze the summary report.'
-tools: ['search/codebase', 'search/changes', 'read/problems', 'read/terminalLastCommand']
----
-
-run tests locally and analyze the summary report.
-
-**IMPORTANT**: **Do not** start implementing.
-**IMPORTANT:** 
+---
+agent: 'agent'
+description: 'Run tests locally and analyze the summary report.'
+tools: ['search/codebase', 'search/changes', 'read/problems', 'read/terminalLastCommand']
+---
+
+run tests locally and analyze the summary report.
+
+**IMPORTANT**: **Do not** start implementing.
+**IMPORTANT:**