ClaudeKit CLI Overview

Command-line tool for bootstrapping and updating ClaudeKit projects from private GitHub repository releases.

What is ClaudeKit CLI?

ClaudeKit CLI (ck) is a command-line tool that downloads and manages ClaudeKit starter kits from private GitHub repositories. Built with Bun and TypeScript, it provides fast, secure project setup and updates.

Important: You need to purchase a ClaudeKit Starter Kit from ClaudeKit.cc to use this CLI. Without a purchased kit and repository access, the CLI cannot download project templates.

Key Features

  • Multi-tier GitHub Authentication - Secure authentication via gh CLI → env vars → keychain → prompt
  • Streaming Downloads - Fast downloads with progress tracking
  • Smart File Merging - Updates projects without breaking custom changes
  • Protected Files - Automatic protection of sensitive files and custom configurations
  • Secure Credential Storage - Uses OS keychain for token management
  • Beautiful CLI Interface - Interactive prompts with progress indicators

Core Commands

ck new

Create new project from latest ClaudeKit release:

# Interactive mode
ck new

# With options
ck new --dir my-project --kit engineer

# Specific version
ck new --kit engineer --version v1.0.0

Options:

  • --dir <dir> - Target directory (default: current directory)
  • --kit <kit> - Kit to use (engineer or marketing)
  • --version <version> - Specific version to download (default: latest)
  • --exclude <pattern> - Exclude files/directories using glob patterns (can be used multiple times)

Learn more about ck new

ck update

Update existing project to latest or specific version:

# Interactive mode
ck update

# With options
ck update --kit engineer

# Specific version
ck update --kit engineer --version v1.0.0

What it does:

  • Downloads specified ClaudeKit release
  • Intelligently merges files
  • Preserves your custom changes
  • Protects sensitive files
  • Maintains custom .claude/ files

Options:

  • --dir <dir> - Target directory (default: current directory)
  • --kit <kit> - Kit to use (engineer or marketing)
  • --version <version> - Specific version to download (default: latest)
  • --exclude <pattern> - Exclude files/directories using glob patterns (can be used multiple times)

ck versions

List available versions of ClaudeKit releases:

# Show all available versions
ck versions

# Filter by specific kit
ck versions --kit engineer
ck versions --kit marketing

# Show more versions (default: 30)
ck versions --limit 50

# Include prereleases and drafts
ck versions --all

Options:

  • --kit <kit> - Filter by specific kit
  • --limit <limit> - Number of releases to show (default: 30)
  • --all - Show all releases including prereleases

Global Options

All commands support these global options:

—verbose, -v

Enable verbose logging for debugging:

ck new --verbose
ck update -v  # Short form

Shows:

  • HTTP request/response details (tokens sanitized)
  • File operations (downloads, extractions, copies)
  • Command execution steps and timing
  • Error stack traces with full context
  • Authentication flow details

—log-file

Write logs to file for sharing:

ck new --verbose --log-file debug.log

Note: All sensitive data (tokens, credentials) is automatically sanitized in logs.

Available Kits

ClaudeKit offers premium starter kits (purchase required):

  • engineer: ClaudeKit Engineer - Engineering toolkit with 14 specialized agents
  • marketing: ClaudeKit Marketing - [Coming Soon]

Purchase at ClaudeKit.cc to get repository access.

Authentication

The CLI requires a GitHub Personal Access Token (PAT) to download releases from private repositories.

Authentication Flow (Multi-Tier Fallback)

  1. GitHub CLI: Uses gh auth token if available
  2. Environment Variables: Checks GITHUB_TOKEN or GH_TOKEN
  3. OS Keychain: Retrieves stored token
  4. User Prompt: Prompts for token and offers secure storage

Creating a Personal Access Token

  1. Go to GitHub Settings → Developer settings → Personal access tokens → Tokens (classic)
  2. Generate new token with repo scope (for private repositories)
  3. Copy the token

Setting Token via Environment Variable

export GITHUB_TOKEN=ghp_your_token_here

Configuration

Configuration stored in ~/.claudekit/config.json:

{
  "github": {
    "token": "stored_in_keychain"
  },
  "defaults": {
    "kit": "engineer",
    "dir": "."
  }
}

Protected Files

These files are never overwritten during updates:

  • Environment files: .env, .env.local, .env.*.local
  • Security files: *.key, *.pem, *.p12
  • Dependencies: node_modules/**, .git/**
  • Build outputs: dist/**, build/**

Custom .claude Files

Your custom files in .claude/ directory are automatically preserved:

Example:

Your project:
  .claude/
    ├── commands/standard.md  (from ClaudeKit)
    └── commands/my-custom.md (your custom command)

After update:
  .claude/
    ├── commands/standard.md  (updated from release)
    └── commands/my-custom.md (preserved automatically)

Quick Start

# Install CLI
npm install -g claudekit-cli

# Verify installation
ck --version

# Authenticate with GitHub
gh auth login
# OR
export GITHUB_TOKEN=ghp_your_token

# Create new project
ck new --kit engineer

# Navigate to project
cd my-project

# Start using ClaudeKit
claude  # Start Claude Code

Common Workflows

Create New Project

# Interactive mode (recommended)
ck new

# Direct with options
ck new --dir my-app --kit engineer

# Specific version
ck new --dir my-app --kit engineer --version v1.0.0

# With exclusions
ck new --kit engineer --exclude "*.log" --exclude "temp/**"

Update Existing Project

# Update to latest
ck update

# Update to specific version
ck update --version v1.2.0

# Update with exclusions
ck update --exclude "local-config/**" --exclude "*.local"

# Update with verbose output
ck update --verbose

Check Available Versions

# List all versions
ck versions

# Filter by kit
ck versions --kit engineer

# Show more releases
ck versions --limit 50

Troubleshooting

Authentication Failed

Problem: “Authentication failed”

Solutions:

  1. Check if GitHub CLI is authenticated: gh auth status
  2. Or set environment variable: export GITHUB_TOKEN=ghp_your_token
  3. Verify token has repo scope
  4. Check repository access (requires purchased kit)

Command Not Found

Problem: ck: command not found

Solutions:

# Reinstall globally
npm install -g claudekit-cli

# Check installation
npm list -g claudekit-cli

# Restart terminal

Download Fails

Problem: “Failed to download release”

Solutions:

  1. Check internet connection
  2. Verify GitHub token is valid: gh auth status
  3. Confirm you have repository access (purchased kit)
  4. Try with verbose flag: ck new --verbose

Version Information

Current version: 1.2.1

Check version:

ck --version

View help:

ck --help
ck -h

Next Steps

Ready to start? Purchase a kit at ClaudeKit.cc, then run ck new to create your first project.