How does this skill handle large architectural changes?

The skill is explicitly designed to pause and ask for approval before making any major architectural, structural, or breaking changes to public APIs.

What kind of issues does it fix automatically?

It autonomously handles minor style consistency, missing function assertions, inconsistent naming, and obvious gaps in test coverage.

Does it fix issues outside of the current file?

Yes, it follows a systematic approach to search for and fix similar issues across the entire project once an inconsistency or violation is identified.

Can I use this with my existing linting tools?

Absolutely. The skill is designed to work alongside existing workflows, including commands like 'make lint' and 'make fmt' to ensure project-wide consistency.

Zero Technical Debt

Name: Zero Technical Debt
Author: mgreenly

bymgreenly

•

Productivity & Workflow

Maintains high-quality codebases by enforcing a philosophy of immediate, systematic resolution of technical debt and code inconsistencies.

About

The Zero Technical Debt skill empowers Claude to proactively maintain code health by identifying and fixing problems, inconsistencies, or standard violations the moment they are discovered. By prioritizing root cause resolution over temporary patches and systematically searching for similar issues throughout the repository, it ensures that technical debt does not accumulate during the development process. The skill strikes a balance between autonomous maintenance—such as fixing naming conventions, missing assertions, and test gaps—and collaborative development by requiring explicit approval for major architectural shifts or breaking API changes.

Key Features

Automated enforcement of naming conventions and error handling standards
Root cause resolution to prevent symptom-only patching
Systematic project-wide scanning for similar patterns when a debt item is found
Continuous improvement of test coverage and precondition assertions
Proactive identification and immediate fixing of code inconsistencies and violations
1 GitHub stars

Use Cases

Automatically identifying and filling test coverage gaps while working on existing modules
Preventing long-term technical debt accumulation during high-velocity feature development
Standardizing error handling and naming patterns across legacy codebases

About

Key Features

Automated enforcement of naming conventions and error handling standards
Root cause resolution to prevent symptom-only patching
Systematic project-wide scanning for similar patterns when a debt item is found
Continuous improvement of test coverage and precondition assertions
Proactive identification and immediate fixing of code inconsistencies and violations
1 GitHub stars

Use Cases

Automatically identifying and filling test coverage gaps while working on existing modules
Preventing long-term technical debt accumulation during high-velocity feature development
Standardizing error handling and naming patterns across legacy codebases