hydra-gate-stub-scan

Detect incomplete code stubs and unused dependencies in PHP and Vue files.

1|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/ConductionNL/shillinq --skill hydra-gate-stub-scan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hydra-gate-stub-scan
Source: https://github.com/ConductionNL/shillinq/tree/main/.claude/skills/hydra-gate-stub-scan
Command: npx skills add https://github.com/ConductionNL/shillinq --skill hydra-gate-stub-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents the integration of incomplete or stubbed code into the production codebase by identifying placeholders, empty logic, and hardcoded UI responses that bypass actual functionality.

Core Features & Use Cases

  • Stub Detection: Identifies marker comments like In a complete implementation and empty background job bodies.
  • Dependency Validation: Flags unused injected dependencies in services and controllers.
  • Frontend Integrity: Detects hardcoded single-entry stubs in Vue fetch methods.
  • Use Case: Before pushing code, run this scan to ensure that all tasks marked as complete in your documentation are actually implemented in the source code.

Quick Start

Run the hydra-gate-stub-scan skill to audit the current directory for incomplete code stubs and unused dependencies.

Frequently Asked Questions about hydra-gate-stub-scan

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

FAQPage Schema
How do I detect incomplete code stubs and placeholder comments in my PHP and Vue codebase?

Detect incomplete code stubs by running an automated static analysis scan that searches PHP and Vue source files for marker comments like 'In a complete implementation' and empty logic blocks before deployment.

What is the best way to prevent hardcoded frontend fetch responses in Vue components from reaching production?

Preventing hardcoded frontend fetch responses in Vue components requires an automated quality gate scan that identifies single-entry stubs in fetch methods and flags them before code integration.

How do I find unused dependency injections in my PHP services and controllers?

Find unused dependency injections in PHP services and controllers by running a static analysis scan that validates injected dependencies and flags any that remain unreferenced in the class logic.

Can I integrate stub detection into a CI/CD pipeline to enforce spec coherence?

You can integrate stub detection into a CI/CD pipeline to enforce spec coherence by running the scan as a pre-deployment quality gate to ensure tasks marked as complete are actually implemented in the source code.

Do I need any special dependencies to run a static analysis scan for empty background job methods?

You do not need special dependencies to scan for empty background job methods, as the static analysis operates using standard Unix utilities like grep, sed, and find to parse PHP and Vue source files.

Why does my code quality gate flag marker comments like 'In a complete implementation' as errors?

A code quality gate flags marker comments like 'In a complete implementation' because they indicate incomplete code stubs that bypass actual functionality, ensuring spec coherence before deployment.