ccjk 14.2.2 → 15.0.0

package/templates/skills/ccjk-init.md

@@ -1,154 +0,0 @@
----
-name: ccjk-init
-description: Initialize CCJK environment with guided setup
-version: 1.0.0
-author: CCJK Team
-category: devops
-triggers:
-  - /ccjk-init
-  - /setup-ccjk
-use_when:
-  - User wants to set up CCJK
-  - When initializing a new project with CCJK
-  - When resetting CCJK configuration
-auto_activate: true
-priority: 9
-user_invocable: true
-context: inherit
-args:
-  - name: mode
-    description: Setup mode (full, quick, project)
-    required: false
-    default: "full"
-allowed_tools:
-  - Read
-  - Write
-  - Edit
-  - Bash(npx ccjk *)
-  - Bash(ccjk *)
-  - Bash(ls *)
-  - Bash(cat *)
-  - Bash(mkdir *)
-hooks:
-  - type: SkillActivate
-    command: "echo '🚀 Starting CCJK initialization...'"
-  - type: SkillComplete
-    command: "echo '✅ CCJK initialization complete!'"
-timeout: 600
----
-
-# CCJK Initialization Skill
-
-This skill guides users through CCJK setup with intelligent defaults and best practices.
-
-## Arguments
-
-- `$0` - **mode**: Setup mode (default: "full")
-  - `full` - Complete setup with all options
-  - `quick` - Quick setup with defaults
-  - `project` - Project-specific setup only
-
-## Initialization Workflow
-
-### Phase 1: Environment Check
-
-1. **Check Node.js version**
-   - Minimum: Node.js 20+
-   - Run: `node --version`
-
-2. **Check existing configuration**
-   - Look for `~/.claude.json`
-   - Look for `~/.claude/` directory
-   - Look for `.claude/` in current project
-
-3. **Detect code tool**
-   - Check if Claude Code is installed
-   - Check for other AI code tools
-
-### Phase 2: Configuration Setup
-
-Based on mode `$0`:
-
-#### Full Mode
-1. Configure API settings (provider, key, URL)
-2. Install MCP services
-3. Install workflows
-4. Set up output styles
-5. Configure cloud sync (optional)
-
-#### Quick Mode
-1. Use default API settings
-2. Install essential MCP services
-3. Install essential workflows
-
-#### Project Mode
-1. Create `.claude/` directory
-2. Set up project-specific settings
-3. Create project CLAUDE.md
-
-### Phase 3: Verification
-
-1. **Test API connection**
-   - Verify API key works
-   - Check model availability
-
-2. **Verify MCP services**
-   - Run `ccjk mcp doctor`
-   - Check service status
-
-3. **Verify workflows**
-   - Check command availability
-   - Test a simple workflow
-
-## Commands to Execute
-
-```bash
-# Full initialization
-npx ccjk init
-
-# Quick setup
-npx ccjk init --quick
-
-# Project setup only
-npx ccjk init --project
-```
-
-## Post-Initialization
-
-After setup, users can:
-
-1. **Use workflows**:
-   - `/init-project` - Initialize project context
-   - `/feat` - Feature development
-   - `/git-commit` - Smart commits
-
-2. **Manage MCP**:
-   - `ccjk mcp list` - List services
-   - `ccjk mcp install` - Add services
-
-3. **Create skills**:
-   - `ccjk skill create` - New skill
-
-## Troubleshooting
-
-### Common Issues
-
-1. **Permission denied**
-   - Check write permissions to `~/.claude/`
-   - Run with appropriate permissions
-
-2. **API key invalid**
-   - Verify key format
-   - Check provider URL
-
-3. **MCP services failing**
-   - Run `ccjk mcp doctor`
-   - Check npm/npx availability
-
-## Example Usage
-
-```
-/ccjk-init full
-/ccjk-init quick
-/setup-ccjk project
-```

package/templates/skills/ccjk-mcp-setup.md

