cokit-cli 1.0.9 → 1.2.2

package/prompts/ck-fix-logs.prompt.md

@@ -0,0 +1,53 @@
+---
+agent: 'agent'
+description: 'Analyze logs and fix issues'
+argument-hint: 'Describe the issue'
+---
+## Variant Notice
+**IMPORTANT — Read before proceeding.**
+`ck-fix-logs` is an internal mode for issues found in logs — it is meant to be selected automatically by AI when you run `/ck-fix`.
+You don't need to call this directly. Just use `/ck-fix` and AI will pick the right mode for you.
+Before executing, you MUST output the following message **exactly as written** and wait for user response:
+
+---
+**Variant Notice**
+
+`ck-fix-logs` is an internal mode for issues found in logs — it is meant to be selected automatically by AI when you run `/ck-fix`.
+You don't need to call this directly. Just use `/ck-fix` and AI will pick the right mode for you.
+
+Do you want to continue anyway, or switch to `/ck-fix`? **[Continue / Switch to /ck-fix]**
+
+---
+
+Only proceed if user explicitly confirms Continue.
+If user chooses "Switch to /ck-fix", run  immediately — do NOT ask user to re-enter their input.
+
+
+## Mission
+<issue>${input}</issue>
+
+## Workflow
+1. Check if `./logs.txt` exists:
+   - If missing, set up permanent log piping in project's script config (`package.json`, `Makefile`, `pyproject.toml`, etc.):
+     - **Bash/Unix**: append `2>&1 | tee logs.txt`
+     - **PowerShell**: append `*>&1 | Tee-Object logs.txt`
+   - Run the command to generate logs
+2. Analyze `./logs.txt` and find root causes:
+   - Search for the last 30 lines of log output (avoid loading entire file)
+   - If insufficient context, increase `head_limit` as needed
+3. Search the codebase to find the exact location of the issues.
+4. Create an implementation plan based on findings.
+5. Implement the fix.
+6. Test the fix and make sure it works.
+7. Review the code changes and make sure it meets requirements.
+8. If there are issues or failed tests, repeat from step 3.
+9. After finishing, respond back to user with a summary of the changes and suggest next steps.
+
+---
+
+## Suggested Next Steps
+
+| Command | Description |
+|---------|-------------|
+| `/ck-test` | Run tests and analyze results |
+| `/ck-git` | Commit changes |

package/prompts/ck-fix-test.prompt.md

@@ -0,0 +1,47 @@
+---
+agent: 'agent'
+description: 'Run test suite and fix issues'
+argument-hint: 'Describe the test issues'
+---
+## Variant Notice
+**IMPORTANT — Read before proceeding.**
+`ck-fix-test` is an internal mode for test failures — it is meant to be selected automatically by AI when you run `/ck-fix`.
+You don't need to call this directly. Just use `/ck-fix` and AI will pick the right mode for you.
+Before executing, you MUST output the following message **exactly as written** and wait for user response:
+
+---
+**Variant Notice**
+
+`ck-fix-test` is an internal mode for test failures — it is meant to be selected automatically by AI when you run `/ck-fix`.
+You don't need to call this directly. Just use `/ck-fix` and AI will pick the right mode for you.
+
+Do you want to continue anyway, or switch to `/ck-fix`? **[Continue / Switch to /ck-fix]**
+
+---
+
+Only proceed if user explicitly confirms Continue.
+If user chooses "Switch to /ck-fix", run  immediately — do NOT ask user to re-enter their input.
+
+
+## Reported Issues:
+<issues>${input}</issues>
+
+## Workflow:
+1. Compile the code and fix all syntax errors if any.
+2. Run the tests and analyze the results.
+3. If there are issues or failed tests, investigate the root cause.
+4. Create an implementation plan based on findings.
+5. Implement the fix step by step.
+6. Test the fix and make sure it works.
+7. Review the code changes and make sure it meets requirements.
+8. If there are issues or failed tests, repeat from step 2.
+9. After finishing, respond back to user with a summary of the changes and suggest next steps.
+
+---
+
+## Suggested Next Steps
+
+| Command | Description |
+|---------|-------------|
+| `/ck-fix` | Analyze and fix issues |
+| `/ck-git` | Commit changes |

package/prompts/ck-fix-types.prompt.md

