claude-code-kit 0.47.0__tar.gz → 0.48.0__tar.gz

{claude_code_kit-0.47.0 → claude_code_kit-0.48.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.47.0",
+      "version": "0.48.0",
       "license": "MIT",
       "keywords": ["sdlc", "agents", "orchestration", "quality-gates", "workflow", "scaffold", "cookiecutter"]
     }

{claude_code_kit-0.47.0 → claude_code_kit-0.48.0}/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-kit",
-  "version": "0.47.0",
+  "version": "0.48.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.47.0 → claude_code_kit-0.48.0}/CHANGELOG.md

@@ -4,6 +4,27 @@ 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.48.0] — 2026-06-27
+
+**Adopt the partition-for-coverage review methodology from `alibaba/open-code-review`** (Apache-2.0,
+re-derived in prose — not vendored). A detailed read of open-code-review showed most of its methodology
+(multi-axis dimensions, line-level grounding + re-verify, severity, multi-model review) was already in
+the kit; the one genuine gap was **complete file coverage on large changesets**, where AI reviewers
+silently skip files. The kit's existing guidance covered *depth allocation* (hotspots) but not
+*coverage guarantee*.
+
+- **`skills/code-review-and-quality`** — new "Cover Every Changed File: Partition, Plan, Then Weight
+  Depth" section: enumerate changed files deterministically (the diff is the checklist of record),
+  bundle related files into one review unit, review each bundle in isolated context concurrently,
+  plan-before-deep-pass on big diffs, and reconcile so every file gets a verdict. The existing hotspot
+  section is reframed as the *depth* step that follows coverage. New coverage item in the review
+  checklist.
+- **`agents/sdlc-code-reviewer`** — "Cover Before You Score" note + a Coverage checklist category
+  (every changed file accounted for; related files reviewed as bundles).
+
+Coverage = every file accounted for; depth = how hard you looked, allocated next. No count/anchor
+changes (skill + agent extended, none added). Version 0.47.0 → 0.48.0.
+
 ## [0.47.0] — 2026-06-27
 
 **Adopt 5 verified agentic-engineering patterns from an exhaustive review of the Alibaba GitHub org**