@@ -1,205 +0,0 @@
----
-name: ccjk-mcp-setup
-description: Interactive MCP service setup and configuration
-version: 1.0.0
-author: CCJK Team
-category: devops
-triggers:
-  - /mcp-setup
-  - /setup-mcp
-use_when:
-  - User wants to set up MCP services
-  - When configuring new MCP services
-  - When optimizing MCP configuration
-auto_activate: true
-priority: 8
-user_invocable: true
-context: inherit
-args:
-  - name: preset
-    description: MCP preset (minimal, standard, full, custom)
-    required: false
-    default: "standard"
-allowed_tools:
-  - Read
-  - Write
-  - Edit
-  - Bash(ccjk mcp *)
-  - Bash(npx *)
-  - Bash(cat *)
-  - Bash(ls *)
-  - mcp__*
-hooks:
-  - type: SkillActivate
-    command: "ccjk mcp list 2>/dev/null || echo 'No MCP services installed'"
-timeout: 600
----
-
-# MCP Setup Skill
-
-This skill helps users set up MCP services with intelligent presets and recommendations.
-
-## Arguments
-
-- `$0` - **preset**: MCP preset (default: "standard")
-  - `minimal` - Essential services only
-  - `standard` - Recommended services
-  - `full` - All available services
-  - `custom` - Interactive selection
-
-## MCP Presets
-
-### Minimal Preset
-Essential services for basic functionality:
-
-| Service | Purpose |
-|---------|--------|
-| `context7` | Documentation lookup |
-| `filesystem-mcp` | File operations |
-
-### Standard Preset (Recommended)
-Balanced set for most users:
-
-| Service | Purpose |
-|---------|--------|
-| `context7` | Documentation lookup |
-| `open-websearch` | Web search |
-| `filesystem-mcp` | File operations |
-| `github-mcp` | GitHub integration |
-
-### Full Preset
-All available services:
-
-| Service | Purpose |
-|---------|--------|
-| `context7` | Documentation lookup |
-| `open-websearch` | Web search |
-| `filesystem-mcp` | File operations |
-| `github-mcp` | GitHub integration |
-| `Playwright` | Browser automation |
-| `sqlite` | Database operations |
-| `mcp-deepwiki` | Wiki search |
-
-## Setup Workflow
-
-### Phase 1: Current State Analysis
-
-1. **Check existing MCP config**:
-   ```bash
-   cat ~/.claude/claude_desktop_config.json 2>/dev/null || echo 'No config found'
-   ```
-
-2. **List installed services**:
-   ```bash
-   ccjk mcp list
-   ```
-
-3. **Run diagnostics**:
-   ```bash
-   ccjk mcp doctor
-   ```
-
-### Phase 2: Preset Installation
-
-Based on preset `$0`:
-
-#### Minimal
-```bash
-ccjk mcp install context7
-ccjk mcp install filesystem-mcp
-```
-
-#### Standard
-```bash
-ccjk mcp install context7
-ccjk mcp install open-websearch
-ccjk mcp install filesystem-mcp
-ccjk mcp install github-mcp
-```
-
-#### Full
-```bash
-ccjk mcp install context7
-ccjk mcp install open-websearch
-ccjk mcp install filesystem-mcp
-ccjk mcp install github-mcp
-ccjk mcp install playwright
-ccjk mcp install sqlite
-ccjk mcp install mcp-deepwiki
-```
-
-#### Custom
-Interactive selection - ask user which services they want.
-
-### Phase 3: Configuration
-
-1. **Configure API keys** (if needed):
-   - GitHub token for `github-mcp`
-   - Other service credentials
-
-2. **Set environment variables**:
-   ```json
-   {
-     "mcpServers": {
-       "github-mcp": {
-         "env": {
-           "GITHUB_TOKEN": "your-token"
-         }
-       }
-     }
-   }
-   ```
-
-### Phase 4: Verification
-
-1. **Test each service**:
-   - Verify service starts
-   - Test basic functionality
-
-2. **Run final diagnostics**:
-   ```bash
-   ccjk mcp doctor
-   ```
-
-## Service Recommendations
-
-### By Use Case
-
-| Use Case | Recommended Services |
-|----------|---------------------|
-| **Web Development** | context7, playwright, github-mcp |
-| **Data Analysis** | sqlite, filesystem-mcp |
-| **Research** | open-websearch, mcp-deepwiki, context7 |
-| **DevOps** | github-mcp, filesystem-mcp |
-| **General** | context7, open-websearch, filesystem-mcp |
-
-### By Resource Usage
-
-| Level | Services | Memory |
-|-------|----------|--------|
-| **Low** | context7, filesystem-mcp | ~50MB |
-| **Medium** | + open-websearch, github-mcp | ~100MB |
-| **High** | + playwright, sqlite | ~200MB+ |
-
-## Troubleshooting
-
-### Service Won't Start
-
-1. Check npm/npx availability
-2. Verify package exists
-3. Check for port conflicts
-
-### Service Not Responding
-
-1. Restart Claude Code
-2. Check service logs
-3. Verify configuration
-
-## Example Usage
-
-```
-/mcp-setup minimal
-/mcp-setup standard
-/setup-mcp full
-/mcp-setup custom
-```

