add-dep
Vet a new or changed third-party dependency for license, provenance, and supply-chain risk before any install runs.
Read-only 3-metric governance glance — override rate, small-lane rate, sprint low-confidence ratio — each with a trend arrow vs. the prior 20-commit window.
> /plugin marketplace add arbiterForge/codeArbiterHow it fires
How this command gets triggered: by you, by Claude, or both.
/metricsContext preview
What this command does when you run it.
Read-only 3-metric governance glance — override rate, small-lane rate, sprint low-confidence ratio — each with a trend arrow vs. the prior 20-commit window.
description: Read-only 3-metric governance glance — override rate, small-lane rate, sprint low-confidence ratio — each with a trend arrow vs. the prior 20-commit window. argument-hint: "[--window N]"
A bare-numbers summary of the three governance-health metrics that `_metricslib.py` tracks across commit windows. Each metric shows its value for the **current** 20-commit window and a direction arrow (↑/↓/→) relative to the immediately preceding window.
This is NOT a second `{{CMD:audit}}` packet. It prints numbers and arrows only — no verbatim override lines, no commit list, no file write. Use it to spot a trend at a glance; reach for `{{CMD:audit}}` when you need the full evidentiary packet.
1. **Invoke the helper.** Call the thin entry hook `metrics.py`, which wraps `compute` from `_metricslib.py`. Resolve the interpreter once by presence — `PY=python3; { command -v python3 >/dev/null 2>&1 && python3 --version >/dev/null 2>&1; } || PY=python` — never `python3 … || python …`, which reruns the helper on any nonzero exit and reports the second run's code instead of the first's (#577). Pass `{{PROJECT_DIR}}` as `--root`. If `--window N` was supplied, pass it through as `--window N`; otherwise omit it (the helper applies the default of 20).
"$PY" "{{PLUGIN_ROOT}}/hooks/metrics.py" --root "{{PROJECT_DIR}}"> **`ensure_ascii` note — do not remove this.** `metrics.py` calls `json.dumps` > with its default `ensure_ascii=True`. This ASCII-escapes the arrow glyphs > (↑↓→) in the subprocess stdout, which avoids a `UnicodeEncodeError` on Windows > `cp1252` consoles that cannot encode those code-points raw. The rendered output > you present to the user (step 2 below) uses the real glyphs — they are written > by the assistant, not piped through the subprocess stdout. Do NOT add > `ensure_ascii=False` here.
With a custom window size:
"$PY" "{{PLUGIN_ROOT}}/hooks/metrics.py" --root "{{PROJECT_DIR}}" --window NReplace `N` with the integer the user supplied.
2. **Render the glance.** Parse the returned JSON dict. Present exactly three lines, one per metric, in this order:
override rate: <current> <arrow> (prior: <prior>) small-lane rate: <current> <arrow> (prior: <prior>) sprint low-conf ratio: <current> <arrow> (prior: <prior>)
`"n/a"` — render it literally (e.g. `n/a ↑`).
this briefly below the table so the reader does not have to guess.
3. **State the window.** Append one line naming the window size used, e.g. `Window: 20 commits (default)` or `Window: N commits (--window N)`.
`git status` MUST be unchanged after a run.
`sprint_low_conf_ratio`. MUST NOT emit verbatim override log lines, verbatim triage entries, commit lists, or any other content from the governance logs.
absent logs (counts return 0 / ratio returns `"n/a"`); surface the degraded values as-is rather than blocking.
the error and stop — do not fabricate metric values.
When you can't trust yourself with your code base, trust Arbiter.
Repo: arbiterForge/codeArbiter
Vet a new or changed third-party dependency for license, provenance, and supply-chain risk before any install runs.
Report the health of Architecture Decision Records — aged, unchallenged, supersession candidates, unresolved CONFIRM-NN. Read-only.
Author a numbered, dated, user-attributed Architecture Decision Record under .codearbiter/decisions/.
Assemble the governance record for a range — commits, overrides, ADRs, sprint auto-decisions, open questions, checkpoint findings — into one dated audit…
Lightweight Q&A about the project — answer from context and return, no routing, no state change.
Periodic multi-reviewer sweep of the whole codebase — surfaces a triaged checkpoint report.