cokit-cli 1.3.0 → 1.4.0

package/skills/git/SKILL.md

@@ -1,113 +0,0 @@
----
-name: git
-description: "Git operations with conventional commits. Use for staging, committing, pushing, PRs, merges. Auto-splits commits by type/scope. Security scans for secrets."
-argument-hint: "cm|cp|pr|merge [args]"
----
-
-# Git Operations
-
-## Default (No Arguments)
-
-If invoked without arguments, ask the user to present available git operations:
-
-| Operation | Description |
-|-----------|-------------|
-| `cm` | Stage files & create commits |
-| `cp` | Stage files, create commits and push |
-| `pr` | Create Pull Request |
-| `merge` | Merge branches |
-
-Present as options by asking the user with header "Git Operation", question "What would you like to do?".
-
-Execute git workflows via `git-manager` subagent to isolate verbose output.
-Activate `context-engineering` skill.
-
-**IMPORTANT:**
-- Sacrifice grammar for the sake of concision.
-- Ensure token efficiency while maintaining high quality.
-- Pass these rules to subagents.
-
-## Arguments
-- `cm`: Stage files & create commits
-- `cp`: Stage files, create commits and push
-- `pr`: Create Pull Request [to-branch] [from-branch]
-  - `to-branch`: Target branch (default: main)
-  - `from-branch`: Source branch (default: current branch)
-- `merge`: Merge [to-branch] [from-branch]
-  - `to-branch`: Target branch (default: main)
-  - `from-branch`: Source branch (default: current branch)
-
-## Quick Reference
-
-| Task | Reference |
-|------|-----------|
-| Commit | `references/workflow-commit.md` |
-| Push | `references/workflow-push.md` |
-| Pull Request | `references/workflow-pr.md` |
-| Merge | `references/workflow-merge.md` |
-| Standards | `references/commit-standards.md` |
-| Safety | `references/safety-protocols.md` |
-| Branches | `references/branch-management.md` |
-| GitHub CLI | `references/gh-cli-guide.md` |
-
-## 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
-
-**NOTE:**
-- Search for related issues on GitHub and add to body.
-- Only use `feat`, `fix`, or `perf` prefixes for files in skills directory (do not use `docs`).
-
-**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"
-```
-
-## 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 |
-
-## References
-
-- `references/workflow-commit.md` - Commit workflow with split logic
-- `references/workflow-push.md` - Push workflow with error handling
-- `references/workflow-pr.md` - PR creation with remote diff analysis
-- `references/workflow-merge.md` - Branch merge workflow
-- `references/commit-standards.md` - Conventional commit format rules
-- `references/safety-protocols.md` - Secret detection, branch protection
-- `references/branch-management.md` - Naming, lifecycle, strategies
-- `references/gh-cli-guide.md` - GitHub CLI commands reference

package/skills/git/references/workflow-commit.md

@@ -1,58 +0,0 @@
-# Commit Workflow
-
-Execute via `git-manager` subagent.
-
-## Tool 1: Stage + Analyze
-```bash
-git add -A && \
-echo "=== STAGED ===" && git diff --cached --stat && \
-echo "=== SECURITY ===" && \
-git diff --cached | grep -c -iE "(api[_-]?key|token|password|secret|credential)" | awk '{print "SECRETS:"$1}' && \
-echo "=== GROUPS ===" && \
-git diff --cached --name-only | awk -F'/' '{
-  if ($0 ~ /\.(md|txt)$/) print "docs:"$0
-  else if ($0 ~ /test|spec/) print "test:"$0
-  else if ($0 ~ /skills|agents/) print "config:"$0
-  else if ($0 ~ /package\.json|lock/) print "deps:"$0
-  else print "code:"$0
-}'
-```
-
-**If SECRETS > 0:** STOP, show matches, block commit.
-
-## Tool 2: Split Decision
-
-NOTE: 
-- Search for related issues on GitHub and add to body.
-- Only use `feat`, `fix`, or `perf` prefixes for files in skills directory (do not use `docs`).
-
-**From groups, decide:**
-
-**A) Single commit:** Same type/scope, FILES ≤ 3, LINES ≤ 50
-
-**B) Multi commit:** Mixed types/scopes, group by:
-- Group 1: `config:` → `chore(config): ...`
-- Group 2: `deps:` → `chore(deps): ...`
-- Group 3: `test:` → `test: ...`
-- Group 4: `code:` → `feat|fix: ...`
-- Group 5: `docs:` → `docs: ...`
-
-## Tool 3: Commit
-
-**Single:**
-```bash
-git commit -m "type(scope): description"
-```
-
-**Multi (sequential):**
-```bash
-git reset && git add file1 file2 && git commit -m "type(scope): desc"
-```
-Repeat for each group.
-
-## Tool 4: Push (if requested)
-```bash
-git push && echo "✓ pushed: yes" || echo "✓ pushed: no"
-```
-
-**Only push if user explicitly requested** ("push", "commit and push").

package/skills/git/references/workflow-merge.md

@@ -1,48 +0,0 @@
-# Merge Workflow
-
-Execute via `git-manager` subagent.
-
-## Variables
-- TO_BRANCH: target (defaults to `main`)
-- FROM_BRANCH: source (defaults to current branch)
-
-## Step 1: Sync with Remote
-
-**IMPORTANT: Always merge `main` (or any default branch) to current branch first.**
-
-```bash
-git fetch origin
-git checkout {TO_BRANCH}
-git pull origin {TO_BRANCH}
-```
-
-## Step 2: Merge from REMOTE
-```bash
-git merge origin/{FROM_BRANCH} --no-ff -m "merge: {FROM_BRANCH} into {TO_BRANCH}"
-```
-
-**Why `origin/{FROM_BRANCH}`:** Ensures merging only committed+pushed changes, not local WIP.
-
-## Step 3: Resolve Conflicts
-If conflicts:
-1. Resolve manually
-2. `git add . && git commit`
-3. If clarifications needed, report to main agent
-
-## Step 4: Push
-```bash
-git push origin {TO_BRANCH}
-```
-
-## Pre-Merge Checklist
-- Fetch latest: `git fetch origin`
-- Ensure FROM_BRANCH pushed to remote
-- Check for conflicts: `git merge --no-commit --no-ff origin/{FROM_BRANCH}` then abort
-
-## Error Handling
-
-| Error | Action |
-|-------|--------|
-| Merge conflicts | Resolve manually, then commit |
-| Branch not found | Verify branch name, ensure pushed |
-| Push rejected | `git pull --rebase`, retry |

package/skills/git/references/workflow-pr.md

@@ -1,58 +0,0 @@
-# Pull Request Workflow
-
-Execute via `git-manager` subagent.
-
-## Variables
-- TO_BRANCH: target (defaults to `main`)
-- FROM_BRANCH: source (defaults to current branch)
-
-## CRITICAL: Use REMOTE diff
-PRs based on remote branches. Local diff includes unpushed changes.
-
-## Tool 1: Sync + Analyze
-
-**IMPORTANT: Always merge `main` (or any default branch) to current branch first.**
-
-```bash
-git fetch origin && \
-git push -u origin HEAD 2>/dev/null || true && \
-BASE=${BASE_BRANCH:-main} && \
-HEAD=$(git rev-parse --abbrev-ref HEAD) && \
-echo "=== PR: $HEAD → $BASE ===" && \
-echo "=== COMMITS ===" && \
-git log origin/$BASE...origin/$HEAD --oneline && \
-echo "=== FILES ===" && \
-git diff origin/$BASE...origin/$HEAD --stat
-```
-
-**If "Branch not on remote":** Push first, retry.
-
-## Tool 2: Generate Content
-**Title:** Conventional commit format, <72 chars, NO version numbers
-**Body:** Summary bullets + Test plan checklist
-
-## Tool 3: Create PR
-```bash
-gh pr create --base $BASE --head $HEAD --title "..." --body "$(cat <<'EOF'
-## Summary
-- Bullet points
-
-## Test plan
-- [ ] Test item
-EOF
-)"
-```
-
-## DO NOT use (local comparison)
-- ❌ `git diff main...HEAD`
-- ❌ `git diff --cached`
-- ❌ `git status`
-
-## Error Handling
-
-| Error | Action |
-|-------|--------|
-| Branch not on remote | `git push -u origin HEAD`, retry |
-| Empty diff | Warn: "No changes for PR" |
-| Push rejected | `git pull --rebase`, resolve, push |
-| No upstream | `git push -u origin HEAD` |

package/skills/git/references/workflow-push.md

@@ -1,52 +0,0 @@
-# Push Workflow
-
-Execute via `git-manager` subagent.
-
-## Pre-Push Checklist
-1. All changes committed
-2. Secrets scanned (see `safety-protocols.md`)
-3. Branch pushed to remote
-
-## Tool 1: Verify State
-```bash
-git status && \
-git log origin/$(git rev-parse --abbrev-ref HEAD)..HEAD --oneline 2>/dev/null || echo "NO_UPSTREAM"
-```
-
-**If uncommitted changes:** Warn user, suggest commit first.
-**If NO_UPSTREAM:** Use `git push -u origin HEAD`.
-
-## Tool 2: Push
-```bash
-git push origin HEAD
-```
-
-**On success:** Report commit hashes pushed.
-
-## Error Handling
-
-| Error | Cause | Solution |
-|-------|-------|----------|
-| `rejected - non-fast-forward` | Remote has newer commits | `git pull --rebase`, resolve conflicts, push again |
-| `no upstream branch` | Branch not tracked | `git push -u origin HEAD` |
-| `Authentication failed` | Invalid credentials | Check `gh auth status` or SSH keys |
-| `Repository not found` | Wrong remote URL | Verify `git remote -v` |
-| `Permission denied` | No write access | Check repository permissions |
-
-## Force Push (DANGER)
-
-**NEVER force push to main/master/production branches.**
-
-If user explicitly requests force push on feature branch:
-```bash
-git push -f origin HEAD
-```
-
-**Warn user:** "Force push rewrites history. Collaborators may lose work."
-
-## Output Format
-```
-✓ pushed: N commits to origin/{branch}
-  - abc123 feat(auth): add login
-  - def456 fix(api): resolve timeout
-```

package/skills/mcp-management/SKILL.md

@@ -1,210 +0,0 @@
----
-name: mcp-management
-description: Manage MCP servers - discover, analyze, execute tools/prompts/resources. Use for MCP integrations, intelligent tool selection, multi-server management, context-efficient capability discovery.
-argument-hint: "[task or server-name]"
----
-
-# MCP Management
-
-Skill for managing and interacting with Model Context Protocol (MCP) servers.
-
-## Overview
-
-MCP is an open protocol enabling AI agents to connect to external tools and data sources. This skill provides scripts and utilities to discover, analyze, and execute MCP capabilities from configured servers without polluting the main context window.
-
-**Key Benefits**:
-- Progressive disclosure of MCP capabilities (load only what's needed)
-- Intelligent tool/prompt/resource selection based on task requirements
-- Multi-server management from single config file
-- Context-efficient: subagents handle MCP discovery and execution
-- Persistent tool catalog: automatically saves discovered tools to JSON for fast reference
-
-## When to Use This Skill
-
-Use this skill when:
-1. **Discovering MCP Capabilities**: Need to list available tools/prompts/resources from configured servers
-2. **Task-Based Tool Selection**: Analyzing which MCP tools are relevant for a specific task
-3. **Executing MCP Tools**: Calling MCP tools programmatically with proper parameter handling
-4. **MCP Integration**: Building or debugging MCP client implementations
-5. **Context Management**: Avoiding context pollution by delegating MCP operations to subagents
-
-## Core Capabilities
-
-### 1. Configuration Management
-
-MCP servers configured in `.vscode/mcp.json`.
-
-**Gemini CLI Integration** (recommended): Create symlink to `.gemini/settings.json`:
-```bash
-mkdir -p .gemini && ln -sf .vscode/mcp.json .gemini/settings.json
-```
-
-See [references/configuration.md](references/configuration.md) and [references/gemini-cli-integration.md](references/gemini-cli-integration.md).
-
-**GEMINI.md Response Format**: Project root contains `GEMINI.md` that Gemini CLI auto-loads, enforcing structured JSON responses:
-```json
-{"server":"name","tool":"name","success":true,"result":<data>,"error":null}
-```
-
-This ensures parseable, consistent output instead of unpredictable natural language. The file defines:
-- Mandatory JSON-only response format (no markdown, no explanations)
-- Maximum 500 character responses
-- Error handling structure
-- Available MCP servers reference
-
-**Benefits**: Programmatically parseable output, consistent error reporting, DRY configuration (format defined once), context-efficient (auto-loaded by Gemini CLI).
-
-### 2. Capability Discovery
-
-```bash
-npx tsx scripts/cli.ts list-tools  # Saves to assets/tools.json
-npx tsx scripts/cli.ts list-prompts
-npx tsx scripts/cli.ts list-resources
-```
-
-Aggregates capabilities from multiple servers with server identification.
-
-### 3. Intelligent Tool Analysis
-
-LLM analyzes `assets/tools.json` directly - better than keyword matching algorithms.
-
-### 4. Tool Execution
-
-**Primary: Gemini CLI** (if available)
-```bash
-# IMPORTANT: Use stdin piping, NOT -p flag (deprecated, skips MCP init)
-echo "Take a screenshot of https://example.com" | gemini -y -m <gemini.model>
-```
-
-**Secondary: Direct Scripts**
-```bash
-npx tsx scripts/cli.ts call-tool memory create_entities '{"entities":[...]}'
-```
-
-**Fallback: mcp-manager Subagent**
-
-See [references/gemini-cli-integration.md](references/gemini-cli-integration.md) for complete examples.
-
-## Implementation Patterns
-
-### Pattern 1: Gemini CLI Auto-Execution (Primary)
-
-Use Gemini CLI for automatic tool discovery and execution. Gemini CLI auto-loads `GEMINI.md` from project root to enforce structured JSON responses.
-
-**Quick Example**:
-```bash
-# IMPORTANT: Use stdin piping, NOT -p flag (deprecated, skips MCP init)
-# Add "Return JSON only per GEMINI.md instructions" to enforce structured output
-echo "Take a screenshot of https://example.com. Return JSON only per GEMINI.md instructions." | gemini -y -m <gemini.model>
-```
-
-**Expected Output**:
-```json
-{"server":"puppeteer","tool":"screenshot","success":true,"result":"screenshot.png","error":null}
-```
-
-**Benefits**:
-- Automatic tool discovery
-- Structured JSON responses (parseable by AI)
-- GEMINI.md auto-loaded for consistent formatting
-- Faster than subagent orchestration
-- No natural language ambiguity
-
-See [references/gemini-cli-integration.md](references/gemini-cli-integration.md) for complete guide.
-
-### Pattern 2: Subagent-Based Execution (Fallback)
-
-Use `mcp-manager` agent when Gemini CLI unavailable. Subagent discovers tools, selects relevant ones, executes tasks, reports back.
-
-**Benefit**: Main context stays clean, only relevant tool definitions loaded when needed.
-
-### Pattern 3: LLM-Driven Tool Selection
-
-LLM reads `assets/tools.json`, intelligently selects relevant tools using context understanding, synonyms, and intent recognition.
-
-### Pattern 4: Multi-Server Orchestration
-
-Coordinate tools across multiple servers. Each tool knows its source server for proper routing.
-
-## Scripts Reference
-
-### scripts/mcp-client.ts
-
-Core MCP client manager class. Handles:
-- Config loading from `.vscode/mcp.json`
-- Connecting to multiple MCP servers
-- Listing tools/prompts/resources across all servers
-- Executing tools with proper error handling
-- Connection lifecycle management
-
-### scripts/cli.ts
-
-Command-line interface for MCP operations. Commands:
-- `list-tools` - Display all tools and save to `assets/tools.json`
-- `list-prompts` - Display all prompts
-- `list-resources` - Display all resources
-- `call-tool <server> <tool> <json>` - Execute a tool
-
-**Note**: `list-tools` persists complete tool catalog to `assets/tools.json` with full schemas for fast reference, offline browsing, and version control.
-
-## Quick Start
-
-**Method 1: Gemini CLI** (recommended)
-```bash
-npm install -g gemini-cli
-mkdir -p .gemini && ln -sf .vscode/mcp.json .gemini/settings.json
-# IMPORTANT: Use stdin piping, NOT -p flag (deprecated, skips MCP init)
-# GEMINI.md auto-loads to enforce JSON responses
-echo "Take a screenshot of https://example.com. Return JSON only per GEMINI.md instructions." | gemini -y -m <gemini.model>
-```
-
-Returns structured JSON: `{"server":"puppeteer","tool":"screenshot","success":true,"result":"screenshot.png","error":null}`
-
-**Method 2: Scripts**
-```bash
-cd skills/mcp-management/scripts && npm install
-npx tsx cli.ts list-tools  # Saves to assets/tools.json
-npx tsx cli.ts call-tool memory create_entities '{"entities":[...]}'
-```
-
-**Method 3: mcp-manager Subagent**
-
-See [references/gemini-cli-integration.md](references/gemini-cli-integration.md) for complete guide.
-
-## Technical Details
-
-See [references/mcp-protocol.md](references/mcp-protocol.md) for:
-- JSON-RPC protocol details
-- Message types and formats
-- Error codes and handling
-- Transport mechanisms (stdio, HTTP+SSE)
-- Best practices
-
-## Integration Strategy
-
-### Execution Priority
-
-1. **Gemini CLI** (Primary): Fast, automatic, intelligent tool selection
-   - Check: `command -v gemini`
-   - Execute: `echo "<task>" | gemini -y -m <gemini.model>`
-   - **IMPORTANT**: Use stdin piping, NOT `-p` flag (deprecated, skips MCP init)
-   - Best for: All tasks when available
-
-2. **Direct CLI Scripts** (Secondary): Manual tool specification
-   - Use when: Need specific tool/server control
-   - Execute: `npx tsx scripts/cli.ts call-tool <server> <tool> <args>`
-
-3. **mcp-manager Subagent** (Fallback): Context-efficient delegation
-   - Use when: Gemini unavailable or failed
-   - Keeps main context clean
-
-### Integration with Agents
-
-The `mcp-manager` agent uses this skill to:
-- Check Gemini CLI availability first
-- Execute via `gemini` command if available
-- Fallback to direct script execution
-- Discover MCP capabilities without loading into main context
-- Report results back to main agent
-
-This keeps main agent context clean and enables efficient MCP integration.

package/skills/mermaidjs-v11/SKILL.md

@@ -1,116 +0,0 @@
----
-name: mermaidjs-v11
-description: Create diagrams with Mermaid.js v11 syntax. Use for flowcharts, sequence diagrams, class diagrams, ER diagrams, Gantt charts, state diagrams, architecture diagrams, timelines, user journeys.
-argument-hint: "[diagram-type or description]"
----
-
-# Mermaid.js v11
-
-## Overview
-
-Create text-based diagrams using Mermaid.js v11 declarative syntax. Convert code to SVG/PNG/PDF via CLI or render in browsers/markdown files.
-
-## Quick Start
-
-**Basic Diagram Structure:**
-```
-{diagram-type}
-  {diagram-content}
-```
-
-**Common Diagram Types:**
-- `flowchart` - Process flows, decision trees
-- `sequenceDiagram` - Actor interactions, API flows
-- `classDiagram` - OOP structures, data models
-- `stateDiagram` - State machines, workflows
-- `erDiagram` - Database relationships
-- `gantt` - Project timelines
-- `journey` - User experience flows
-
-See `references/diagram-types.md` for all 24+ types with syntax.
-
-## Creating Diagrams
-
-**Inline Markdown Code Blocks:**
-````markdown
-```mermaid
-flowchart TD
-    A[Start] --> B{Decision}
-    B -->|Yes| C[Action]
-    B -->|No| D[End]
-```
-````
-
-**Configuration via Frontmatter:**
-````markdown
-```mermaid
----
-theme: dark
----
-flowchart LR
-    A --> B
-```
-````
-
-**Comments:** Use `%% ` prefix for single-line comments.
-
-## CLI Usage
-
-Convert `.mmd` files to images:
-```bash
-# Installation
-npm install -g @mermaid-js/mermaid-cli
-
-# Basic conversion
-mmdc -i diagram.mmd -o diagram.svg
-
-# With theme and background
-mmdc -i input.mmd -o output.png -t dark -b transparent
-
-# Custom styling
-mmdc -i diagram.mmd --cssFile style.css -o output.svg
-```
-
-See `references/cli-usage.md` for Docker, batch processing, and advanced workflows.
-
-## JavaScript Integration
-
-**HTML Embedding:**
-```html
-<pre class="mermaid">
-  flowchart TD
-    A[Client] --> B[Server]
-</pre>
-<script src="https://cdn.jsdelivr.net/npm/mermaid@latest/dist/mermaid.min.js"></script>
-<script>mermaid.initialize({ startOnLoad: true });</script>
-```
-
-See `references/integration.md` for Node.js API and advanced integration patterns.
-
-## Configuration & Theming
-
-**Common Options:**
-- `theme`: "default", "dark", "forest", "neutral", "base"
-- `look`: "classic", "handDrawn"
-- `fontFamily`: Custom font specification
-- `securityLevel`: "strict", "loose", "antiscript"
-
-See `references/configuration.md` for complete config options, theming, and customization.
-
-## Practical Patterns
-
-Load `references/examples.md` for:
-- Architecture diagrams
-- API documentation flows
-- Database schemas
-- Project timelines
-- State machines
-- User journey maps
-
-## Resources
-
-- `references/diagram-types.md` - Syntax for all 24+ diagram types
-- `references/configuration.md` - Config, theming, accessibility
-- `references/cli-usage.md` - CLI commands and workflows
-- `references/integration.md` - JavaScript API and embedding
-- `references/examples.md` - Practical patterns and use cases