claudekit-cli 1.4.1 → 1.5.1

package/bin/ck.js

@@ -0,0 +1,62 @@
+#!/usr/bin/env node
+
+/**
+ * Wrapper script that detects platform and executes the correct binary
+ * This is the entry point that NPM symlinks to when installing globally
+ */
+
+import { spawn } from "node:child_process";
+import { existsSync } from "node:fs";
+import { dirname, join } from "node:path";
+import { fileURLToPath } from "node:url";
+
+const __dirname = dirname(fileURLToPath(import.meta.url));
+
+// Detect platform and architecture
+const platform = process.platform;
+const arch = process.arch;
+
+// Map to binary filename
+const getBinaryPath = () => {
+	const ext = platform === "win32" ? ".exe" : "";
+
+	const binaryMap = {
+		"darwin-arm64": `ck-darwin-arm64${ext}`,
+		"darwin-x64": `ck-darwin-x64${ext}`,
+		"linux-x64": `ck-linux-x64${ext}`,
+		"win32-x64": `ck-win32-x64${ext}`,
+	};
+
+	const key = `${platform}-${arch}`;
+	const binaryName = binaryMap[key];
+
+	if (!binaryName) {
+		console.error(`❌ Unsupported platform: ${platform}-${arch}`);
+		console.error("Supported platforms: macOS (arm64, x64), Linux (x64), Windows (x64)");
+		process.exit(1);
+	}
+
+	return join(__dirname, binaryName);
+};
+
+const binaryPath = getBinaryPath();
+
+// Check if binary exists
+if (!existsSync(binaryPath)) {
+	console.error(`❌ Binary not found: ${binaryPath}`);
+	console.error("Please report this issue at: https://github.com/claudekit/claudekit-cli/issues");
+	process.exit(1);
+}
+
+// Execute the binary with all arguments
+const child = spawn(binaryPath, process.argv.slice(2), {
+	stdio: "inherit",
+	windowsHide: true,
+});
+
+child.on("exit", (code, signal) => {
+	if (signal) {
+		process.kill(process.pid, signal);
+	}
+	process.exit(code || 0);
+});

package/package.json

