inventory

Scan a repository with a YAML recipe pack and produce a Markdown inventory report.

4|3|Updated May 2, 2026
One-click install
npx skills add https://github.com/ggemba/squad-mcp --skill inventory-ggemba
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: inventory
Source: https://github.com/ggemba/squad-mcp/tree/main/skills/inventory
Command: npx skills add https://github.com/ggemba/squad-mcp --skill inventory-ggemba

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codebases hide scattered patterns like raw SQL, debug leftovers, deprecated APIs, or potential secrets, and manually finding them is slow and error-prone.

Core Features & Use Cases

  • Recipe-driven detection: Scans for named patterns defined in a YAML recipe pack (including inline SQL, fetch calls, feature flags, debug output, deprecated APIs, and hardcoded secrets).
  • Cross-reference enrichment: Optionally maps findings to framework relationships such as routes → controllers/handlers when a pack declares cross-reference rules.
  • Deterministic output artifact: Produces a structured Markdown inventory report at a chosen path, without modifying your source code.

Quick Start

Run the inventory scan for a bundled pack like debug-leftovers across your workspace with normal depth.

Frequently Asked Questions about inventory

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

FAQPage Schema
How do I detect inline SQL and debug leftovers across my codebase?

To detect inline SQL and debug leftovers across a codebase, run a deterministic ripgrep sweep using a YAML recipe pack to locate named patterns and generate a structured Markdown inventory report.

Can I map deprecated API usage and hardcoded secrets without modifying source code?

Mapping deprecated API usage and hardcoded secrets requires only a read-only ripgrep scan, producing a remediation-ready triage artifact that documents findings without modifying your source code.

How does cross-reference enrichment work for framework relationships like routes and controllers?

Cross-reference enrichment maps framework relationships like routes to controllers by applying optional cross-reference rules declared in a YAML recipe pack during the scan, appending the relationships to the inventory report.

What is a codebase inventory report and when do I need one for technical debt triage?

A codebase inventory report is a structured Markdown file enumerating recurring code patterns and potential security issues, needed when triaging technical debt or auditing scattered constructs across a workspace.

Does the inventory scan require external dependencies to run a ripgrep pattern detection?

The inventory scan requires no external dependencies to execute the deterministic ripgrep pattern detection, though it optionally supports tiered LLM enrichment with strict schema validation for enhanced findings.

What are the limitations of using YAML recipe packs for security triage?

YAML recipe packs limit security triage to predefined named patterns detected by deterministic ripgrep sweeps, meaning unanticipated vulnerability signatures or complex data flow issues require manual recipe configuration.