📦 deps(thirdparty): update snapshots
This commit is contained in:
ci[bot]
@@ -0,0 +1,37 @@
|
||||
---
|
||||
name: brooks-health
|
||||
description: >
|
||||
Combined codebase health dashboard that scores a project across all four quality
|
||||
dimensions — PR quality, architecture, tech debt, and test quality — in a single
|
||||
pass, drawing on twelve classic engineering books.
|
||||
Triggers when: user wants an overall quality assessment, asks "how healthy is this
|
||||
codebase?", "run all the checks", "give me a big-picture quality report", "I need a
|
||||
health score before the release", "what's the overall state of our code?", or wants
|
||||
to onboard a new team with a quality overview.
|
||||
Do NOT trigger for: server health checks, HTTP health endpoints, Kubernetes
|
||||
liveness/readiness probes, database health, or application uptime. Also do not
|
||||
trigger when the user specifically requests only one dimension — use the
|
||||
corresponding focused skill instead (brooks-review / brooks-audit /
|
||||
brooks-debt / brooks-test).
|
||||
---
|
||||
|
||||
# Brooks-Lint — Health Dashboard
|
||||
|
||||
## Setup
|
||||
|
||||
1. Read `../_shared/common.md` for the Iron Law, Project Config, Report Template, and Health Score rules
|
||||
2. Read `../_shared/source-coverage.md` for book-level coverage, exceptions, and tradeoffs
|
||||
3. Read `../_shared/decay-risks.md` for production risk symptom definitions
|
||||
4. Read `../_shared/test-decay-risks.md` for test risk symptom definitions
|
||||
5. Read `health-guide.md` in this directory for the dashboard orchestration process
|
||||
|
||||
## Process
|
||||
|
||||
**If the user has not specified a project or directory:** apply Auto Scope Detection
|
||||
from `../_shared/common.md` to determine the review scope before proceeding.
|
||||
|
||||
1. Run abbreviated scans across all four dimensions (Step 1 of the guide)
|
||||
2. Compute per-dimension and composite Health Scores with weighting (Step 2 of the guide)
|
||||
3. Output the Health Dashboard using the dashboard report template (Step 3 of the guide)
|
||||
|
||||
**Mode line in report:** `Health Dashboard`
|
||||
@@ -0,0 +1,89 @@
|
||||
# Health Dashboard Guide — Mode 5
|
||||
|
||||
**Purpose:** Produce a cross-dimensional health dashboard for the codebase.
|
||||
Every finding must follow the Iron Law: Symptom → Source → Consequence → Remedy.
|
||||
|
||||
---
|
||||
|
||||
## Analysis Process
|
||||
|
||||
### Step 1: Run Lightweight Scan Across Four Dimensions
|
||||
|
||||
For each dimension, run an abbreviated scan using the decay-risks definitions
|
||||
from `_shared/`. Do NOT read the individual mode guide files — use the abbreviated
|
||||
checklists below. Cap each dimension at 3 findings; for Debt: cap at 2 per risk code and 3 across all risk codes.
|
||||
|
||||
**PR dimension (if changes exist):**
|
||||
- Apply Auto Scope Detection (common.md)
|
||||
- Scan for R2 (Change Propagation) and R1 (Cognitive Overload) in the diff
|
||||
|
||||
**Architecture dimension:**
|
||||
- Gather codebase context: read top-level structure, entry points, import statements
|
||||
- Draw a Mermaid dependency graph (follow standard graph rules from common.md)
|
||||
- Scan for R5 (Dependency Disorder): circular deps, upward flows, fan-out > 5
|
||||
- INCLUDE the Mermaid graph in output
|
||||
|
||||
**Debt dimension:**
|
||||
- Scan for all six decay risks (R1-R6) across the codebase
|
||||
- Skip Pain × Spread scoring (use severity tier only)
|
||||
|
||||
**Test dimension:**
|
||||
- Build the Test Suite Map (unit/integration/E2E counts)
|
||||
- Scan for T1 (Test Obscurity) and T2 (Test Brittleness) in test files
|
||||
|
||||
### Step 2: Compute Dashboard Scores
|
||||
|
||||
Each dimension gets its own Health Score (base 100, same deduction rules from common.md).
|
||||
Composite score = weighted average of dimension scores:
|
||||
|
||||
| Dimension | Weight | Rationale |
|
||||
|-----------|--------|-----------|
|
||||
| PR (code quality) | 0.25 | Only applies if changes exist; skip if no diff |
|
||||
| Architecture | 0.30 | Structural issues have highest blast radius |
|
||||
| Debt | 0.25 | Systemic but slower-moving |
|
||||
| Test | 0.20 | Supporting signal |
|
||||
|
||||
If PR dimension is skipped (no changes), redistribute its 0.25 weight proportionally
|
||||
across the remaining three dimensions by dividing each remaining weight by
|
||||
(1 − 0.25) = 0.75. Compute redistribution dynamically — do not hardcode the values.
|
||||
|
||||
**Redistributed weights (PR skipped):**
|
||||
|
||||
| Dimension | Base Weight | Redistributed Weight |
|
||||
|-----------|------------|---------------------|
|
||||
| Architecture | 0.30 | 0.30 / 0.75 = 0.40 |
|
||||
| Debt | 0.25 | 0.25 / 0.75 = 0.33 |
|
||||
| Test | 0.20 | 0.20 / 0.75 = 0.27 |
|
||||
|
||||
### Step 3: Output Dashboard
|
||||
|
||||
Use the dashboard report template below instead of the standard common.md template.
|
||||
|
||||
---
|
||||
|
||||
## Dashboard Report Template
|
||||
|
||||
````markdown
|
||||
# Brooks-Lint Health Dashboard
|
||||
|
||||
**Mode:** Health Dashboard
|
||||
**Scope:** [project name or directory]
|
||||
**Composite Score:** XX/100
|
||||
|
||||
| Dimension | Score | Top Finding |
|
||||
|-----------|-------|------------|
|
||||
| Code Quality | XX/100 | [one-line summary or "Clean"] |
|
||||
| Architecture | XX/100 | [one-line summary or "Clean"] |
|
||||
| Tech Debt | XX/100 | [one-line summary or "Clean"] |
|
||||
| Test Quality | XX/100 | [one-line summary or "Clean"] |
|
||||
|
||||
## Module Dependency Graph
|
||||
[Mermaid graph from architecture scan]
|
||||
|
||||
## Top Findings (max 5 across all dimensions)
|
||||
[Standard Iron Law format, sorted by severity]
|
||||
|
||||
## Recommendation
|
||||
[One paragraph: what to fix first, which dimension needs the most attention,
|
||||
suggest running the full individual skill for the worst dimension]
|
||||
````
|
||||
Reference in New Issue
Block a user