{claude_code_kit-0.47.0 → claude_code_kit-0.48.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: claude-code-kit
-Version: 0.47.0
+Version: 0.48.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

{claude_code_kit-0.47.0 → claude_code_kit-0.48.0}/agents/sdlc-code-reviewer.md

@@ -38,8 +38,22 @@ Apply every applicable rule from these documents when reviewing code. Reference
 
 Review all code changes produced by the Developer (Agent 4). Check for correctness, security, performance, and adherence to standards. Gate the pipeline — **testing CANNOT start without your approval** (CLAUDE.md §2).
 
+## Cover Before You Score (large changesets)
+
+Before weighting depth, guarantee coverage. Take the changed-file list from the diff
+(`git diff --name-only`) as the **checklist of record** — every file is reviewed or explicitly marked
+out-of-scope with a reason; the model never decides which files "seem worth" looking at. Review related
+files as **bundles in isolated context** (use parallel lanes for very large changesets per
+`.claude/rules/mandatory-workflow.md`), then reconcile so no file is silently skipped. Allocate extra
+depth to hotspots/coupled files **after** coverage is assured. This is the partition-for-coverage
+discipline in the `code-review-and-quality` skill.
+
 ## Review Checklist
 
+### Coverage
+- [ ] Every changed file is accounted for — reviewed or explicitly marked out-of-scope (no silent skips)
+- [ ] Related files reviewed together as bundles (function+tests, schema+migration, paired config/i18n)
+
 ### Correctness
 - [ ] Logic matches the spec exactly
 - [ ] All acceptance criteria from the spec are implemented

{claude_code_kit-0.47.0 → claude_code_kit-0.48.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "claude-code-kit"
-version = "0.47.0"
+version = "0.48.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"

{claude_code_kit-0.47.0 → claude_code_kit-0.48.0}/skills/code-review-and-quality/SKILL.md

@@ -80,9 +80,45 @@ For detailed profiling and optimization, see `performance-optimization`. Does th
 - Any missing pagination on list endpoints?
 - Any large objects created in hot paths?
 
+## Cover Every Changed File: Partition, Plan, Then Weight Depth
+
+On a large changeset the signature failure of an AI reviewer is **silently skipping files** —
+reviewing a plausible subset while implying the whole. Coverage is a *mechanical* property: guarantee
+it with engineering, not model discretion, **before** deciding where to spend depth (next section).
+
+- **Enumerate deterministically.** Take the changed-file list from the diff itself and treat it as the
+  checklist of record — every file is reviewed or explicitly marked out-of-scope with a reason. The
+  model never decides which files "seem worth" looking at.
+  ```bash
+  git diff --name-only <base>...<head>   # the coverage checklist — nothing falls off it
+  ```
+- **Bundle related files into one review unit.** Group files that must be understood together — a
+  function and its tests, an interface and its implementations, paired translation/config files
+  (`messages.en.json` + `messages.zh.json`), a schema and its migration. A bundle reviewed as a unit
+  catches cross-file contract breaks that a one-file-at-a-time pass misses.
+- **Review each bundle in isolated context, concurrently.** Give each bundle its own focused context
+  (its own sub-agent/lane) instead of streaming the whole changeset through one window —
+  divide-and-conquer keeps quality stable on very large changes and parallelizes naturally (the
+  `.claude/rules/mandatory-workflow.md` lane model, within the Brooks's-law caution in
+  `.claude/rules/tool-design.md` §7). Context gathered for one bundle is for *understanding only* — a
+  discovery in file B doesn't become a comment on the unrelated file A.
+- **Plan before the deep pass on a big diff.** For a large change, first emit a one-paragraph change
+  summary plus risk points ranked high→low and the context each needs, then review against that plan.
+  A cheap planning pass beats diving in file-by-file blind.
+- **Reconcile at the end.** Merge the per-bundle findings and confirm every file on the enumerated list
+  got a verdict. **Coverage = every file accounted for; depth = how hard you looked, allocated next.**
+
+> Partition-for-coverage (deterministic file selection, related-file bundling, isolated-context
+> concurrent review, plan-phase for large diffs) is a stack-agnostic adaptation of the hybrid
+> architecture in the Apache-2.0
+> [`alibaba/open-code-review`](https://github.com/alibaba/open-code-review) — engineering guarantees
+> coverage, the model supplies judgment. Re-derived in prose; not vendored.
+
 ## Where to Focus: Change Hotspots & Coupling
 
-You can't give every line equal attention — on a large change or an unfamiliar codebase, spend the most scrutiny where defects actually cluster. The project's own git history surfaces this for free, no special tooling required:
+Once every changed file is accounted for (above), allocate *depth* — you can't give every line equal
+attention; on a large change or an unfamiliar codebase, spend the most scrutiny where defects actually
+cluster. The project's own git history surfaces this for free, no special tooling required:
 
 - **Hotspots (churn × complexity).** Files that change *often* **and** are *large/complex* carry the most risk. List the frequently-changed files and weight review toward the complex ones among them — a rarely-touched file is usually stable, while a hotspot edited in *this* change deserves extra correctness and test scrutiny.
   ```bash
@@ -306,6 +342,7 @@ For a full pre-add evaluation of a specific candidate (maintenance/bus-factor, l
 
 ### Context
 - [ ] I understand what this change does and why
+- [ ] Every changed file is accounted for — reviewed or explicitly marked out-of-scope (no silent skips)
 - [ ] For a large/unfamiliar change, I focused review on the riskiest files (hotspots, coupled files)
 
 ### Correctness

{claude_code_kit-0.47.0 → claude_code_kit-0.48.0}/src/claude_kit/__init__.py

@@ -7,4 +7,4 @@ Docker): ``claude-kit init`` asks ordered questions and lays down ``CLAUDE.md``
 as a plugin. Extensibility is data-driven via the ``catalog/`` (stacks, profiles, MCP).
 """
 
-__version__ = "0.47.0"
+__version__ = "0.48.0"