How do I mark a placeholder as intentional?

You can use the '# SUBSTITUTE-OK' comment syntax next to any token to signal to the auditor that the specific placeholder is intentional and should be ignored in future scans.

Does it flag my unit test mocks as errors?

No, Substitute Eraser is context-aware and automatically excludes common mock, fake, and stub patterns when they are located within test directories or files following standard test naming conventions.

How does Substitute Eraser differ from standard linting?

While linters focus on syntax and style, Substitute Eraser focuses on semantic technical debt, identifying intentional but temporary placeholders and providing a structured roadmap to replace them with production code.

Can I use this skill to fail builds in CI/CD?

Yes, the 'substitute-critical' command is designed for CI environments, returning a non-zero exit code if high-severity tokens are found, preventing incomplete code from being merged.

Substitute Eraser

Name: Substitute Eraser
Author: plurigrid

byplurigrid

•

Seguridad y Pruebas

Scans codebases for placeholders, TODOs, and stubs to generate structured remediation plans for technical debt.

Acerca de

Substitute Eraser is a specialized auditing tool designed to identify and eliminate technical debt within existing codebases. It performs deep scans of source files, configurations, and documentation to locate placeholder tokens like TODO, FIXME, and temporary mocks that often leak into production. Unlike standard output validators, this skill categorizes findings by severity—Critical, Warning, and Info—and provides actionable remediation reports. It integrates seamlessly with task management systems like GitHub and Linear, allowing developers to convert code stubs into tracked tickets and maintain a clean, production-ready repository.

Características Principales

Interactive fix mode for rapid on-the-fly codebase cleanup
Categorized severity reporting with automated remediation plan generation
Context-aware detection that ignores intentional stubs in tests and documentation
Deep codebase scanning for TODOs, FIXMEs, and custom placeholder patterns
2 GitHub stars
Task export capabilities for GitHub, Linear, and local TODO files

Casos de Uso

Pre-release audits to ensure no temporary code or stubs remain in the production branch
CI/CD integration to block merges containing critical placeholders or unaddressed FIXMEs
Automated technical debt discovery and backlog generation for legacy repositories

Acerca de

Características Principales

Interactive fix mode for rapid on-the-fly codebase cleanup
Categorized severity reporting with automated remediation plan generation
Context-aware detection that ignores intentional stubs in tests and documentation
Deep codebase scanning for TODOs, FIXMEs, and custom placeholder patterns
2 GitHub stars
Task export capabilities for GitHub, Linear, and local TODO files

Casos de Uso

Pre-release audits to ensure no temporary code or stubs remain in the production branch
CI/CD integration to block merges containing critical placeholders or unaddressed FIXMEs
Automated technical debt discovery and backlog generation for legacy repositories