cokit-cli 1.0.9 → 1.2.0

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

@@ -1,79 +1,104 @@
----
-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
+---
+agent: 'agent'
+description: 'Git operations with conventional commits'
+argument-hint: 'cm | cp | pr | merge'
+tools: ['execute/runInTerminal', 'execute/getTerminalOutput']
+---
+
+## Context
+Git operation:
+<operation>${input}</operation>
+
+## Arguments
+
+| Arg | Description |
+|-----|-------------|
+| `cm` | Stage files & create commits |
+| `cp` | Stage files, create commits and push |
+| `pr` | Create Pull Request [to-branch] [from-branch] |
+| `merge` | Merge [to-branch] [from-branch] |
+
+**Defaults:**
+- `to-branch`: main
+- `from-branch`: current branch
+
+## Core Workflow
+
+### Step 1: Stage + Analyze
+```bash
+git add -A && git diff --cached --stat && git diff --cached --name-only
+```
+
+### Step 2: Security Check
+Scan for secrets before commit:
+```bash
+git diff --cached | grep -iE "(api[_-]?key|token|password|secret|credential)"
+```
+**If secrets found:** STOP, warn user, suggest `.gitignore`.
+
+### Step 3: Split Decision
+
+**Split commits if:**
+- Different types mixed (feat + fix, code + docs)
+- Multiple scopes (auth + payments)
+- Config/deps + code mixed
+- FILES > 10 unrelated
+
+**Single commit if:**
+- Same type/scope, FILES ≤ 3, LINES ≤ 50
+
+### Step 4: Commit
+```bash
+git commit -m "type(scope): description"
+```
+
+## Commit Types
+
+| Type | Description |
+|------|-------------|
+| `feat` | New feature |
+| `fix` | Bug fix |
+| `docs` | Documentation only |
+| `style` | Formatting, no code change |
+| `refactor` | Code change, no feature/fix |
+| `perf` | Performance improvement |
+| `test` | Adding/updating tests |
+| `chore` | Maintenance tasks |
+
+## Output Format
+```
+✓ staged: N files (+X/-Y lines)
+✓ security: passed
+✓ commit: HASH type(scope): description
+✓ pushed: yes/no
+```
+
+## Error Handling
+
+| Error | Action |
+|-------|--------|
+| Secrets detected | Block commit, show files |
+| No changes | Exit cleanly |
+| Push rejected | Suggest `git pull --rebase` |
+| Merge conflicts | Suggest manual resolution |
+
+## Pull Request Format
+
+```bash
+gh pr create --title "type(scope): description" --body "## Summary
+- Change 1
+- Change 2
+
+## Test Plan
+- [ ] Test A
+- [ ] Test B"
+```
+
+---
+
+## Suggested Next Steps
+
+| Command | Description |
+|---------|-------------|
+| `/ck.test` | Run tests before push |
+| `/ck.review` | Code review |

package/{prompts/ck-ck-help.prompt.md → templates/repo/.github/prompts/ck-help.prompt.md}

