Codebase intelligence for AI and humans: code health scores, auto-generated docs, git analytics, dead code detection, and architectural decisions via MCP.
Python aicode-complexitycode-healthcode-intelligencecode-qualitydead-codedeveloper-toolsdocumentationgit-analyticsmcpopen-sourcepythonrefactoringstatic-analysistechnical-debt
fix(ci): regenerate the plugin prompt and bundled changelog from their sources (#1762)
Raghav Chamadiya197f72243188
diff --git a/packages/cli/src/repowise/cli/agent_targets/_data/codex_prompts/repowise-impacted-tests.md b/packages/cli/src/repowise/cli/agent_targets/_data/codex_prompts/repowise-impacted-tests.mdindex 0e8aedd62..d13f66532 100644--- a/packages/cli/src/repowise/cli/agent_targets/_data/codex_prompts/repowise-impacted-tests.md+++ b/packages/cli/src/repowise/cli/agent_targets/_data/codex_prompts/repowise-impacted-tests.md@@ -41,8 +41,8 @@ repowise impacted-tests main..HEAD --format list | xargs pytestheaded "NOT coverage-backed", each carrying a `via` marker: `changed-test`(the changed file is itself a test), `call-graph` or `import-graph` (a testfile that reaches it, no ingest needed), or `filename-pattern` (a name-shaped- guess). Report- them as candidates. Only `via: coverage` proves a test executed the change.+ guess). Report them as candidates. Only `via: coverage` proves a test+ executed the change.- A file none of those can speak to is "unknown, run the full suite".- For a whole-change defect-risk score, use `/prompts:repowise-risk`. For per-fileblast radius / `tests_to_run`, use the `get_risk` MCP tool.diff --git a/packages/core/src/repowise/core/upgrade/_data/CHANGELOG.md b/packages/core/src/repowise/core/upgrade/_data/CHANGELOG.mdindex 107140c1b..4b9ba1015 100644--- a/packages/core/src/repowise/core/upgrade/_data/CHANGELOG.md+++ b/packages/core/src/repowise/core/upgrade/_data/CHANGELOG.md@@ -16,43 +16,55 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0- **A test-to-code map that needs no coverage report.** The per-test map onlyever existed if you ingested a coverage report with contexts, so on mostrepositories `tests_to_run` was empty, `impacted_tests` said "run the full- suite", and `untested_hotspot` fell back to matching filenames. The dependency- graph already records which test files import which source files, and that+ suite", and `untested_hotspot` fell back to matching filenames. The call graph+ already records which test can execute into which source file, and thatrelation now answers when the measured one cannot. It is labelled `inferred`everywhere, never blended with measured coverage, and never turned into apercentage. Nothing is stored: it is a bounded walk over rows already indexed,- measured at 27 ms once per health run on a 3,700-file repository.+ measured at 63 ms once per health run on a 3,700-file repository.++ The call graph is the primary signal and the import graph the weaker fallback,+ which is a measured choice rather than a preference. Dogfooded against a real+ `coverage run --contexts=test` over a slice where per-test attribution is+ complete, with both sides seeing the same 37 test files: walking imports one+ hop scored 72.1% precision at 19.5% recall, walking calls three hops scored+ 91.7% at 27.7%, and dropping the one call-resolution strategy that only+ matches a name repo-wide (`global_unique`) took that to 95.7% at no cost to+ recall. Unioning the two is worse than either lead, so the import tier is+ spent only on the files the call graph says nothing about, where it answers+ one more of them at no loss of precision.New fields: `tests_to_run_basis` on `get_risk`'s directive(`measured` / `inferred` / `none`), `basis` and a `status: "inferred"` on`get_change_risk`'s `impacted_tests`, and a `via` marker on every- `repowise impacted-tests` candidate.+ `repowise impacted-tests` candidate saying which tier answered.### Changed-- **`untested_hotspot` stops accusing files that six tests import.** With no+- **`untested_hotspot` stops accusing files that the tests run.** With nocoverage ingested it fired on any hotspot without a *paired test file*, whichis a filename convention, so a suite that names its tests for behaviour- satisfied nothing. A test reaching the file in the import graph now suppresses- it too. On this repository five of the six worst bug-magnet files had no test- named for them and read as untested; the sixth, `analysis/health/engine.py`,- was called tested because the convention matched `distill/test_engine.py` on- basename alone. The same floor now runs under `get_risk`'s `missing_tests`,- which had two separate filename heuristics that disagreed.-- Measured on repowise's own index: 74 of its 110 standing `untested_hotspot`- findings are cleared, 18 of them graded critical. The persisted- `has_test_file` widens to match, so the file table stops labelling those same- files "untested" while the biomarker says nothing.+ satisfied nothing. A test whose calls reach the file now suppresses it too. On+ this repository five of the six worst bug-magnet files had no test named for+ them and read as untested; the sixth, `analysis/health/engine.py`, was called+ tested because the convention matched `distill/test_engine.py` on basename+ alone. The same floor now runs under `get_risk`'s `missing_tests`, which had+ two separate filename heuristics that disagreed.++ Measured on repowise's own index, against the 80 standing `untested_hotspot`+ findings the filename convention leaves behind: the call graph clears 32 of+ them, 22 graded high and 3 critical, where a one-hop import walk clears 11.+ The persisted `has_test_file` widens to match, so the file table stops+ labelling those same files "untested" while the biomarker says nothing.Both stored values are wrong on an index built before this, so- `HEALTH_ANALYZER_VERSION` moves to 2 and the next `repowise update` with+ `HEALTH_ANALYZER_VERSION` moves to 3 and the next `repowise update` withchanged files re-scores health rather than waiting out the decay timer.- **`repowise impacted-tests --format json` renames `guessed_tests` to`inferred_tests`.** The bucket no longer holds only filename guesses, so the- old name described the wrong thing; each entry carries `via`- (`import-graph` or `filename-pattern`) to say which tier answered.+ old name described the wrong thing; each entry carries `via` (`call-graph`,+ `import-graph` or `filename-pattern`) to say which tier answered.---diff --git a/plugins/claude-code/commands/impacted-tests.md b/plugins/claude-code/commands/impacted-tests.mdindex 1f8f0919c..e637a85be 100644--- a/plugins/claude-code/commands/impacted-tests.md+++ b/plugins/claude-code/commands/impacted-tests.md@@ -40,9 +40,10 @@ repowise impacted-tests main..HEAD --format list | xargs pytest"no tests needed" result.- A changed file with no coverage rows gets *candidates* instead, in a tableheaded "NOT coverage-backed", each carrying a `via` marker: `changed-test`- (the changed file is itself a test), `import-graph` (a test file that reaches- it, no ingest needed), or `filename-pattern` (a name-shaped guess). Report- them as candidates. Only `via: coverage` proves a test executed the change.+ (the changed file is itself a test), `call-graph` or `import-graph` (a test+ file that reaches it, no ingest needed), or `filename-pattern` (a name-shaped+ guess). Report them as candidates. Only `via: coverage` proves a test+ executed the change.- A file none of those can speak to is "unknown, run the full suite".- For a whole-change defect-risk score, use `/repowise:risk`. For per-fileblast radius / `tests_to_run`, use the `get_risk` MCP tool.diff --git a/plugins/shared/commands/impacted-tests.md b/plugins/shared/commands/impacted-tests.mdindex 499737c0f..fb6c929c1 100644--- a/plugins/shared/commands/impacted-tests.md+++ b/plugins/shared/commands/impacted-tests.md@@ -41,9 +41,10 @@ repowise impacted-tests main..HEAD --format list | xargs pytest"no tests needed" result.- A changed file with no coverage rows gets *candidates* instead, in a tableheaded "NOT coverage-backed", each carrying a `via` marker: `changed-test`- (the changed file is itself a test), `import-graph` (a test file that reaches- it, no ingest needed), or `filename-pattern` (a name-shaped guess). Report- them as candidates. Only `via: coverage` proves a test executed the change.+ (the changed file is itself a test), `call-graph` or `import-graph` (a test+ file that reaches it, no ingest needed), or `filename-pattern` (a name-shaped+ guess). Report them as candidates. Only `via: coverage` proves a test+ executed the change.- A file none of those can speak to is "unknown, run the full suite".- For a whole-change defect-risk score, use `{{cmd:risk}}`. For per-fileblast radius / `tests_to_run`, use the `get_risk` MCP tool.