v1.2.4

fix(update): guard kit materialization behind ccsk-project detection

ccsk update no longer scatters kit files into arbitrary directories. The global CLI self-update still runs everywhere, but kit templates + agents/skills + plugin are re-materialized only in an existing ccsk project (a dir with .ccsk/ or materialized .claude/skills/ccsk-*), or when you opt in with --force or an explicit --path <dir>.

• Drop commander's . default on --path so an explicit --path . reads as deliberate intent.
• Add --force to override the guard for the current directory.
• isCcskProject() detection (directory check, not bare existence).

v1.2.3

Materialize agents & skills into the project by default. ccsk init now copies the 12 agents + 16 skills into .claude/{agents,skills} so the kit is self-contained and visible per-project — no plugin install or trust dialog needed. Skills become /ccsk-<name> commands, agents stay bare (planner, code-reviewer); a namespace transform rewrites the plugin ccsk: references so cross-refs and subagent delegation resolve.

Use ccsk init --plugin for the legacy plugin delivery (colon commands /ccsk:plan, nothing copied). The post-install summary now counts what actually landed, and ccsk update refreshes a materialized project in place.

v1.2.2

Keep CLAUDE.md pure on rtk init. ccsk init now snapshots and restores CLAUDE.md around the external rtk init binary (which otherwise mutates it), leaving the .claude/settings.json hook intact. RTK guidance is re-introduced cleanly as a dedicated .claude/rules/rtk-instructions.md referenced by a single contract-style @-import (idempotent).

Boxed install summary. After copy, ccsk init prints a rounded-box summary of the installed roster — agents, skills, commands, and rules with counts — so you can see exactly what landed. NO_COLOR-safe.

v1.2.1

Full Changelog: v1.2.0...v1.2.1

v1.2.0

Full Changelog: v1.1.1...v1.2.0

v1.1.1

Hardened kit fetch to prevent stale-kit installs (fixes 'no slash commands after init'): fallback version derived from package.json, and cache provenance markers so partial/legacy clones are re-fetched. Kit commands are now /ccsk-plan, /ccsk-build, /ccsk-loop.

v1.1.0

Full Changelog: v1.0.15...v1.1.0

v1.0.15 — Kit ships /scaffold + npm provenance

What's new

• Kit ships /scaffold. ccsk-org/ccsk-kit v1.0.1 replaces _dot_claude/commands/ccsk-bootstrap.md with scaffold.md. ccsk init resolves the latest kit tag, so new installs now receive /scaffold — matching the CLI's next-steps output (completes the rename started in 101c914).
• npm provenance. publish.yml now publishes with --provenance, producing the verified/provenance badge on npm.
• Quality. Bundled the scaffold-remediation work: Vitest coverage for copy-kit, remove-kit, gitignore-sync, donation-qr (26 tests), file splits, and refactors.
• Docs. codebase-summary + project-roadmap updated to record the kit-side scaffold completion.

Signed commit + signed tag (verified).

v1.0.14 - ADD Integration + Scaffold

What's Changed

New Features

• ADD Installation: Optional ADD (AI-Driven Development) installation step during ccsk init
• --no-add flag: Explicitly skip ADD installation
• Renamed /ccsk-bootstrap → /scaffold: Cleaner command name

Other Changes

• Added .add/ to ccsk-managed gitignore block
• Added TinDang to contributors

Full Changelog: v1.0.13...v1.0.14

v1.0.13 - Single Kit Architecture

What's Changed

• Single kit architecture — simplified from multi-kit to single-kit model
• Install tracking with optional email capture
• Donation flow integration with VietQR
• Streamlined init command flow

Full Changelog: v1.0.12...v1.0.13