skills.rest
maddhruv
maddhruvCOMMUNITY
Explore all skills by this author →
Website𝕏@maddhruvGitHub

absolute-debt

Resolve existing lint and type errors in codebases through isolated serial fixup waves.

207|31|Updated Mar 14, 2026
Search Tags:#code quality#linting#technical debt#type checking#repository health
One-click install
npx skills add https://github.com/maddhruv/absolute --skill absolute-debt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: absolute-debt
Source: https://github.com/maddhruv/absolute/tree/main/skills/absolute-debt
Command: npx skills add https://github.com/maddhruv/absolute --skill absolute-debt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill targets and resolves pre-existing lint and type errors in a codebase, systematically reducing technical debt without disrupting development workflow.

Core Features & Use Cases

  • Lint and Type Error Cleanup: Clears out all existing violations one rule at a time.
  • Safe Wavering: Runs fixes in isolated, serial waves for independent verification.
  • Maintenance Automation: Regularly scans green main branch for unresolved issues.
  • Use Case: When starting a new project or before a major release, use this Skill to clean up and stabilize your codebase by removing old warnings and fixing types that have evolved over time.

Quick Start

/absolute-debt "Clear our lint warnings and type errors"

Frequently Asked Questions about absolute-debt

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

FAQPage Schema
How do I fix existing lint and type errors in my codebase without breaking the main branch?▼

To fix existing lint and type errors safely, technical debt cleanup should be performed in isolated, serial waves. This approach allows independent verification of incremental fixes while maintaining a green main branch throughout the process.

What is the best way to systematically reduce technical debt from old lint warnings and type issues?▼

The best way to reduce technical debt systematically is wave-based fixups, clearing violations one rule at a time. This ensures incremental cleanup of old warnings and evolved types without disrupting active development workflows.

Does technical debt cleanup work with both ESLint and mypy for resolving codebase violations?▼

Yes, technical debt cleanup works across multiple ecosystems requiring linters and typecheckers like ESLint, Pylint, and mypy. It resolves existing violations across these tools through systematic, incremental fixups.

How do I automate codebase health maintenance to catch unresolved lint and type issues?▼

Automate codebase health maintenance by regularly scanning a green main branch for unresolved lint and type issues. This ongoing monitoring ensures new violations are caught and resolved incrementally over time.

When should I run a technical debt cleanup on my repository before a major release?▼

Run technical debt cleanup before major releases or when starting new projects to stabilize your codebase. Removing old warnings and fixing evolved types ensures repository health and prevents unexpected failures during deployment.

Related Skills

Explore More Software Engineering Skills→
NVIDIANVIDIA
17.4k

linting-and-formatting

Format, lint, and type-check Megatron-LM Python code with black, isort, ruff, pylint, and mypy.

Official
Intermediate
hidonguyenhidonguyen

ck:fix

Diagnose and fix code issues with verification and regression prevention.

Community
Advanced
SandroBeatzSandroBeatz

lint-check

Run ESLint and TypeScript type checking on a codebase.

Community
Intermediate
gwpjpgwpjp
3

verify

Runs typecheck, lint, prettier, and build to produce a pass/fail report.

Community
Advanced