Claudekit Cli

Definition

ClaudeKit CLI (ck) is a command-line tool and web dashboard for managing ClaudeKit projects. It provides 16 CLI commands, a React web dashboard, hook diagnostics, a projects registry, and GitHub integration. It is a commercial product of ClaudeKit.cc.

Version v3.41.4 is written in TypeScript and published under the MIT license. A global install exposes ck, including ck new, ck doctor, ck watch, and ck content. The dashboard from ck config is a React UI on 127.0.0.1 unless a host flag opens it on the LAN. The registry file is ~/.claudekit/projects.json. Auth can fall through the GitHub CLI, an environment token, the config file, or the OS keychain.

Basic Information

Installation

npm install -g claudekit-cli
# or: bun add -g claudekit-cli
# or: yarn global add claudekit-cli
# or: pnpm add -g claudekit-cli

ck --version

Architecture

claudekit-cli/
├── src/              # Modular domain-driven architecture (122 modules)
├── bin/              # CLI entry point
├── scripts/          # Build & utility scripts
├── docs/             # Comprehensive documentation
├── __tests__/        # Test suite
├── tests/            # Integration tests
├── plans/templates/  # Project templates
└── backlog/          # Development backlog

Core Features

CLI Commands (16)

Web Dashboard

ck config              # Local only (127.0.0.1)
ck config --host 0.0.0.0 --no-open  # LAN access

An interactive React UI for configuration and project management.

Hook Diagnostics Dashboard

Inspect recent Claude hook activity and failures from ck config, across global and project scopes.

Projects Registry

A centralized registry at ~/.claudekit/projects.json with file locking.

Multi-Tier Authentication

1. GitHub CLI (gh auth token)
2. Environment Variables (GITHUB_TOKEN)
3. Config File (~/.claudekit/config.json)
4. OS Keychain (secure storage)
5. User Prompt (with save option)

GitHub Issue Watcher (ck watch)

An autonomous daemon that monitors GitHub issues, analyzes them with Claude, generates plans, and creates PRs.

Features: issue lifecycle management (10 statuses), Claude-powered brainstorming/planning, automatic PR creation, rate limiting, multi-repo support.

Content Generation (ck content)

Scans git activity, generates social media content with Claude, and publishes to X/Twitter and Facebook.

11-phase pipeline: scan -> filter -> classify -> context -> create -> validate -> review -> photo -> publish -> engage -> analyze.

Doctor Command

ck doctor              # Full health check
ck doctor --verbose    # Verbose mode
ck doctor --report     # Shareable diagnostic report
ck doctor --fix        # Auto-fix issues
ck doctor --check-only # CI mode
ck doctor --json       # Machine-readable output

Health checks: System, ClaudeKit, Auth, Project, Modules.

Skills Migration

Auto-detects structure changes (flat -> categorized):

• SHA-256 hash comparison for customization detection
• Backup before migration, rollback on failure

Available Kits

Configuration

// ~/.claudekit/config.json
{
  "github": {
    "token": "stored_in_keychain"
  },
  "defaults": {
    "kit": "engineer",
    "dir": "."
  }
}

Architecture Highlights

• Modular: 122 focused modules (< 100 lines each)
• Facade pattern: Each domain exposes a public API
• Phase handlers: Complex commands use an orchestrator + phase handlers
• Self-documenting: kebab-case file names

Tech Stack

Pros

Cons

ck new starts a project from a template, and ck init updates one. ck skills, ck agents, and ck commands manage those pieces. ck migrate moves a flat skills tree into categories. It compares SHA-256 hashes, backs up first, and rolls back on failure. ck doctor checks System, ClaudeKit, Auth, Project, and Modules. ck watch tracks ten statuses, asks Claude for a plan, opens a pull request, and can watch more than one repo. ck content scans git activity through an eleven-phase pipeline and publishes to X or Facebook. The src tree holds 122 modules, each kept under 100 lines. The engineer kit starts at v1.0.0, and the marketing kit is v1.0.0. Only the starter kit is free. A full kit is bought from ClaudeKit.cc, and a GitHub PAT is needed to download the private repo.

When to Use

• ClaudeKit users: Manage ClaudeKit projects through the CLI/dashboard
• Project scaffolding: Need new project templates
• Hook debugging: Need visual hook diagnostics
• GitHub automation: Need autonomous issue/PR management
• Content generation: Need an automated social media pipeline

References:

• mrgoonie/claudekit-cli
• npm: claudekit-cli
• ClaudeKit.cc

See also: ClaudeKit · Claudekit Skills · Kit Comparison