Dormant Feature Scanner
Paste any public GitLab URL to discover which disabled features are ready to revive. Every finding is verified against live external evidence, not training-data guesses.
Your codebase has features you already paid for, but never shipped
NECRO scans your GitLab commit history to find disabled features, then checks whether the original kill reason still applies today. Most teams discover 4–8 revivable features per scan.
Paste GitLab URL
Any public GitLab repo. Agent Builder autonomously assesses history depth before scanning.
Verify, Not Just Find
Gemini 3 Flash checks if the kill constraint still applies today, live external evidence, not guesses.
One-Click Revival
Create a GitLab issue or Draft MR with full revival checklist, auto-assigned to the engineer who disabled it.
Necrosis Scanner: Dead Code Detection
The mirror of revival. Paste a public GitLab URL to find code that was deprecated or disabled but never removed, necrotic tissue still attached to a living codebase. Every finding is checked against live callers (GitLab blobs search) before NECRO suggests excising it. We never recommend deleting load-bearing code.
search_blobs + per-line blame dating
Feature Kill Timeline: kills by month
Recommendation Breakdown
How NECRO classified each dormant feature
Revival Feasibility Distribution
How easy are detected features to revive?
Kill Reason Categories
Why features were disabled
Cost-Benefit Matrix
Bubble = demand signals · top-left = easiest wins · ● revive ● investigate
No repositories monitored yet.
Add a GitLab URL above to start autonomous scanning.
Revived Feature Audit Trails
This panel logs all GitLab issue actions and merge requests created by NECRO's Google Cloud Agent Builder coordinator.
Revival issues created via NECRO will appear here. Create a GitLab issue from any 'Revive Now' feature card to log it.
Stop Rebuilding Features You Already Built
NECRO finds disabled features in your GitLab repo, verifies whether the kill reason still exists, and surfaces the ones ready to revive, with cited evidence
WHAT is it?
NECRO is a multi-agent forensics system that scans your GitLab commit history using Google Cloud Agent Builder and GitLab MCP to find features, flags, and merged work that was disabled or shelved, then determines which ones are ready to revive based on whether the original kill reason still applies today.
WHY does it matter?
Dead code and dormant features are two sides of the same problem. Decisions expire. The constraint that killed a feature in 2022 may have dissolved in 2023, but nobody checks. Code stays dead. Deprecated handlers pile up. Teams reinvent shelved work from scratch. Industry estimates: $140K+ wasted per year per 25-developer team, across 30M+ GitLab users globally.
HOW does it work?
- Phase 0: Agent Builder autonomously assesses the repo: calls list_commits via MCPToolset, decides optimal scan depth, streams reasoning live.
- Phase 1: 6 forensic strategies detect dead features via GitLab MCP. Gemini 3 Flash analyzes kill reasons, then calls Google Search to verify whether each constraint was resolved. Every "what changed" claim is backed by a live URL and release date. An independent Vertex AI challenger stress-tests every revival case.
- Phase 2: Agent Builder synthesizes all findings into a ranked executive action plan. One click creates a GitLab issue or Draft MR with a revival checklist.