-
-
Notifications
You must be signed in to change notification settings - Fork 90
feat(enrichment): Revert-recurrence detector #1514
Copy link
Copy link
Closed
Labels
gittensor:featureGittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.Gittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.gittensor:priorityMaintainer-selected Gittensor priority — scores a 1.5x multiplier.Maintainer-selected Gittensor priority — scores a 1.5x multiplier.
Description
Metadata
Metadata
Assignees
Labels
gittensor:featureGittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.Gittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.gittensor:priorityMaintainer-selected Gittensor priority — scores a 1.5x multiplier.Maintainer-selected Gittensor priority — scores a 1.5x multiplier.
Projects
StatusShow more project fields
Done
Context
A REES (review-enrichment service) analyzer. Tier: solid.
Detects: The PR re-introduces code in a region that was previously reverted/hot-fixed out — a strong signal it's re-treading a known-bad path.
Data source: GitHub REST: GET /commits?path= for history + GET /commits/{sha} for each revert commit's patch; intersect reverted line-ranges with this PR's added-line ranges. Free, contents:read.
This is heavy/external/historical analysis the no-checkout headless
claude --printreviewer cannot do; the REES returns it as a brief block the engine splices into the review (additive + fail-safe).Implementation (established pattern, all inside
review-enrichment/)BriefFindingskey insrc/types.tssrc/analyzers/<name>.ts— pure, injectfetchfor testssrc/brief.tsANALYZERS registrysrc/render.tsnode:testunits againstdist/+ a live smoke against the real data sourceDeliverables
Parent: #1499