scan-orphans

Scan codebases to identify and classify unclaimed code as Active, Dead, or Uncertain.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/hariinfo/agentic-code-template --skill scan-orphans
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scan-orphans
Source: https://github.com/hariinfo/agentic-code-template/tree/main/.claude/skills/orphan-scanner
Command: npx skills add https://github.com/hariinfo/agentic-code-template --skill scan-orphans

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scan entire codebase for orphaned, unclaimed, or dead code missed by entry-point analysis. Identifies active orphans (REST endpoints, Kafka consumers, scheduled jobs, stored procedures with no entry point coverage), classifies code as Active, Dead, or Uncertain, extracts functionality details, assesses risk, and recommends modernization path.

Core Features & Use Cases

  • Builds a unified set of claimed files from modernization-output fingerprints to separate known-good from unclaimed code.
  • Recursively scans the legacy codebase across Java, JSP, SQL, configuration, and other files to identify unclaimed files.
  • Classifies unclaimed files into Active Orphan, Dead Code, or Uncertain with evidence on usage, references, and recent activity.
  • For active orphans, extracts entry points, behavior, data dependencies, error handling, integration points, security considerations, and evidence to guide modernization planning.

Quick Start

Run the orphan scanner to detect and report unclaimed code in the repository.

Frequently Asked Questions about scan-orphans

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find orphaned and dead code across a legacy Java and JSP codebase?

You can identify active orphaned code by scanning for REST endpoints, Kafka consumers, scheduled jobs, and stored procedures that lack entry-point coverage. The tool classifies these as active orphans to distinguish them from dead code.

What is the best way to classify unclaimed code for modernization risk assessment?

Before scanning for orphaned code, you must build a unified set of claimed files from modernization-output fingerprints. This establishes a baseline to accurately separate known-good code from unclaimed files across the repository.

How do I extract integration points and security considerations from active orphans?

You extract integration points and security considerations by running an orphan analysis on active files. This process details entry points, behavior, data dependencies, and error handling to guide modernization planning.

Can I scan SQL and configuration files for dead code alongside Java sources?

Yes, you can scan SQL and configuration files for dead code alongside Java sources. The scanner recursively evaluates all source file types to identify unclaimed files and assess their modernization risk.