claude-code-kit 0.21.0__tar.gz → 0.23.0__tar.gz

{claude_code_kit-0.21.0 → claude_code_kit-0.23.0}/.claude-plugin/marketplace.json

@@ -10,7 +10,7 @@
       "name": "claude-kit",
       "source": "./",
       "description": "Cookiecutter-style scaffolder for an autonomous Claude Code SDLC config (no app code, no Docker): install CLAUDE.md + .claude/ (rules, the profile's agents/skills, hooks, artifact templates) + optional .mcp.json, then run /sdlc to drive spec → review → build → test → security → ship through profile-aware quality gates, working memory, and a self-improving learnings loop.",
-      "version": "0.21.0",
+      "version": "0.23.0",
       "license": "MIT",
       "keywords": ["sdlc", "agents", "orchestration", "quality-gates", "workflow", "scaffold", "cookiecutter"]
     }

{claude_code_kit-0.21.0 → claude_code_kit-0.23.0}/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-kit",
-  "version": "0.21.0",
+  "version": "0.23.0",
   "description": "Cookiecutter-style scaffolder for an autonomous Claude Code SDLC config (no app code, no Docker). `claude-kit init` asks ordered questions and installs CLAUDE.md + .claude/ (rules, the profile's agents/skills, hooks, artifact templates) + optional .mcp.json; run /sdlc to drive spec → review → build → test → security → ship through profile-aware quality gates with working memory and a self-improving learnings loop.",
   "author": {
     "name": "Arjunsingh Yadav",

{claude_code_kit-0.21.0 → claude_code_kit-0.23.0}/CHANGELOG.md

@@ -4,6 +4,83 @@ All notable changes to claude-kit are documented here. The format follows
 [Keep a Changelog](https://keepachangelog.com/), and the project uses
 [semantic versioning](https://semver.org/).
 
+## [0.23.0] — 2026-06-23
+
+**PR2 of the phased hardening review: structural single-source-of-truth for hooks, and plugin/CLI
+parity that fails loud instead of silently degrading.**
+
+### Changed
+
+- **Hooks are now generated from one registry.** The two previously hand-maintained static hook files —
+  the plugin's `hooks/hooks.json` and the no-pip starter `templates/settings.json` — are now generated
+  from `src/claude_kit/hooks.py` (`HOOK_REGISTRY` + per-channel membership data) via
+  `scripts/gen_hooks.py`. They had already drifted (the starter was missing `load-autonomy`, the PR1
+  `jq`-degradation prefix, and used a slightly different block message). A drift test
+  (`gen_hooks.py --check`, run in the suite) fails the build if either file is hand-edited.
+  - The installed per-profile `.claude/settings.json` (built by `build_settings`) is **byte-identical**
+    to before — pure refactor, verified against `origin/main`.
+  - `hooks/hooks.json` is **semantically identical** to before (reflowed to canonical 2-space JSON; no
+    hook added, removed, or reordered).
+  - `templates/settings.json` changes only by refreshing its two inline Bash guards to the registry
+    versions (gaining the `command -v jq … || exit 0` no-jq degradation + aligned message); same hook
+    membership.
+- **`guard-kubectl-delete` is now declared data.** It moves into a `PLUGIN_ONLY_HOOKS` map (with a
+  `reason`) — the single documented exception to "the registry is the source of truth" — instead of
+  being a silent hand-edit in `hooks.json`.
+
+### Fixed
+
+- **Plugin/CLI parity: `/claude-kit:init` requires the CLI and fails loud.** The command no longer
+  silently falls back to the thin `scripts/init.sh` scaffolder when neither `claude-kit` nor `ckit` is
+  on PATH — it stops and instructs `pipx install claude-code-kit` (or `pip install …`). The shell
+  fallback is now opt-in only (`CLAUDE_KIT_BASIC=1`) and prints a loud "degraded, no-resolution
+  install; upgrade/diff won't work" warning. README onboarding documents the CLI requirement.
+
+## [0.22.0] — 2026-06-23
+
+**Critical-correctness hardening (PR1 of a phased review): a non-destructive `init` merge that no longer
+deletes your files, a CI guard against doc/version/count drift, stricter config validation, pinned
+third-party MCP versions, and several P2 fixes.**
+
+### Fixed
+
+- **Data-loss bug in `init` merge mode.** Re-running `claude-kit init` over an existing `.claude/`
+  (the default `merge` mode) used to `shutil.rmtree` whole kit-managed directories (`rules/`,
+  `skills/<name>/`, `skills/_references/`), silently deleting any file you had added under them.
+  `init` now reconciles non-destructively via the new `upgrader.merge_install`, which reuses the
+  owner-aware upgrade logic: kit/overlay files are refreshed (user-modified ones backed up to
+  `.claude-kit.bak-N/` first), user-editable files are sidecar'd, kit/overlay orphans are pruned, and
+  **files the kit doesn't track are never touched**. An untracked hand-rolled `.claude/` is migrated
+  safely too (collisions are backed up). `--force` / `overwrite` remains the only destructive path.
+- **`README.claude-sdlc.md` is now user-editable.** `init` no longer hard-overwrites it; it honours
+  `--force` and otherwise writes a `.claude-kit` sidecar, and `upgrade` protects it like `CLAUDE.md`.
+- **Documentation/version drift.** `SECURITY.md` supported-version, the `/sdlc` skill's `standard`
+  gate row (added `contract-clear`), and the README hook count (16 → 17) corrected.
+
+### Added
+
+- **`scripts/check_docs_consistency.py`** — a fail-loud guard (run in tests + CI) that re-derives the
+  facts and asserts the docs agree: version parity across `pyproject.toml`, `__init__.py`, both plugin
+  manifests, the latest `CHANGELOG` heading and `SECURITY.md`; component counts (agents / rules / core
+  & collection skills / hook scripts / MCP servers) against every number the docs quote; and the
+  profile→gate tables in `README.md` + `skills/sdlc/SKILL.md` against `catalog/profiles.yaml`.
+- **Stricter `--config` / selection validation.** A bare `mcp: github` (or `teams: …`) string is
+  normalised to a one-element list instead of being iterated character-by-character; malformed shapes,
+  unknown config keys, an unknown `frontend_language` for the chosen framework, and an unknown `scope`
+  now fail loudly with a clear message (`Selection.from_dict(strict=True)` + `catalog.resolve` checks).
+
+### Changed
+
+- **Pinned MCP server package versions.** `catalog/mcp.yaml` replaces moving `@latest` / implicit-latest
+  `npx` tags with exact version pins (snapshot 2026-06-23) for reproducible, supply-chain-aware installs;
+  the deprecated official GitHub/Postgres reference servers are flagged. README notes that MCP servers
+  are third-party code.
+- **Planned CLI commands exit non-zero.** `package-org-pack`, `install-org-pack`, and
+  `research import-sources` now exit `2` (still announcing "planned") instead of a silent success-`0`.
+- **Inline guard hooks degrade without `jq`.** The `rm -rf` / push-to-main / secrets inline guards (in
+  both the plugin `hooks.json` and the CLI registry) now no-op when `jq` is absent, matching the
+  script-backed guards and the SECURITY.md promise.
+
 ## [0.21.0] — 2026-06-22
 
 **Add two stack-collection skills — `cron-and-scheduled-jobs` (scheduled/recurring jobs across Kubernetes

{claude_code_kit-0.21.0 → claude_code_kit-0.23.0}/CONTRIBUTING.md

@@ -38,11 +38,15 @@ locally, and how to release.
   *when* to use it. Add it to the relevant profile(s) in `catalog/profiles.yaml`.
 - **Rule** → add `rules/<name>.md`; cross-reference siblings as `.claude/rules/<name>.md`.
 - **Hook** → add a script to `hooks/scripts/`, register it in the `HOOK_REGISTRY` in
-  `src/claude_kit/hooks.py`, wire it in `hooks/hooks.json` (plugin), and list its id in the relevant
-  profile's `hooks:`. (Exception: the agent-side capture hooks `capture-learnings[-catchup|-stop]` are
-  **not** profile-listed — they're installed by the init-time `capture_mode` choice via
-  `catalog/capture.yaml` + `catalog._apply_capture_mode`. One script, three triggers, dispatched by an
-  arg.)
+  `src/claude_kit/hooks.py`, and list its id in the relevant profile's `hooks:`. To surface it in the
+  plugin and/or the no-pip starter, add its id to `PLUGIN_HOOK_IDS` / `STARTER_HOOK_IDS` (same module),
+  then **run `python scripts/gen_hooks.py`** to regenerate `hooks/hooks.json` and
+  `templates/settings.json` — **never hand-edit those two files** (a drift test, `gen_hooks.py --check`,
+  fails the build if they diverge from the registry). A plugin-only hook (no CLI scaffold equivalent,
+  e.g. `guard-kubectl-delete`) goes in `PLUGIN_ONLY_HOOKS` with a `reason` instead of the registry.
+  (Exception: the agent-side capture hooks `capture-learnings[-catchup|-stop]` are **not** profile-listed
+  — they're installed by the init-time `capture_mode` choice via `catalog/capture.yaml` +
+  `catalog._apply_capture_mode`. One script, three triggers, dispatched by an arg.)
 - **Stack** (framework / database) → a **data change**: add an entry to `catalog/stacks.yaml`
   (`label`, `overlay_rules`, optional `overlay_agents`, `skills`, `stack_dir`, `commands`) and create
   `templates/stacks/<stack_dir>/rules/<name>.md` (+ `agents/` for a database). Mark not-yet-ready

{claude_code_kit-0.21.0 → claude_code_kit-0.23.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: claude-code-kit
-Version: 0.21.0
+Version: 0.23.0
 Summary: Cookiecutter-style scaffolder for an autonomous Claude Code SDLC configuration (no app code, no Docker). Asks ordered questions and installs CLAUDE.md + .claude/ (rules, the chosen profile's agents/skills, hooks, artifact templates) + optional .mcp.json; run /sdlc to drive spec → review → build → test → security → ship through profile-aware quality gates, working memory, and a self-improving learnings loop.
 Project-URL: Homepage, https://github.com/ajyadav013/claude-kit
 Project-URL: Repository, https://github.com/ajyadav013/claude-kit
@@ -82,7 +82,7 @@ Quick start) for the full breakdown of any row.
 | 🧱 **Stacks & overlays** | Stack-agnostic core + **10** overlay rule sets (React · FastAPI · Go · Postgres · Mongo) wired to your exact commands, incl. a full React design system |
 | 🎚️ **Profiles, scopes & org** | **3** rigor profiles · **3** scopes · **5** autonomy levels · **7** org packs + **10** policy rules |
 | 🧠 **Memory & learning** | Working memory across context compaction + a cost-aware learnings loop (`capture_mode`) so the same mistake isn't repeated |
-| 🛠️ **Hooks & guards** | **16** event hooks — blocking safety guards vs. advisory warnings — that no-op gracefully without `jq` |
+| 🛠️ **Hooks & guards** | **17** event hooks — blocking safety guards vs. advisory warnings — that no-op gracefully without `jq` |
 | 📦 **Distribution & lifecycle** | Plugin **and** pip from one source, **9** ready MCP fragments, and edit-preserving `upgrade` |
 | ♻️ **Reuse-first by design** | Adopt-only-the-new reviews, opt-in LLM/AI security (OWASP LLM Top 10), a worked example + self-test matrix |
 
@@ -110,6 +110,12 @@ Then, inside any project you want the pipeline to manage:
 /sdlc Add a CSV export button to the reports page
 ```
 
+> **`/claude-kit:init` requires the Python CLI** (`pipx install claude-code-kit`, or `pip install
+> claude-code-kit`) — it's what resolves your stack/profile/MCP catalog and records `init-options.json`
+> for safe `upgrade`/`diff`. If the CLI isn't on PATH the command stops and tells you to install it
+> rather than doing a partial install. (A degraded, no-resolution shell scaffolder is available only by
+> explicitly setting `CLAUDE_KIT_BASIC=1`; `upgrade`/`diff` won't work against it.)
+
 > `/sdlc` is a **project skill** installed by `init`, so it becomes available after the restart. The
 > plugin also exposes `/claude-kit:sdlc <task>`, which works immediately (no restart needed).
 
@@ -306,7 +312,7 @@ need.
 
 <br>
 
-- **16 event hook scripts** in [`hooks/`](hooks/) enforce the pipeline outside the model —
+- **17 event hook scripts** in [`hooks/`](hooks/) enforce the pipeline outside the model —
   `guard-secrets`, `guard-destructive-git`, `lint-fix`, `type-check`, and `validate-settings` run
   deterministically.
 - **Advisory, never-blocking warnings** — `warn-llm-io`, `warn-large-edits`, `warn-missing-tests`, and
@@ -325,6 +331,10 @@ need.
   (`claude-kit` / `ckit` / `claude-sdlc`) generate identical config.
 - **Catalog-driven extensibility** — adding a stack, framework, database, profile, MCP server, or org
   pack is a [`catalog/`](catalog/) YAML edit, never a code change; 9 MCP server fragments ship ready.
+- **MCP servers are third-party** — each fragment runs an external package or hosted endpoint that
+  claude-kit references but does not vendor or audit; the `npx` commands are **pinned to an exact
+  version** (not `@latest`) for reproducible, supply-chain-aware installs. Review a server's source and
+  license before enabling it, and bump pins deliberately. See [`SECURITY.md`](SECURITY.md).
 - **Safe, edit-preserving upgrades** — `upgrade` refreshes kit/overlay files via per-file `owner` +
   checksum, never clobbers your edits, backs up changes, and restores deleted files (`diff` previews
   first).

{claude_code_kit-0.21.0 → claude_code_kit-0.23.0}/README.md

@@ -55,7 +55,7 @@ Quick start) for the full breakdown of any row.
 | 🧱 **Stacks & overlays** | Stack-agnostic core + **10** overlay rule sets (React · FastAPI · Go · Postgres · Mongo) wired to your exact commands, incl. a full React design system |
 | 🎚️ **Profiles, scopes & org** | **3** rigor profiles · **3** scopes · **5** autonomy levels · **7** org packs + **10** policy rules |
 | 🧠 **Memory & learning** | Working memory across context compaction + a cost-aware learnings loop (`capture_mode`) so the same mistake isn't repeated |
-| 🛠️ **Hooks & guards** | **16** event hooks — blocking safety guards vs. advisory warnings — that no-op gracefully without `jq` |
+| 🛠️ **Hooks & guards** | **17** event hooks — blocking safety guards vs. advisory warnings — that no-op gracefully without `jq` |
 | 📦 **Distribution & lifecycle** | Plugin **and** pip from one source, **9** ready MCP fragments, and edit-preserving `upgrade` |
 | ♻️ **Reuse-first by design** | Adopt-only-the-new reviews, opt-in LLM/AI security (OWASP LLM Top 10), a worked example + self-test matrix |
 
@@ -83,6 +83,12 @@ Then, inside any project you want the pipeline to manage:
 /sdlc Add a CSV export button to the reports page
 ```
 
+> **`/claude-kit:init` requires the Python CLI** (`pipx install claude-code-kit`, or `pip install
+> claude-code-kit`) — it's what resolves your stack/profile/MCP catalog and records `init-options.json`
+> for safe `upgrade`/`diff`. If the CLI isn't on PATH the command stops and tells you to install it
+> rather than doing a partial install. (A degraded, no-resolution shell scaffolder is available only by
+> explicitly setting `CLAUDE_KIT_BASIC=1`; `upgrade`/`diff` won't work against it.)
+
 > `/sdlc` is a **project skill** installed by `init`, so it becomes available after the restart. The
 > plugin also exposes `/claude-kit:sdlc <task>`, which works immediately (no restart needed).
 
@@ -279,7 +285,7 @@ need.
 
 <br>
 
-- **16 event hook scripts** in [`hooks/`](hooks/) enforce the pipeline outside the model —
+- **17 event hook scripts** in [`hooks/`](hooks/) enforce the pipeline outside the model —
   `guard-secrets`, `guard-destructive-git`, `lint-fix`, `type-check`, and `validate-settings` run
   deterministically.
 - **Advisory, never-blocking warnings** — `warn-llm-io`, `warn-large-edits`, `warn-missing-tests`, and
@@ -298,6 +304,10 @@ need.
   (`claude-kit` / `ckit` / `claude-sdlc`) generate identical config.
 - **Catalog-driven extensibility** — adding a stack, framework, database, profile, MCP server, or org
   pack is a [`catalog/`](catalog/) YAML edit, never a code change; 9 MCP server fragments ship ready.
+- **MCP servers are third-party** — each fragment runs an external package or hosted endpoint that
+  claude-kit references but does not vendor or audit; the `npx` commands are **pinned to an exact
+  version** (not `@latest`) for reproducible, supply-chain-aware installs. Review a server's source and
+  license before enabling it, and bump pins deliberately. See [`SECURITY.md`](SECURITY.md).
 - **Safe, edit-preserving upgrades** — `upgrade` refreshes kit/overlay files via per-file `owner` +
   checksum, never clobbers your edits, backs up changes, and restores deleted files (`diff` previews
   first).

{claude_code_kit-0.21.0 → claude_code_kit-0.23.0}/catalog/mcp.yaml

@@ -1,16 +1,26 @@
 # claude-kit optional MCP integrations. Selected servers are written into a project-root `.mcp.json`
 # ONLY when chosen at init (default: none). Configs use ${ENV} placeholders — no credentials are ever
 # generated. Fill the referenced env vars (e.g. in your shell or .env) before using a server.
+#
+# SUPPLY CHAIN: every server below is THIRD-PARTY code (an npx package or a hosted HTTP endpoint) with
+# its own maintainers, trust, and licensing model — claude-kit only references it, never vendors or
+# audits it. The `npx -y <pkg>@<version>` commands are pinned to an exact version (snapshot 2026-06-23)
+# rather than a moving `@latest`, so an install is reproducible and a fresh upstream release can't
+# silently change what runs. Bump these deliberately (and review the changelog) — do not switch back
+# to `@latest`. See SECURITY.md and the README "MCP integrations" note.
 
 version: 1
 
 servers:
   github:
     label: "GitHub (issues, PRs, repos)"
+    # NOTE: the official @modelcontextprotocol/server-github npm package is archived/deprecated upstream
+    # (GitHub now ships a Go `github-mcp-server`). Pinned to its last published version for a stable
+    # install; switch to the maintained server in a future kit release if you need newer features.
     config:
       type: stdio
       command: npx
-      args: ["-y", "@modelcontextprotocol/server-github"]
+      args: ["-y", "@modelcontextprotocol/server-github@2025.4.8"]
       env:
         GITHUB_PERSONAL_ACCESS_TOKEN: "${GITHUB_PERSONAL_ACCESS_TOKEN}"
   linear:
@@ -23,22 +33,25 @@ servers:
     config:
       type: stdio
       command: npx
-      args: ["-y", "mcp-atlassian"]
+      args: ["-y", "mcp-atlassian@2.1.0"]
       env:
         JIRA_URL: "${JIRA_URL}"
         JIRA_API_TOKEN: "${JIRA_API_TOKEN}"
   postgres:
     label: "PostgreSQL (query the database)"
+    # NOTE: @modelcontextprotocol/server-postgres is archived/deprecated upstream; pinned to its last
+    # published version for a stable install. Consider a maintained Postgres MCP server going forward.
     config:
       type: stdio
       command: npx
-      args: ["-y", "@modelcontextprotocol/server-postgres", "${DATABASE_URL}"]
+      args:
+        ["-y", "@modelcontextprotocol/server-postgres@0.6.2", "${DATABASE_URL}"]
   mongodb:
     label: "MongoDB (query the database)"
     config:
       type: stdio
       command: npx
-      args: ["-y", "mongodb-mcp-server"]
+      args: ["-y", "mongodb-mcp-server@1.13.0"]
       env:
         MDB_MCP_CONNECTION_STRING: "${MONGODB_URI}"
   playwright:
@@ -46,7 +59,7 @@ servers:
     config:
       type: stdio
       command: npx
-      args: ["-y", "@playwright/mcp@latest"]
+      args: ["-y", "@playwright/mcp@0.0.76"]
   docs:
     label: "Docs / Context7 (live library docs)"
     config:
@@ -61,7 +74,7 @@ servers:
   # source is FSL-1.1-Apache-2.0 (source-available; converts to Apache-2.0 two years after each
   # release) — flagged in the label like the repowise AGPL note; this entry references only the
   # OAuth-hosted service, not the source. Self-hosted/token alternative (instead of the http url):
-  #   command: npx, args: ["-y", "@sentry/mcp-server@latest"], env: SENTRY_ACCESS_TOKEN: "${SENTRY_ACCESS_TOKEN}".
+  #   command: npx, args: ["-y", "@sentry/mcp-server@0.36.0"], env: SENTRY_ACCESS_TOKEN: "${SENTRY_ACCESS_TOKEN}".
   sentry:
     label: "Sentry (error monitoring / issue triage; source-available FSL-1.1)"
     config:

{claude_code_kit-0.21.0 → claude_code_kit-0.23.0}/commands/init.md

@@ -6,21 +6,35 @@ allowed-tools: Bash, Read, Glob
 
 Install the claude-kit autonomous-SDLC configuration into the current project.
 
-**Prefer the full Python CLI** (it runs the ordered prompts, resolves the stack/profile/MCP catalog,
+**The Python CLI is required.** It runs the ordered prompts, resolves the stack/profile/MCP catalog,
 installs overlay rules + agents, assembles `settings.json`, and records `init-options.json` for safe
-upgrades). Check whether it's on PATH and use it, passing through `$ARGUMENTS`:
+upgrades (`claude-kit upgrade` / `diff`). Check whether it's on PATH and use it, passing through
+`$ARGUMENTS`:
 
 ```
 command -v claude-kit >/dev/null 2>&1 && claude-kit init $ARGUMENTS \
-  || { command -v ckit >/dev/null 2>&1 && ckit init $ARGUMENTS; }
+  || { command -v ckit >/dev/null 2>&1 && ckit init $ARGUMENTS \
+  || echo "CKIT_CLI_MISSING"; }
 ```
 
-If neither `claude-kit` nor `ckit` is installed, fall back to the **thin** bundled scaffolder (it
-copies the full payload with no stack/profile resolution — a superset install; suggest the user
-`pip install claude-code-kit` afterwards for the catalog-driven experience):
+**If the output is `CKIT_CLI_MISSING`, STOP — do not scaffold anything.** Neither `claude-kit` nor
+`ckit` is installed. Tell the user the CLI is required and how to install it, then have them re-run
+`/claude-kit:init`. Do **not** silently fall back to a partial install:
+
+- Recommended: `pipx install claude-code-kit`
+- Or: `pip install claude-code-kit`
+
+**Escape hatch (advanced, opt-in only).** A thin shell scaffolder exists for locked-down environments
+where installing the CLI is impossible. It copies the full payload as a **superset** with **no**
+stack/profile/MCP resolution, and `claude-kit upgrade` / `diff` will **not** work against it. Use it
+**only** if the user has explicitly opted in by setting `CLAUDE_KIT_BASIC=1`:
 
 ```
-bash "${CLAUDE_PLUGIN_ROOT}/scripts/init.sh" $ARGUMENTS
+if [ "${CLAUDE_KIT_BASIC:-0}" = "1" ]; then
+  bash "${CLAUDE_PLUGIN_ROOT}/scripts/init.sh" $ARGUMENTS
+else
+  echo "set CLAUDE_KIT_BASIC=1 to use the degraded no-CLI scaffolder (the CLI is the supported path)"
+fi
 ```
 
 If `${CLAUDE_PLUGIN_ROOT}` is not set (running from a source checkout), locate `scripts/init.sh` in

claude_code_kit-0.23.0/hooks/hooks.json

@@ -0,0 +1,106 @@
+{
+  "hooks": {
+    "SessionStart": [
+      {
+        "matcher": "",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "bash \"${CLAUDE_PLUGIN_ROOT}/hooks/scripts/load-continuity.sh\""
+          },
+          {
+            "type": "command",
+            "command": "bash \"${CLAUDE_PLUGIN_ROOT}/hooks/scripts/load-learnings.sh\""
+          },
+          {
+            "type": "command",
+            "command": "bash \"${CLAUDE_PLUGIN_ROOT}/hooks/scripts/load-autonomy.sh\""
+          },
+          {
+            "type": "command",
+            "command": "bash \"${CLAUDE_PLUGIN_ROOT}/hooks/scripts/capture-learnings.sh\" catchup"
+          }
+        ]
+      }
+    ],
+    "PreToolUse": [
+      {
+        "matcher": "Bash",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "command -v jq >/dev/null 2>&1 || exit 0; CMD=$(jq -r '.tool_input.command'); if echo \"$CMD\" | grep -qE 'rm[[:space:]]+-[^[:space:]]*r[^[:space:]]*f'; then echo 'BLOCKED: rm -rf is disabled by claude-kit. Move to trash or delete specific paths explicitly.' >&2; exit 2; fi"
+          },
+          {
+            "type": "command",
+            "command": "command -v jq >/dev/null 2>&1 || exit 0; CMD=$(jq -r '.tool_input.command'); if echo \"$CMD\" | grep -qE 'git[[:space:]]+push.*[[:space:]:](main|master)([[:space:]]|$)'; then echo 'BLOCKED: refusing to push to main/master — use a feature branch and a PR.' >&2; exit 2; fi"
+          },
+          {
+            "type": "command",
+            "command": "bash \"${CLAUDE_PLUGIN_ROOT}/hooks/scripts/guard-destructive-git.sh\""
+          },
+          {
+            "type": "command",
+            "command": "bash \"${CLAUDE_PLUGIN_ROOT}/hooks/scripts/guard-secrets.sh\""
+          },
+          {
+            "type": "command",
+            "command": "bash \"${CLAUDE_PLUGIN_ROOT}/hooks/scripts/guard-kubectl-delete.sh\""
+          }
+        ]
+      },
+      {
+        "matcher": "Edit|Write",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "bash \"${CLAUDE_PLUGIN_ROOT}/hooks/scripts/warn-shared-modules.sh\""
+          },
+          {
+            "type": "command",
+            "command": "bash \"${CLAUDE_PLUGIN_ROOT}/hooks/scripts/warn-llm-io.sh\""
+          },
+          {
+            "type": "command",
+            "command": "bash \"${CLAUDE_PLUGIN_ROOT}/hooks/scripts/warn-sensitive-files.sh\""
+          }
+        ]
+      },
+      {
+        "matcher": "Write",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "bash \"${CLAUDE_PLUGIN_ROOT}/hooks/scripts/validate-settings.sh\""
+          }
+        ]
+      }
+    ],
+    "Stop": [
+      {
+        "matcher": "",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "bash \"${CLAUDE_PLUGIN_ROOT}/hooks/scripts/lint-fix.sh\""
+          },
+          {
+            "type": "command",
+            "command": "bash \"${CLAUDE_PLUGIN_ROOT}/hooks/scripts/type-check.sh\""
+          }
+        ]
+      }
+    ],
+    "SessionEnd": [
+      {
+        "matcher": "",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "bash \"${CLAUDE_PLUGIN_ROOT}/hooks/scripts/capture-learnings.sh\" end"
+          }
+        ]
+      }
+    ]
+  }
+}

{claude_code_kit-0.21.0 → claude_code_kit-0.23.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "claude-code-kit"
-version = "0.21.0"
+version = "0.23.0"
 description = "Cookiecutter-style scaffolder for an autonomous Claude Code SDLC configuration (no app code, no Docker). Asks ordered questions and installs CLAUDE.md + .claude/ (rules, the chosen profile's agents/skills, hooks, artifact templates) + optional .mcp.json; run /sdlc to drive spec → review → build → test → security → ship through profile-aware quality gates, working memory, and a self-improving learnings loop."
 readme = "README.md"
 requires-python = ">=3.9"