@@ -1,112 +1,140 @@
----
-agent: 'agent'
-description: 'Cokit usage guide - just type naturally'
-tools: ['search/codebase']
----
-
-Think harder.
-All-in-one Cokit guide for GitHub Copilot. Run the script and present output based on type markers.
-
-## Pre-Processing
-
-**IMPORTANT: Always translate `${input}` to English before passing to script.**
-
-The Python script only understands English keywords. If `${input}` is in another language:
-1. Translate `${input}` to English
-2. Pass the translated English string to the script
-
-## Execution
-
-Search for CoKit resources in `.github/` directory and present them to user based on their query: `${input}`
-
-## Output Type Detection
-
-The script outputs a type marker on the first line: `@CK_OUTPUT_TYPE:<type>`
-
-**Read this marker and adjust your presentation accordingly:**
-
-### `@CK_OUTPUT_TYPE:comprehensive-docs`
-
-Full documentation (config, schema, setup guides).
-
-**Presentation:**
-1. Show the **COMPLETE** script output verbatim - every section, every code block
-2. **THEN ADD** helpful context:
-   - Real-world usage examples ("For example, if you're working on multiple projects...")
-   - Common gotchas and tips ("Watch out for: ...")
-   - Practical scenarios ("This is useful when...")
-3. End with a specific follow-up question
-
-**Example enhancement after showing full output:**
-```
-## Additional Tips
-
-**When to use global vs local config:**
-- Use global ( for personal preferences like language, issue prefix style
-- Use local ( for project-specific paths, naming conventions
-
-**Common setup for teams:**
-Each team member sets their locale globally, but projects share local config via git.
-
-Need help setting up a specific configuration?
-```
-
-### `@CK_OUTPUT_TYPE:category-guide`
-
-Workflow guides for command categories (fix, plan, cook, etc.).
-
-**Presentation:**
-1. Show the complete workflow and command list
-2. **ADD** practical context:
-   - When to use this workflow vs alternatives
-   - Real example: "If you encounter a bug in authentication, start with..."
-   - Transition tips between commands
-3. Offer to help with a specific task
-
-### `@CK_OUTPUT_TYPE:command-details`
-
-Single command documentation.
-
-**Presentation:**
-1. Show full command info from script
-2. **ADD**:
-   - Concrete usage example with realistic input
-   - When this command shines vs alternatives
-   - Common flags or variations
-3. Offer to run the command for them
-
-### `@CK_OUTPUT_TYPE:search-results`
-
-Search matches for a keyword.
-
-**Presentation:**
-1. Show all matches from script
-2. **HELP** user navigate:
-   - Group by relevance if many results
-   - Suggest most likely match based on context
-   - Offer to explain any specific command
-3. Ask what they're trying to accomplish
-
-### `@CK_OUTPUT_TYPE:task-recommendations`
-
-Task-based command suggestions.
-
-**Presentation:**
-1. Show recommended commands from script
-2. **EXPLAIN** the reasoning:
-   - Why these commands fit the task
-   - Suggested order of execution
-   - What each step accomplishes
-3. Offer to start with the first recommended command
-
-## Key Principle
-
-**Script output = foundation. Your additions = value-add.**
-
-Never replace or summarize the script output. Always show it fully, then enhance with your knowledge and context.
-
-## Important: Correct Workflows
-
-- **`/ck-plan` → `/ck-code`**: Plan first, then execute the plan
-- **`/ck-cook`**: Standalone - plans internally, no separate plan needed
-- **NEVER** suggest `/ck-plan` → `/ck-cook` (cook has its own planning)
+---
+agent: 'agent'
+description: 'CoKit usage guide - just type naturally'
+argument-hint: 'Category, command name, or task description'
+tools: ['execute/runInTerminal', 'execute/getTerminalOutput']
+---
+
+Think harder.
+All-in-one ClaudeKit guide. Run the script and present output based on type markers.
+
+## Intent Validation
+
+The script uses keyword matching with smart weighting. After getting results, **validate** against these heuristics:
+
+| Sentence Pattern | Primary Intent | Example |
+|------------------|----------------|---------|
+| `[action verb] my [object]` | The action verb | "commit my changes" → git |
+| `[context] [subject noun]` | The subject noun | "setup notifications" → notifications |
+| `[noun] [noun]` | Last noun (topic) | "discord webhook" → notifications |
+
+**Action verbs** (high intent when first): fix, test, commit, push, build, create, review, deploy, run, check, find, plan, refactor
+
+**Context words** (low intent, modify subject): setup, add, start, new, my, the, configure
+
+**Override script only if:** result clearly mismatches the sentence pattern above. Otherwise trust the algorithm.
+
+## Translation
+
+**IMPORTANT: Always translate `${input}` to English before passing to script.**
+
+The Python script only understands English keywords. If `${input}` is in another language:
+1. Translate `${input}` to English
+2. Pass the translated English string to the script
+
+## Execution
+
+```bash
+python $HOME/.copilot/scripts/ck-help.py "${input}"
+```
+
+## Output Type Detection
+
+The script outputs a type marker on the first line: `@CK_OUTPUT_TYPE:<type>`
+
+**Read this marker and adjust your presentation accordingly:**
+
+### `@CK_OUTPUT_TYPE:comprehensive-docs`
+
+Full documentation (config, schema, setup guides).
+
+**Presentation:**
+1. Show the **COMPLETE** script output verbatim - every section, every code block
+2. **THEN ADD** helpful context:
+   - Real-world usage examples ("For example, if you're working on multiple projects...")
+   - Common gotchas and tips ("Watch out for: ...")
+   - Practical scenarios ("This is useful when...")
+3. End with a specific follow-up question
+
+**Example enhancement after showing full output:**
+```
+## Additional Tips
+
+**When to use global vs local config:**
+- Use global (~/.copilot/.ck.json) for personal preferences like language, issue prefix style
+- Use local ($HOME/.copilot/.ck.json) for project-specific paths, naming conventions
+
+**Common setup for teams:**
+Each team member sets their locale globally, but projects share local config via git.
+
+Need help setting up a specific configuration?
+```
+
+### `@CK_OUTPUT_TYPE:category-guide`
+
+Workflow guides for command categories (fix, plan, cook, etc.).
+
+**Presentation:**
+1. Show the complete workflow and command list
+2. **ADD** practical context:
+   - When to use this workflow vs alternatives
+   - Real example: "If you encounter a bug in authentication, start with..."
+   - Transition tips between commands
+3. Offer to help with a specific task
+
+### `@CK_OUTPUT_TYPE:command-details`
+
+Single command documentation.
+
+**Presentation:**
+1. Show full command info from script
+2. **ADD**:
+   - Concrete usage example with realistic input
+   - When this command shines vs alternatives
+   - Common flags or variations
+3. Offer to run the command for them
+
+### `@CK_OUTPUT_TYPE:search-results`
+
+Search matches for a keyword.
+
+**Presentation:**
+1. Show all matches from script
+2. **HELP** user navigate:
+   - Group by relevance if many results
+   - Suggest most likely match based on context
+   - Offer to explain any specific command
+3. Ask what they're trying to accomplish
+
+### `@CK_OUTPUT_TYPE:task-recommendations`
+
+Task-based command suggestions.
+
+**Presentation:**
+1. Show recommended commands from script
+2. **EXPLAIN** the reasoning:
+   - Why these commands fit the task
+   - Suggested order of execution
+   - What each step accomplishes
+3. Offer to start with the first recommended command
+
+## Key Principle
+
+**Script output = foundation. Your additions = value-add.**
+
+Never replace or summarize the script output. Always show it fully, then enhance with your knowledge and context.
+
+## Important: Correct Workflows
+
+- **`/ck.plan` → `/cook`**: Plan first, then execute the plan
+- **`/cook`**: Standalone - plans internally, no separate `/ck.plan` needed
+- **NEVER** suggest `/ck.plan` → `/cook` (cook has its own planning)
+
+---
+
+## Suggested Next Steps
+
+| Command | Description |
+|---------|-------------|
+| `/ck.brainstorm` | Explore ideas |
+| `/ck.plan` | Create plan |

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

