nacl-tl-stubs

Scan codebases for stub markers and maintain a persistent stub registry.

23|2|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/ITSalt/NaCl --skill nacl-tl-stubs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nacl-tl-stubs
Source: https://github.com/ITSalt/NaCl/tree/main/nacl-tl-stubs
Command: npx skills add https://github.com/ITSalt/NaCl --skill nacl-tl-stubs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scans a codebase for stub markers and placeholder code, maintaining a persistent registry to prevent shipping unfinished work.

Core Features & Use Cases

  • Detects markers such as TODO, FIXME, STUB, and MOCK across the codebase.
  • Maintains a stub-registry.json to track live and resolved stubs over time.
  • Generates per-UC stub reports and enforces gating on critical stubs.

Quick Start

Run /nacl-tl-stubs to perform a full repository scan, update the registry, and generate the consolidated report.

Frequently Asked Questions about nacl-tl-stubs

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

FAQPage Schema
How do I detect and track stub markers like TODO and FIXME across my codebase?

Stub gating works by classifying detected placeholder code by severity and enforcing a quality gate that prevents progress until critical issues are resolved. It generates per-UC reports to track exact blocker locations.

What is the best way to maintain a persistent registry of unresolved placeholder code?

Maintaining a persistent registry of unresolved placeholder code involves generating a stub-registry.json file during a full repository scan. This registry reconciles live and resolved stubs automatically to keep production code clean.

Can I scan for incomplete code and associate findings with a specific use case scope?

Yes, you can scan for incomplete code within specific use case scopes. The scanner detects placeholder markers in the src/ directory and associates findings with the relevant UC, generating per-UC stub reports for targeted tracking.

How do I prevent shipping unfinished work with a static analysis quality gate?

Preventing shipping unfinished work requires a static analysis quality gate that flags incomplete code by severity. The gate blocks progress on critical stubs identified during the repository scan until they are fully resolved.

What are the limitations of using a stub registry for code quality tracking?

Limitations of using a stub registry include relying on predefined markers like TODO, FIXME, STUB, and MOCK for detection. Unconventional placeholder code without these explicit markers may be missed during the src/ directory scan.