package/templates/skills/ccjk-troubleshoot.md

@@ -1,228 +0,0 @@
----
-name: ccjk-troubleshoot
-description: Diagnose and fix common CCJK issues
-version: 1.0.0
-author: CCJK Team
-category: debugging
-triggers:
-  - /ccjk-troubleshoot
-  - /ccjk-doctor
-  - /fix-ccjk
-use_when:
-  - User has CCJK issues
-  - When something isn't working
-  - When diagnosing configuration problems
-auto_activate: true
-priority: 9
-user_invocable: true
-context: inherit
-args:
-  - name: area
-    description: Area to troubleshoot (all, api, mcp, skills, workflows)
-    required: false
-    default: "all"
-allowed_tools:
-  - Read
-  - Glob
-  - Grep
-  - Bash(ccjk *)
-  - Bash(npx *)
-  - Bash(cat *)
-  - Bash(ls *)
-  - Bash(node *)
-  - Bash(npm *)
-hooks:
-  - type: SkillActivate
-    command: "echo '🔍 Starting CCJK diagnostics...'"
-timeout: 300
----
-
-# CCJK Troubleshooting Skill
-
-This skill diagnoses and fixes common CCJK issues systematically.
-
-## Arguments
-
-- `$0` - **area**: Area to troubleshoot (default: "all")
-  - `all` - Check everything
-  - `api` - API configuration issues
-  - `mcp` - MCP service issues
-  - `skills` - Skills system issues
-  - `workflows` - Workflow issues
-
-## Diagnostic Workflow
-
-### Step 1: Environment Check
-
-```bash
-# Check Node.js version
-node --version
-
-# Check npm version
-npm --version
-
-# Check CCJK version
-npx ccjk --version
-```
-
-**Expected**:
-- Node.js >= 20.0.0
-- npm >= 9.0.0
-- CCJK latest version
-
-### Step 2: Configuration Check
-
-```bash
-# Check Claude config exists
-ls -la ~/.claude.json
-
-# Check Claude directory
-ls -la ~/.claude/
-
-# Check MCP config
-ls -la ~/.claude/claude_desktop_config.json
-```
-
-**Check for**:
-- Valid JSON syntax
-- Correct file permissions
-- Required fields present
-
-### Step 3: Area-Specific Diagnostics
-
-#### API Issues (`$0` = "api")
-
-1. **Check API configuration**:
-   ```bash
-   cat ~/.claude.json | grep -E "apiKey|apiUrl|model"
-   ```
-
-2. **Common API issues**:
-   - Invalid API key format
-   - Wrong API URL
-   - Model not available
-   - Rate limiting
-
-3. **Fixes**:
-   ```bash
-   ccjk config api
-   ```
-
-#### MCP Issues (`$0` = "mcp")
-
-1. **Run MCP doctor**:
-   ```bash
-   ccjk mcp doctor
-   ```
-
-2. **Check MCP config**:
-   ```bash
-   cat ~/.claude/claude_desktop_config.json
-   ```
-
-3. **Common MCP issues**:
-   - Invalid JSON syntax
-   - Missing dependencies
-   - Wrong command paths
-   - Environment variable issues
-
-4. **Fixes**:
-   ```bash
-   # Reinstall problematic service
-   ccjk mcp uninstall <service>
-   ccjk mcp install <service>
-   ```
-
-#### Skills Issues (`$0` = "skills")
-
-1. **Check skills directories**:
-   ```bash
-   ls -la ~/.claude/skills/
-   ls -la .claude/skills/
-   ```
-
-2. **Validate skill files**:
-   - Check YAML frontmatter syntax
-   - Verify required fields
-   - Check file extensions (.md)
-
-3. **Common skills issues**:
-   - Invalid YAML syntax
-   - Missing required fields
-   - Conflicting triggers
-   - Permission issues
-
-4. **Fixes**:
-   ```bash
-   # Reload skills
-   ccjk skills reload
-
-   # Check specific skill
-   ccjk skill info <skill-name>
-   ```
-
-#### Workflow Issues (`$0` = "workflows")
-
-1. **Check workflow directories**:
-   ```bash
-   ls -la ~/.claude/commands/
-   ls -la ~/.claude/agents/
-   ```
-
-2. **Common workflow issues**:
-   - Missing command files
-   - Missing agent files
-   - Invalid YAML frontmatter
-   - Broken agent references
-
-3. **Fixes**:
-   ```bash
-   # Reinstall workflows
-   ccjk workflows install --force
-
-   # Update workflows
-   ccjk workflows update
-   ```
-
-### Step 4: Generate Report
-
-After diagnostics, provide:
-
-1. **Summary of issues found**
-2. **Recommended fixes**
-3. **Commands to run**
-4. **Prevention tips**
-
-## Quick Fixes
-
-### Reset Everything
-
-```bash
-# Backup current config
-ccjk config backup
-
-# Reinitialize
-npx ccjk init --force
-```
-
-### Fix Permissions
-
-```bash
-chmod 644 ~/.claude.json
-chmod -R 755 ~/.claude/
-```
-
-### Clear Cache
-
-```bash
-rm -rf ~/.ccjk/cache/
-```
-
-## Example Usage
-
-```
-/ccjk-troubleshoot
-/ccjk-troubleshoot api
-/ccjk-troubleshoot mcp
-/fix-ccjk skills
-```

