skills.rest
Obsidian-Owl
Obsidian-OwlOFFICIAL
Explore all skills by this author →
WebsiteGitHub

speckit-wiring-check

Identify Python modules unreachable from CLI, plugin registry, or package exports.

4|11|Updated Dec 14, 2025
Search Tags:#cli#plugins#verify#exports#wiring#entry-points#code-integrity
One-click install
npx skills add https://github.com/Obsidian-Owl/floe --skill speckit-wiring-check
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-wiring-check
Source: https://github.com/Obsidian-Owl/floe/tree/main/.claude/skills/speckit-wiring-check
Command: npx skills add https://github.com/Obsidian-Owl/floe --skill speckit-wiring-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps ensure that newly added code is reachable via the project's entry points (CLI commands, plugin registry, or package exports), preventing orphaned or hidden code that never gets used.

Core Features & Use Cases

  • Verifies that new modules are exposed through CLI entry points, plugin registries, or public API surfaces.
  • Flags orphaned code and guides teams to wire new components into the system.
  • Use Case: During a PR review, run this to confirm the changes are actually reachable by users or downstream systems.

Quick Start

Run speckit-wiring-check to verify that the new code is reachable via CLI, plugin registry, and package exports.

Frequently Asked Questions about speckit-wiring-check

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

FAQPage Schema
What is the best way to check if new Python modules are wired to CLI and plugin entry points?▼

Verifying entry point reachability involves checking that newly added Python modules are exposed through CLI commands, plugin registries, or public API exports to prevent orphaned code.

How do I detect orphaned code modules during a PR review?▼

To detect orphaned code during a PR review, verify that newly added Python modules are reachable from CLI commands, plugin registries, or package exports to ensure they are integrated into the system.

Why does newly added code remain hidden from the package exports?▼

Newly added code remains hidden from package exports when it lacks proper wiring to the public API surface, requiring an import reachability check to verify entry points and flag orphaned modules.

Can I verify plugin registry integration for newly added Python modules?▼

Yes, you can verify plugin registry integration by running a wiring check that confirms newly added Python modules are properly exposed and reachable through the plugin registry entry points.

What are the limitations of automated entry point wiring checks?▼

Automated entry point wiring checks are limited to verifying static import reachability and proper exports for Python modules via CLI, plugin, and API surfaces, without validating runtime execution behavior.

Related Skills

Explore More Software Engineering Skills→
elbrunoelbruno
2

CLI Command Wiring

Validate CLI command routing and help registration in TypeScript entrypoints.

Community
Basic
SethGammonSethGammon
820

scaffold

Generate new project files matching existing codebase conventions and wiring.

Community
Intermediate
AreteDriverAreteDriver
4

cicd-pipeline

Implements CI/CD pipelines using Batcomputer for automated code review and deployment gating.

Community
Advanced
Destynova2Destynova2
5

cli-audit-tangle

Analyze codebases for god functions, circular dependencies, dead code, and module boundaries.

Community
Advanced