skills.rest
azishio
azishioCOMMUNITY
Explore all skills by this author →
GitHub

anti-overengineering-debt

Collects anti-overengineering comment markers into a grouped technical debt ledger report.

Updated Jul 11, 2026
Search Tags:#refactoring#technical debt#code comments#grep#shortcuts#code scan#debt ledger
One-click install
npx skills add https://github.com/azishio/coding-skills --skill anti-overengineering-debt-azishio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: anti-overengineering-debt
Source: https://github.com/azishio/coding-skills/tree/main/skills/anti-overengineering-debt
Command: npx skills add https://github.com/azishio/coding-skills --skill anti-overengineering-debt-azishio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deliberate shortcuts marked with anti-overengineering: comments tend to be forgotten and silently become permanent. This Skill scans the codebase for every such marker and compiles them into a single debt ledger so deferred work stays visible and trackable. ## Core Features & Use Cases - Marker Scanning: Greps the repository for anti-overengineering: comment markers while skipping node_modules, .git, target, and build output. - Structured Ledger: Produces one row per marker grouped by file, extracting the ceiling (the limit named) and the upgrade trigger from each comment, with optional git blame ownership. - Rot Detection: Flags any marker lacking an upgrade trigger with a no-trigger tag, highlighting the shortcuts most likely to rot. - Use Case: Before a sprint planning session, run the scan to list every deferred simplification, identify which ones have no revisit trigger, and decide which debts to pay down. ## Quick Start Ask the assistant to run the anti-overengineering debt scan and list every marked shortcut in this repository with its ceiling and upgrade trigger.

Frequently Asked Questions about anti-overengineering-debt

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

FAQPage Schema
How do I track deliberate technical debt shortcuts in my codebase?▼

Mark each deliberate shortcut with an anti-overengineering: comment naming its ceiling and upgrade trigger, then run this scan to grep all markers into a grouped ledger. Each row shows the file, line, what was simplified, and when to revisit it.

How to find code comments marking deferred work across a repository?▼

Use grep -rnE '(#|//) ?anti-overengineering:' . to locate every marker, skipping node_modules, .git, target, and build output. The scan groups hits by file and pulls the ceiling and upgrade trigger straight from each comment.

Does the debt ledger scan modify my source files?▼

No, the scan is read-only and changes nothing in the repository. It only reports findings, and it writes the ledger to a file such as ANTI-OVERENGINEERING-DEBT.md only if you explicitly ask it to persist the output.

What happens if a shortcut comment has no upgrade trigger?▼

Any anti-overengineering: comment that names no upgrade path or trigger receives a no-trigger tag in the ledger. These flagged rows are the ones most likely to silently rot, since nothing defines when the shortcut should be revisited.

Can I see who wrote each debt marker comment?▼

Yes, the ledger supports optional ownership per row by running git blame -L<line>,<line> on each marker location. This attributes every shortcut to the commit author who introduced it.

Related Skills

Explore More Software Engineering Skills→
Jatinkrmahato993203Jatinkrmahato993203

ponytail-debt

Harvests ponytail comment markers from a codebase into a technical debt ledger.

Community
Basic
RohithdgrrRohithdgrr

tech-debt-tracker

Scan codebases for technical debt, prioritize remediation, and track debt trends over time.

Community
Advanced
CENKSSSCENKSSS

qe-quality-assessment

Automate code quality assessment with complexity analysis, linting, and test health metrics.

Community
Advanced
hulusi-tunchulusi-tunc
3

accessibility-debt-tracking

Track accessibility debt with issue fields and triage governance rules.

Community
Advanced