package/templates/skills/code-refactor.hbs

@@ -1,133 +0,0 @@
----
-name: code-refactor
-description: Intelligent code refactoring with file operation priority
-version: 1.0.0
-author: CCJK Team
-category: dev
-triggers:
-  - /refactor
-  - /code-refactor
-use_when:
-  - User wants to refactor code
-  - When code needs restructuring or cleanup
-  - When improving code quality
-auto_activate: true
-priority: 7
-user_invocable: true
-context: inherit
-args:
-  - name: file
-    description: Target file or directory to refactor
-    required: true
-    type: path
-  - name: scope
-    description: Refactoring scope (function, class, module, all)
-    required: false
-    default: "all"
-allowed_tools:
-  - Read
-  - Edit
-  - Write
-  - Glob
-  - Grep
-  - Bash(git diff *)
-  - Bash(git status)
-hooks:
-  - type: SkillActivate
-    command: "git status --short"
-  - type: PreToolUse
-    matcher: "Edit(*)"
-    command: "echo 'Editing file...'"
-timeout: 600
----
-
-# Code Refactoring Skill
-
-Intelligent code refactoring that prioritizes file operation tools (Read, Edit, Write) over bash commands, following Claude Code v2.1.21+ best practices.
-
-## Core Principles
-
-1. **File Operations First**: Always use Read/Edit/Write tools instead of cat/sed/awk
-2. **Preserve Behavior**: Refactoring must not change external behavior
-3. **Incremental Changes**: Make small, verifiable changes
-4. **Test Coverage**: Ensure tests pass after each change
-
-## Arguments
-
-- `$0` - **file**: Target file or directory to refactor (required)
-- `$1` - **scope**: Refactoring scope - function, class, module, or all (default: "all")
-
-## Workflow
-
-### Step 1: Analysis
-
-1. Use `Read` tool to examine the target file: `$0`
-2. Identify code smells and improvement opportunities
-3. Check for existing tests
-
-### Step 2: Planning
-
-1. List specific refactoring actions needed
-2. Prioritize by impact and risk
-3. Identify dependencies between changes
-
-### Step 3: Execution
-
-For each refactoring action:
-
-1. **Read** the current state of the code
-2. **Edit** with precise, minimal changes
-3. **Verify** the change doesn't break functionality
-
-### Step 4: Verification
-
-1. Run existing tests
-2. Check for type errors
-3. Verify git diff shows expected changes
-
-## Refactoring Patterns
-
-### Extract Function
-```typescript
-// Before
-function process() {
-  // complex logic A
-  // complex logic B
-}
-
-// After
-function process() {
-  doLogicA()
-  doLogicB()
-}
-```
-
-### Rename for Clarity
-```typescript
-// Before
-const d = getData()
-
-// After
-const userData = fetchUserData()
-```
-
-### Remove Dead Code
-- Delete unused imports
-- Remove commented-out code
-- Clean up unused variables
-
-## Important Rules
-
-1. **NEVER use bash for file editing** - Use Edit tool instead of sed/awk
-2. **NEVER use cat for reading** - Use Read tool
-3. **Always show diff preview** before committing changes
-4. **Preserve formatting** - Match existing code style
-5. **One concern per edit** - Don't mix unrelated changes
-
-## Example Usage
-
-```
-/refactor src/utils/config.ts function
-/refactor src/components/ all
-/code-refactor ./lib/parser.ts class
-```