This release includes breaking changes for platform teams planning a safe upgrade.
✓ No known CVEs patched in this version
Topics
+14 more
Summary
AI summaryUpdates π Fixed, π§ Changed, and π¦ Install / Upgrade across a mixed release.
Full changelog
A focused patch on top of v1.0.0: 28 files of documentation accuracy, skill-guide tightening, and developer-experience fixes. No behavior or API changes β all skill logic is identical to v1.0.0. Existing users can upgrade at any time with zero migration risk.
π Fixed
Documentation bugs that broke workflows
- Broken
Manual Installcommands inREADME.md(Claude Code & Gemini CLI sections).cp -r skills/ ~/.claude/skills/brooks-lintsilently produced a nestedbrooks-lint/skills/directory instead of installing the skills. Fixed with an explicitmkdir -ppluscp -r skills/*. - Fictional
gemini skills reloadcommand inGEMINI.mdβ replaced with/quit+ relaunch, which is how Gemini CLI actually picks up local skill edits. bug_report.mdversion query β thecat ~/.claude/plugins/.../package.jsonplaceholder couldn't be pasted and run. Replaced with a/plugin listinstruction that actually works.
Wrong citations in skill guides
- Characterization Tests β
Ch. 8corrected toCh. 13intest-guide.md(Feathers, Working Effectively with Legacy Code). - Over-engineering source β removed the stale βEvils of Duplication (YAGNI corollary)β entry (that chapter is DRY, not YAGNI). Now correctly cites
Topic 4: Good-Enough Softwarefrom The Pragmatic Programmer. - Slow-suite T6 source β tightened from vague βTest suite design principlesβ to Meszaros' explicit
Slow Tests (p. 253); now aligned acrosstest-guide.mdandtest-decay-risks.md.
Structural errors in skill guides
pr-review-guide.mdOutput section was placed beforeStep 7, which broke the Analysis Process flow. Moved to its correct position after Step 7 so the steps are contiguous.debt-guide.mddeclared "three steps" but actually shipped four (Step 1,2,2b,3). PromotedStep 2b: Classify Debt IntenttoStep 3, renumbered the final step toStep 4, and fixed the preamble.architecture-guide.mdStep 2 hint referenced a stale β οΈ symbol that wasn't in the example. Now correctly cites the actual-.->|circular|Mermaid edge.common.mdAuto Scope Detection was missing the Health Dashboard branch. Also removed a hard-coded"PR Review Step 7"label β now uses the named"Quick Test Check"step, so future renumbering won't silently rot the reference.
Contribution workflow
CONTRIBUTING.mdβ the "Three Ways to Contribute" section actually shipped with four paths (the fourth was unnumbered and floated between Β§2 and Β§3). Renamed to "Four Ways", promotedAdding a new decay riskto a numberedΒ§4, and reordered by difficulty (1 β 2 β 3 β 4).
Gallery accuracy
docs/gallery.mdβ fixed a self-contradicting"Critical / Scheduled"cell in the Debt Summary Table (the schema expects a single classification). Now reads"Mixed (1 Critical + 1 Scheduled)". Harmonized the~9 minvs~542sinconsistency for the same data point. The preamble now honestly says"lightly abridged β some Consequence lines trimmed"instead of claiming zero editing.
π§ Changed
SKILL.md Process convention β skeleton + guide citation
v1.0.0 required SKILL.md Process sections to mirror the guide's step list 1:1. In practice this forced readers β and Claude running the skill β to read the same list twice. v1.0.1 switches to a high-level skeleton (3β6 items) that cites guide Step ranges inline, e.g. Scan decay risks (Steps 1β7 of the guide).
- The guide owns the detailed numbered steps; the skeleton is for orientation.
- Counts no longer need to match β
CLAUDE.md,AGENTS.md, andGEMINI.mdall document the new rule. npm run validatestill enforces guide step continuity (sub-steps like2a/6ballowed) and SKILL.md Process-section presence.- All five
SKILL.mdProcess sections have been updated to the new format.
Slash-command wrapper hardening
All five commands/*.md now declare allowed-tools: Skill. The command turn can only dispatch the skill; once invoked the skill retains full tool access. Result: fewer permission prompts on first use.
Typographic consistency
- Unified
Pain Γ Spread(UnicodeΓwith spaces) acrossbrooks-debt/SKILL.md,health-guide.md,evals.json, anddocs/gallery.md. Previously a mix ofPain x Spread(ASCII) andPainΓSpread(no spaces). - Unified
Ch. Xchapter citations (ASCII space after the period) acrosstest-decay-risks.md,test-guide.md,architecture-guide.md, andpr-review-guide.md.
README.md Roadmap
Added a Current state callout so historical milestones like v0.3: Eight Brooks dimensions and v0.4: Six-book framework aren't misread as today's feature set.
health-guide.md dashboard template
Added the **Mode:** Health Dashboard field and standard --- section dividers so the dashboard report aligns visually with the other four skill reports.
π¦ Install / Upgrade
Claude Code plugin marketplace
```
/plugin marketplace update
/plugin install brooks-lint@brooks-lint-marketplace
```
Manual install β Claude Code
```bash
mkdir -p ~/.claude/skills/brooks-lint
cp -r skills/* ~/.claude/skills/brooks-lint/
```
Manual install β Gemini CLI
```bash
mkdir -p ~/.gemini/skills/brooks-lint
cp -r skills/* ~/.gemini/skills/brooks-lint/
```
New users
See the README for the full install matrix (Claude Code, Gemini CLI, Codex CLI).
π Available Skills
| Command | Description |
|---------|-------------|
| `/brooks-review` | PR code review β decay risks with Iron Law findings |
| `/brooks-audit` | Architecture audit β dependency graph, layering, Conway's Law |
| `/brooks-debt` | Tech debt assessment β Pain Γ Spread prioritization |
| `/brooks-test` | Test quality review β brittleness, mock abuse, coverage illusions |
| `/brooks-health` | Health dashboard β composite score across all four dimensions |
All skills are behaviourally unchanged from v1.0.0.
π Credits
Consistency pass driven by a repo-wide documentation audit. Full diff: v1.0.0...v1.0.1.
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
About Brooks-Lint
All releases βRelated context
Related tools
Beta — feedback welcome: [email protected]