dev-verify-wiring

Detect orphaned exports and wiring gaps in frontend modules.

1|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/Obsidian-Owl/agentlint --skill dev-verify-wiring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-verify-wiring
Source: https://github.com/Obsidian-Owl/agentlint/tree/main/.claude/skills/dev.verify-wiring
Command: npx skills add https://github.com/Obsidian-Owl/agentlint --skill dev-verify-wiring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers detect unintegrated features before they become dead code, ensuring that designed wiring patterns (the Ink component pattern) are actually implemented in the codebase.

Core Features & Use Cases

  • Detect unwired features lingering as dead code in frontend modules.
  • Trace wiring paths to verify exports, imports, and entry points align with epic plans.
  • Provide actionable guidance on missing wiring and suggested fixes.

Quick Start

Use /dev.verify-wiring [options] to start the check on your current branch.

Frequently Asked Questions about dev-verify-wiring

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

FAQPage Schema
How do I detect dead code from unwired features in a frontend module?

During code review, verify wiring by tracing export and import paths to ensure they align with entry points. This integration validation surfaces disconnected subgraphs and wiring gaps, confirming that new features are actually reachable.

What is the best way to find orphaned exports in a frontend codebase?

Finding orphaned exports involves analyzing the import usage graph to identify exported modules that no entry-point path reaches. This static analysis highlights unintegrated features and provides concrete fixes to reconnect or remove them.

How do I validate frontend integration and fix missing wiring gaps?

Validate frontend integration by checking that exports and components align with your epic plans across all entry points. The analysis identifies wiring gaps and provides actionable guidance on missing connections to ensure proper implementation.

When should I run static analysis to check for unintegrated features?

Run static analysis to check for unintegrated features during PR reviews and when completing wiring tasks. This prevents disconnected subgraphs and orphaned exports from slipping into the main branch as unreachable dead code.