@@ -0,0 +1,29 @@
+---
+agent: 'agent'
+description: 'Fix type errors'
+---
+## Variant Notice
+**IMPORTANT — Read before proceeding.**
+`ck-fix-types` is an internal mode for TypeScript type errors — it is meant to be selected automatically by AI when you run `/ck-fix`.
+You don't need to call this directly. Just use `/ck-fix` and AI will pick the right mode for you.
+Before executing, you MUST output the following message **exactly as written** and wait for user response:
+
+---
+**Variant Notice**
+
+`ck-fix-types` is an internal mode for TypeScript type errors — it is meant to be selected automatically by AI when you run `/ck-fix`.
+You don't need to call this directly. Just use `/ck-fix` and AI will pick the right mode for you.
+
+Do you want to continue anyway, or switch to `/ck-fix`? **[Continue / Switch to /ck-fix]**
+
+---
+
+Only proceed if user explicitly confirms Continue.
+If user chooses "Switch to /ck-fix", run  immediately — do NOT ask user to re-enter their input.
+
+
+Run `bun run typecheck` or `tsc` or `npx tsc` and fix all type errors.
+
+## Rules
+- Fix all of type errors and repeat the process until there are no more type errors.
+- Do not use `any` just to pass the type check.

package/prompts/ck-fix-ui.prompt.md

@@ -0,0 +1,50 @@
+---
+agent: 'agent'
+description: 'Analyze and fix UI issues'
+argument-hint: 'Describe the UI issue'
+---
+## Variant Notice
+**IMPORTANT — Read before proceeding.**
+`ck-fix-ui` is an internal mode for UI/UX issues — it is meant to be selected automatically by AI when you run `/ck-fix`.
+You don't need to call this directly. Just use `/ck-fix` and AI will pick the right mode for you.
+Before executing, you MUST output the following message **exactly as written** and wait for user response:
+
+---
+**Variant Notice**
+
+`ck-fix-ui` is an internal mode for UI/UX issues — it is meant to be selected automatically by AI when you run `/ck-fix`.
+You don't need to call this directly. Just use `/ck-fix` and AI will pick the right mode for you.
+
+Do you want to continue anyway, or switch to `/ck-fix`? **[Continue / Switch to /ck-fix]**
+
+---
+
+Only proceed if user explicitly confirms Continue.
+If user chooses "Switch to /ck-fix", run  immediately — do NOT ask user to re-enter their input.
+
+
+## Required Skills
+1. **`frontend-design`** - Design patterns and implementation
+
+Read and analyze `./docs/design-guidelines.md` then fix the following issues:
+<issue>${input}</issue>
+
+## Workflow
+1. Activate `frontend-design` skill to understand design patterns and best practices.
+2. Implement the fix step by step following design guidelines.
+3. Take screenshots of the fix and analyze to verify it matches the design guideline and addresses all issues.
+   - If the issues are not addressed, repeat the process until all issues are addressed.
+4. Test the fix and compile the code to make sure it works.
+   - If there are issues or failed tests, fix all of them and repeat until all tests pass.
+5. Final Report:
+   * Summary of changes, guide user to get started, suggest next steps.
+   * Ask the user if they want to commit and push to git repository.
+
+---
+
+## Suggested Next Steps
+
+| Command | Description |
+|---------|-------------|
+| `/ck-test` | Run tests and analyze results |
+| `/ck-git` | Commit changes |

package/prompts/ck-fix.prompt.md

@@ -1,44 +1,50 @@
----
-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 with intelligent routing'
+argument-hint: 'Describe the issues to fix'
+---
+
+**Analyze issues and route to specialized fix command:**
+<issues>${input}</issues>
+
+## Decision Tree
+
+**1. Check for existing plan:**
+- If markdown plan exists → `/ck-cook <path-to-plan>`
+
+**2. Route by issue type:**
+
+**A) Type Errors** (keywords: type, typescript, tsc, type error)
+→ `/ck-fix-types`
+
+**B) UI/UX Issues** (keywords: ui, ux, design, layout, style, visual, button, component, css, responsive)
+→ `/ck-fix-ui <detailed-description>`
+
+**C) CI/CD Issues** (keywords: github actions, pipeline, ci/cd, workflow, deployment, build failed)
+→ `/ck-fix-ci <github-actions-url-or-description>`
+
+**D) Test Failures** (keywords: test, spec, jest, vitest, failing test, test suite)
+→ `/ck-fix-test <detailed-description>`
+
+**E) Log Analysis** (keywords: logs, error logs, log file, stack trace)
+→ `/ck-fix-logs <detailed-description>`
+
+**F) Complex/Multiple Issues** (keywords: complex, architecture, refactor, major, system-wide, multiple components, 2+ unrelated issues)
+→ `/ck-fix-hard <detailed-description>`
+
+**G) Simple/Quick Fixes** (default: small bug, single file, straightforward)
+→ `/ck-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 → `/ck-fix-hard`
+
+---
+
+## Suggested Next Steps
+
+| Command | Description |
+|---------|-------------|
+| `/ck-test` | Run tests and analyze results |
+| `/ck-git` | Commit changes |

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