@@ -0,0 +1,17 @@
+---
+agent: 'agent'
+description: 'Write journal entries from recent changes and memories'
+---
+
+Use the `journal-writer` subagent to explore the memories and recent code changes, and write some journal entries.
+Journal entries should be concise and focused on the most important events, key changes, impacts, and decisions.
+Keep journal entries in the `./docs/journals/` directory.
+
+---
+
+## Suggested Next Steps
+
+| Command | Description |
+|---------|-------------|
+| `/ck.brainstorm` | Explore ideas |
+| `/ck.plan` | Create plan |

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

@@ -0,0 +1,85 @@
+---
+agent: 'agent'
+description: 'No research. Only analyze and create an implementation plan'
+argument-hint: 'Task description or requirements'
+---
+
+Think.
+Activate `planning` skill.
+
+## Your mission
+<task>
+${input}
+</task>
+
+## Pre-Creation Check (Active vs Suggested Plan)
+
+Check the `## Plan Context` section in the injected context:
+- If "Plan:" shows a path → Active plan exists. Ask user: "Continue with this? [Y/n]"
+- If "Suggested:" shows a path → Branch-matched hint only. Ask if they want to activate or create new.
+- If "Plan: none" → Create new plan using naming from `## Naming` section.
+
+## Workflow
+Use `planner` subagent to:
+1. If creating new: Create directory using `Plan dir:` from `## Naming` section, then run `node $HOME/.copilot/scripts/set-active-plan.cjs {plan-dir}`
+   If reusing: Use the active plan path from Plan Context.
+   Make sure you pass the directory path to every subagent during the process.
+2. Follow strictly to the "Plan Creation & Organization" rules of `planning` skill.
+3. Analyze the codebase by reading `codebase-summary.md`, `code-standards.md`, `system-architecture.md` and `project-overview-pdr.md` file.
+4. Gathers all information and create an implementation plan of this task.
+5. Ask user to review the plan.
+
+## Context Reminder (MANDATORY)
+
+**IMPORTANT:** After plan creation, you MUST remind the user:
+
+> **Best Practice:** Run `/clear` before implementing to start with fresh context.
+> Then run `/cook {plan-path}` to begin implementation.
+
+This reminder is **NON-NEGOTIABLE** - always output it after presenting the plan.
+
+## Output Requirements
+
+**Plan Directory Structure** (use `Plan dir:` from `## Naming` section)
+```
+{plan-dir}/
+├── reports/
+│   ├── XX-report.md
+│   └── ...
+├── plan.md
+├── phase-XX-phase-name-here.md
+└── ...
+```
+
+**Plan File Specification**
+- Every `plan.md` MUST start with YAML frontmatter:
+  ```yaml
+  ---
+  title: "{Brief title}"
+  description: "{One sentence for card preview}"
+  status: pending
+  priority: P2
+  effort: {sum of phases, e.g., 4h}
+  branch: {current git branch}
+  tags: [relevant, tags]
+  created: {YYYY-MM-DD}
+  ---
+  ```
+- Save the overview access point at `{plan-dir}/ck.plan.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.
+
+## Important Notes
+- **IMPORTANT:** Ensure token consumption efficiency while maintaining high quality.
+- **IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.
+- **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.
+
+---
+
+## Suggested Next Steps
+
+| Command | Description |
+|---------|-------------|
+| `/ck.test` | Run tests and analyze results |
+| `/ck.fix` | Analyze and fix issues |

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

@@ -0,0 +1,112 @@
+---
+agent: 'agent'
+description: 'Research, analyze, and create an implementation plan'
+argument-hint: 'Task description or requirements'
+tools: ['web/fetch', 'search/codebase', 'read/readFile', 'search/listDirectory', 'edit/createFile', 'edit/editFiles']
+---
+
+Think harder.
+Activate `planning` skill.
+
+## Your mission
+<task>
+${input}
+</task>
+
+## Pre-Creation Check (Active vs Suggested Plan)
+
+Check the `## Plan Context` section in the injected context:
+- If "Plan:" shows a path → Active plan exists. Ask user: "Continue with this? [Y/n]"
+- If "Suggested:" shows a path → Branch-matched hint only. Ask if they want to activate or create new.
+- If "Plan: none" → Create new plan using naming from `## Naming` section.
+
+## Workflow
+1. If creating new: Create directory using `Plan dir:` from `## Naming` section, then run `node $HOME/.copilot/scripts/set-active-plan.cjs {plan-dir}`
+   If reusing: Use the active plan path from Plan Context.
+   Make sure you pass the directory path to every subagent during the process.
+2. Follow strictly to the "Plan Creation & Organization" rules of `planning` skill.
+3. Use multiple `researcher` agents (max 2 agents) in parallel to research for this task:
+   Each agent research for a different aspect of the task and are allowed to perform max 5 tool calls.
+4. Analyze the codebase by reading `codebase-summary.md`, `code-standards.md`, `system-architecture.md` and `project-overview-pdr.md` file.
+   **ONLY PERFORM THIS FOLLOWING STEP IF `codebase-summary.md` is not available or older than 3 days**: Use `/scout <instructions>` slash command to search the codebase for files needed to complete the task.
+5. Main agent gathers all research and scout report filepaths, and pass them to `planner` subagent with the prompt to create an implementation plan of this task.
+6. Main agent receives the implementation plan from `planner` subagent, and ask user to review the plan
+
+## Post-Plan Validation (Optional)
+
+After plan creation, offer validation interview to confirm decisions before implementation.
+
+**Check `## Plan Context` → `Validation: mode=X, questions=MIN-MAX`:**
+
+| Mode | Behavior |
+|------|----------|
+| `prompt` | Ask user: "Validate this plan with a brief interview?" → Yes (Recommended) / No |
+| `auto` | Automatically execute `/ck.plan:validate {plan-path}` |
+| `off` | Skip validation step entirely |
+
+**If mode is `prompt`:** Use `AskUserQuestion` tool with options above.
+**If user chooses validation or mode is `auto`:** Execute `/ck.plan:validate {plan-path}` SlashCommand.
+
+## Context Reminder (MANDATORY)
+
+**IMPORTANT:** If user skips validation (chooses "No" or mode is `off`), you MUST remind them:
+
+> **Best Practice:** Run `/clear` before implementing to start with fresh context.
+> Then run `/cook {plan-path}` to begin implementation.
+
+This reminder is **NON-NEGOTIABLE** when validation is skipped.
+
+## Output Requirements
+
+**Plan Directory Structure** (use `Plan dir:` from `## Naming` section)
+```
+{plan-dir}/
+├── research/
+│   ├── researcher-XX-report.md
+│   └── ...
+├── reports/
+│   ├── XX-report.md
+│   └── ...
+├── scout/
+│   ├── scout-XX-report.md
+│   └── ...
+├── plan.md
+├── phase-XX-phase-name-here.md
+└── ...
+```
+
+**Research Output Requirements**
+- Ensure every research markdown report remains concise (≤150 lines) while covering all requested topics and citations.
+
+**Plan File Specification**
+- Every `plan.md` MUST start with YAML frontmatter:
+  ```yaml
+  ---
+  title: "{Brief title}"
+  description: "{One sentence for card preview}"
+  status: pending
+  priority: P2
+  effort: {sum of phases, e.g., 4h}
+  branch: {current git branch}
+  tags: [relevant, tags]
+  created: {YYYY-MM-DD}
+  ---
+  ```
+- Save the overview access point at `{plan-dir}/ck.plan.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.
+
+## Important Notes
+**IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.
+**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.
+
+---
+
+## Suggested Next Steps
+
+| Command | Description |
+|---------|-------------|
+| `/ck.test` | Run tests and analyze results |
+| `/ck.fix` | Analyze and fix issues |