@@ -1,15 +1,19 @@
 {
 	"name": "claudekit-cli",
-	"version": "1.4.1",
+	"version": "1.5.1",
 	"description": "CLI tool for bootstrapping and updating ClaudeKit projects",
 	"type": "module",
 	"bin": {
-		"ck": "./dist/index.js"
+		"ck": "./bin/ck.js"
 	},
+	"files": [
+		"bin"
+	],
 	"scripts": {
 		"dev": "bun run src/index.ts >> logs.txt 2>&1",
 		"build": "bun build src/index.ts --outdir dist --target node --external keytar --external @octokit/rest >> logs.txt 2>&1",
 		"compile": "bun build src/index.ts --compile --outfile ck >> logs.txt 2>&1",
+		"compile:binary": "bun build src/index.ts --compile --outfile bin/ck",
 		"test": "bun test >> logs.txt 2>&1",
 		"test:watch": "bun test --watch >> logs.txt 2>&1",
 		"lint": "biome check . >> logs.txt 2>&1",

package/.github/workflows/ci.yml

@@ -1,45 +0,0 @@
-name: CI
-
-on:
-  pull_request:
-    branches:
-      - main
-      - master
-      - dev
-  push:
-    branches:
-      - main
-      - master
-      - dev
-
-jobs:
-  test:
-    name: Test
-    runs-on: ubuntu-latest
-
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-
-      - name: Setup Bun
-        uses: oven-sh/setup-bun@v2
-        with:
-          bun-version: latest
-
-      - name: Install system dependencies
-        run: sudo apt-get update && sudo apt-get install -y libsecret-1-dev
-
-      - name: Install dependencies
-        run: bun install --frozen-lockfile
-
-      - name: Run type check
-        run: bun run typecheck
-
-      - name: Run linter
-        run: bun run lint
-
-      - name: Build
-        run: bun run build
-
-      - name: Run tests
-        run: bun test

package/.github/workflows/claude-code-review.yml

@@ -1,57 +0,0 @@
-name: Claude Code Review
-
-on:
-  pull_request:
-    types: [opened, synchronize]
-    # Optional: Only run on specific file changes
-    # paths:
-    #   - "src/**/*.ts"
-    #   - "src/**/*.tsx"
-    #   - "src/**/*.js"
-    #   - "src/**/*.jsx"
-
-jobs:
-  claude-review:
-    # Optional: Filter by PR author
-    # if: |
-    #   github.event.pull_request.user.login == 'external-contributor' ||
-    #   github.event.pull_request.user.login == 'new-developer' ||
-    #   github.event.pull_request.author_association == 'FIRST_TIME_CONTRIBUTOR'
-
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-      pull-requests: read
-      issues: read
-      id-token: write
-
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 1
-
-      - name: Run Claude Code Review
-        id: claude-review
-        uses: anthropics/claude-code-action@v1
-        with:
-          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
-          prompt: |
-            REPO: ${{ github.repository }}
-            PR NUMBER: ${{ github.event.pull_request.number }}
-
-            Please review this pull request and provide feedback on:
-            - Code quality and best practices
-            - Potential bugs or issues
-            - Performance considerations
-            - Security concerns
-            - Test coverage
-
-            Use the repository's CLAUDE.md for guidance on style and conventions. Be constructive and helpful in your feedback.
-
-            Use `gh pr comment` with your Bash tool to leave your review as a comment on the PR.
-
-          # See https://github.com/anthropics/claude-code-action/blob/main/docs/usage.md
-          # or https://docs.claude.com/en/docs/claude-code/cli-reference for available options
-          claude_args: '--allowed-tools "Bash(gh issue view:*),Bash(gh search:*),Bash(gh issue list:*),Bash(gh pr comment:*),Bash(gh pr diff:*),Bash(gh pr view:*),Bash(gh pr list:*)"'
-

package/.github/workflows/claude.yml

@@ -1,50 +0,0 @@
-name: Claude Code
-
-on:
-  issue_comment:
-    types: [created]
-  pull_request_review_comment:
-    types: [created]
-  issues:
-    types: [opened, assigned]
-  pull_request_review:
-    types: [submitted]
-
-jobs:
-  claude:
-    if: |
-      (github.event_name == 'issue_comment' && contains(github.event.comment.body, '@claude')) ||
-      (github.event_name == 'pull_request_review_comment' && contains(github.event.comment.body, '@claude')) ||
-      (github.event_name == 'pull_request_review' && contains(github.event.review.body, '@claude')) ||
-      (github.event_name == 'issues' && (contains(github.event.issue.body, '@claude') || contains(github.event.issue.title, '@claude')))
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-      pull-requests: read
-      issues: read
-      id-token: write
-      actions: read # Required for Claude to read CI results on PRs
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 1
-
-      - name: Run Claude Code
-        id: claude
-        uses: anthropics/claude-code-action@v1
-        with:
-          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
-
-          # This is an optional setting that allows Claude to read CI results on PRs
-          additional_permissions: |
-            actions: read
-
-          # Optional: Give a custom prompt to Claude. If this is not specified, Claude will perform the instructions specified in the comment that tagged it.
-          # prompt: 'Update the pull request description to include a summary of changes.'
-
-          # Optional: Add claude_args to customize behavior and configuration
-          # See https://github.com/anthropics/claude-code-action/blob/main/docs/usage.md
-          # or https://docs.claude.com/en/docs/claude-code/cli-reference for available options
-          # claude_args: '--allowed-tools Bash(gh pr:*)'
-

package/.github/workflows/release.yml

@@ -1,102 +0,0 @@
-name: Release
-
-on:
-  push:
-    branches:
-      - main
-
-permissions:
-  contents: write
-  issues: write
-  pull-requests: write
-  id-token: write
-
-jobs:
-  release:
-    name: Release
-    runs-on: ubuntu-latest
-
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-          persist-credentials: false
-
-      - name: Setup Bun
-        uses: oven-sh/setup-bun@v2
-        with:
-          bun-version: latest
-
-      - name: Install system dependencies
-        run: sudo apt-get update && sudo apt-get install -y libsecret-1-dev
-
-      - name: Install dependencies
-        run: bun install --frozen-lockfile
-
-      - name: Run type check
-        run: bun run typecheck
-
-      - name: Run linter
-        run: bun run lint
-
-      - name: Run tests
-        run: bun test
-
-      - name: Build
-        run: bun run build
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: 'lts/*'
-
-      - name: Release
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
-        run: npx semantic-release
-
-      - name: Notify Discord
-        if: ${{ success() }}
-        uses: actions/github-script@v7
-        env:
-          DISCORD_WEBHOOK_URL: ${{ secrets.DISCORD_WEBHOOK_URL }}
-        with:
-          github-token: ${{ secrets.GITHUB_TOKEN }}
-          script: |
-            if (!process.env.DISCORD_WEBHOOK_URL) {
-              core.warning('DISCORD_WEBHOOK_URL not set, skipping Discord notification.')
-              return
-            }
-
-            const { owner, repo } = context.repo
-            const { data: releases } = await github.rest.repos.listReleases({
-              owner,
-              repo,
-              per_page: 1,
-            })
-
-            if (!releases.length) {
-              core.warning('No releases found, skipping Discord notification.')
-              return
-            }
-
-            const release = releases[0]
-            const description = (release.body || '').slice(0, 4000)
-
-            await fetch(process.env.DISCORD_WEBHOOK_URL, {
-              method: 'POST',
-              headers: { 'Content-Type': 'application/json' },
-              body: JSON.stringify({
-                username: 'ClaudeKit Release Bot',
-                embeds: [
-                  {
-                    title: `Release ${release.name || release.tag_name}`,
-                    url: release.html_url,
-                    description: description || 'No changelog available.',
-                    timestamp: release.created_at,
-                  },
-                ],
-              }),
-            })

package/.releaserc.json

@@ -1,17 +0,0 @@
-{
-	"branches": ["main"],
-	"plugins": [
-		"@semantic-release/commit-analyzer",
-		"@semantic-release/release-notes-generator",
-		"@semantic-release/changelog",
-		"@semantic-release/npm",
-		[
-			"@semantic-release/git",
-			{
-				"assets": ["package.json", "CHANGELOG.md"],
-				"message": "chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}"
-			}
-		],
-		"@semantic-release/github"
-	]
-}

package/.repomixignore

@@ -1,15 +0,0 @@
-docs/*
-plans/*
-assets/*
-dist/*
-coverage/*
-build/*
-ios/*
-android/*
-
-.claude/*
-.serena/*
-.pnpm-store/*
-.github/*
-.dart_tool/*
-.idea/*

package/AGENTS.md

@@ -1,217 +0,0 @@
-# AGENTS.md
-
-This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
-
-## Project Overview
-
-...
-
-## Project Structure
-
-- `docs/` - Product requirements and wireframes
-  - `product-overview-pdr.md` - Complete product requirements document (Vietnamese)
-  - `code-standards.md` - Code standards and conventions
-  - `codebase-summary.md` - Codebase summary & structure
-  - `project-roadmap.md` - Project roadmap
-- `plans/` - Implementation plans
-  - `templates/` - Implementation plan templates
-  - `reports/` - Implementation reports
-
-## Key Features to Implement
-
-...
-
-## Development Commands
-
-...
-
-## Architecture Guidelines
-
-...
-
----
-
-## Role & Responsibilities
-
-Your role is to analyze user requirements, delegate tasks to appropriate sub-agents, and ensure cohesive delivery of features that meet specifications and architectural standards.
-
-### Orchestration Protocol
-
-#### Sequential Chaining
-Chain subagents when tasks have dependencies or require outputs from previous steps:
-- **Planning → Implementation → Testing → Review**: Use for feature development
-- **Research → Design → Code → Documentation**: Use for new system components
-- Each agent completes fully before the next begins
-- Pass context and outputs between agents in the chain
-
-#### Parallel Execution
-Spawn multiple subagents simultaneously for independent tasks:
-- **Code + Tests + Docs**: When implementing separate, non-conflicting components
-- **Multiple Feature Branches**: Different agents working on isolated features
-- **Cross-platform Development**: iOS and Android specific implementations
-- **Careful Coordination**: Ensure no file conflicts or shared resource contention
-- **Merge Strategy**: Plan integration points before parallel execution begins
-
-### Core Responsibilities
-
-#### 1. Code Implementation
-- Before you start, delegate to `planner` agent to create a implementation plan with TODO tasks in `./plans` directory.
-- When in planning phase, use multiple `researcher` agents in parallel to conduct research on different relevant technical topics and report back to `planner` agent to create implementation plan.
-- Write clean, readable, and maintainable code
-- Follow established architectural patterns
-- Implement features according to specifications
-- Handle edge cases and error scenarios
-- **DO NOT** create new enhanced files, update to the existing files directly.
-- **[IMPORTANT]** After creating or modifying code file, run `flutter analyze <path/to/file>` to check for any compile errors.
-
-#### 2. Testing
-- Delegate to `tester` agent to run tests and analyze the summary report.
-  - Write comprehensive unit tests
-  - Ensure high code coverage
-  - Test error scenarios
-  - Validate performance requirements
-- Tests are critical for ensuring code quality and reliability, **DO NOT** ignore failing tests just to pass the build.
-- **IMPORTANT:** Always fix failing tests follow the recommendations and delegate to `tester` agent to run tests again, only finish your session when all tests pass.
-
-#### 3. Code Quality
-- After finish implementation, delegate to `code-reviewer` agent to review code.
-- Follow coding standards and conventions
-- Write self-documenting code
-- Add meaningful comments for complex logic
-- Optimize for performance and maintainability
-
-#### 4. Integration
-- Always follow the plan given by `planner` agent
-- Ensure seamless integration with existing code
-- Follow API contracts precisely
-- Maintain backward compatibility
-- Document breaking changes
-- Delegate to `docs-manager` agent to update docs in `./docs` directory if any.
-
-#### 5. Debugging
-- When a user report bugs or issues on the server or a CI/CD pipeline, delegate to `debugger` agent to run tests and analyze the summary report.
-- Read the summary report from `debugger` agent and implement the fix.
-- Delegate to `tester` agent to run tests and analyze the summary report.
-- If the `tester` agent reports failed tests, fix them follow the recommendations.
-
----
-
-## Context Management & Anti-Rot Guidelines
-
-**REMEMBER: Everything is Context Engineering!** 
-Subagents have their own context, delegate tasks to them using file system whenever possible.
-
-### Context Refresh Protocol
-To prevent context degradation and maintain performance in long conversations:
-
-#### Agent Handoff Refresh Points
-- **Between Agents**: Reset context when switching between specialized agents
-- **Phase Transitions**: Clear context between planning → implementation → testing → review phases
-- **Document Generation**: Use fresh context for creating plans, reports, and documentation
-- **Error Recovery**: Reset context after debugging sessions to avoid confusion
-
-#### Information Handoff Structure
-When delegating to agents, provide only essential context:
-```markdown
-## Task Summary
-- **Objective**: [brief description]
-- **Scope**: [specific boundaries]
-- **Critical Context**: [requirements, constraints, current state]
-- **Reference Files**: [relevant file paths and line numbers - don't include full content]
-- **Success Criteria**: [clear acceptance criteria]
-```
-
-#### Context Health Guidelines
-- **Prioritize Recent Changes**: Emphasize recent modifications over historical data
-- **Use References Over Content**: Link to files instead of including full content
-- **Summary Over Details**: Provide bullet points instead of verbose explanations
-
-### Agent Interaction Best Practices
-- Each agent should complete its task and provide a focused summary report
-- Avoid circular dependencies between agents  
-- Use clear "handoff complete" signals when transitioning
-- Include only task-relevant context in agent instructions
-- Pass plan file path across subagents
-
----
-
-## Project Documentation Management
-
-### Roadmap & Changelog Maintenance
-- **Project Roadmap** (`./docs/development-roadmap.md`): Living document tracking project phases, milestones, and progress
-- **Project Changelog** (`./docs/project-changelog.md`): Detailed record of all significant changes, features, and fixes
-- **System Architecture** (`./docs/system-architecture.md`): Detailed record of all significant changes, features, and fixes
-- **Code Standards** (`./docs/code-standards.md`): Detailed record of all significant changes, features, and fixes
-
-### Automatic Updates Required
-- **After Feature Implementation**: Update roadmap progress status and changelog entries
-- **After Major Milestones**: Review and adjust roadmap phases, update success metrics
-- **After Bug Fixes**: Document fixes in changelog with severity and impact
-- **After Security Updates**: Record security improvements and version updates
-- **Weekly Reviews**: Update progress percentages and milestone statuses
-
-### Documentation Triggers
-The `project-manager` agent MUST update these documents when:
-- A development phase status changes (e.g., from "In Progress" to "Complete")
-- Major features are implemented or released
-- Significant bugs are resolved or security patches applied
-- Project timeline or scope adjustments are made
-- External dependencies or breaking changes occur
-
-### Update Protocol
-1. **Before Updates**: Always read current roadmap and changelog status
-2. **During Updates**: Maintain version consistency and proper formatting
-3. **After Updates**: Verify links, dates, and cross-references are accurate
-4. **Quality Check**: Ensure updates align with actual implementation progress
-
----
-
-## Development Rules
-
-### General
-- **File Size Management**: Keep individual code files under 500 lines for optimal context management
-  - Split large files into smaller, focused components
-  - Use composition over inheritance for complex widgets
-  - Extract utility functions into separate modules
-  - Create dedicated service classes for business logic
-- You ALWAYS follow these principles: **YANGI (You Aren't Gonna Need It) - KISS (Keep It Simple, Stupid) - DRY (Don't Repeat Yourself)**
-- Use `context7` mcp tools for exploring latest docs of plugins/packages
-- Use `senera` mcp tools for semantic retrieval and editing capabilities
-- Use `psql` bash command to query database for debugging.
-- Use `eyes_vision_analysis` tool of `human` mcp server to read and analyze images.
-- **[IMPORTANT]** Follow the codebase structure and code standards in `./docs` during implementation
-- **[IMPORTANT]** When you finish the implementation, send a full summary report to Discord channel with `./.claude/send-discord.sh 'Your message here'` script (remember to escape the string).
-- **[IMPORTANT]** Do not just simulate the implementation or mocking them, always implement the real code.
-
-### Subagents
-Delegate detailed tasks to these subagents according to their roles & expertises:
-- Use file system (in markdown format) to hand over reports in `./plans/reports` directory from agent to agent with this file name format: `YYMMDD-from-agent-name-to-agent-name-task-name-report.md`.
-- Use `planner` agent to plan for the implementation plan using templates in `./plans/templates/` (`planner` agent can spawn multiple `researcher` agents in parallel to explore different approaches with "Query Fan-Out" technique).
-- Use `database-admin` agent to run tests and analyze the summary report.
-- Use `tester` agent to run tests and analyze the summary report.
-- Use `debugger` agent to collect logs in server or github actions to analyze the summary report.
-- Use `code-reviewer` agent to review code according to the implementation plan.
-- Use `docs-manager` agent to update docs in `./docs` directory if any (espcially for `./docs/codebase-summary.md` when significant changes are made).
-- Use `git-manager` agent to commit and push code changes.
-- Use `project-manager` agent for project's progress tracking, completion verification & TODO status management.
-- **[IMPORTANT]** Always delegate to `project-manager` agent after completing significant features, major milestones, or when requested to update project documentation.
-**IMPORTANT:** You can intelligently spawn multiple subagents **in parallel** or **chain them sequentially** to handle the tasks efficiently.
-
-### Code Quality Guidelines
-- Read and follow codebase structure and code standards in `./docs`
-- Don't be too harsh on code linting, but make sure there are no syntax errors and code are compilable
-- Prioritize functionality and readability over strict style enforcement and code formatting
-- Use reasonable code quality standards that enhance developer productivity
-- Use try catch error handling & cover security standards
-- Use `code-reviewer` agent to review code after every implementation
-
-### Pre-commit/Push Rules
-- Run linting before commit
-- Run tests before push (DO NOT ignore failed tests just to pass the build or github actions)
-- Keep commits focused on the actual code changes
-- **DO NOT** commit and push any confidential information (such as dotenv files, API keys, database credentials, etc.) to git repository!
-- NEVER automatically add AI attribution signatures like:
-  "🤖 Generated with [Claude Code]"
-  "Co-Authored-By: Claude noreply@anthropic.com"
-  Any AI tool attribution or signature
-- Create clean, professional commit messages without AI references. Use conventional commit format.