file-tech-debt

Automate tech-debt tracking by triggering this skill during code reviews to file out-of-scope findings as durable GitHub issues. It standardizes the lifecycle of technical debt through automated creation, deduplication, and provenance tracking for every identified issue.

Automated deduplication prevents duplicate GitHub issues by generating a unique machine-readable key for each code location. This key ensures every identified out-of-scope finding is uniquely indexed before a new issue is created.

Yes, you can integrate tech-debt issue tracking with existing repository statusline debt-count sentinels. The skill satisfies requirements for idempotent issue creation and automated label management to sync with your repository statusline.

The best way to standardize severity grading and labeling is to enforce a consistent workflow for all engineering teams. This skill categorizes every tech-debt issue by severity and difficulty while applying automated label management to ensure uniformity.

Provenance tracking records the origin, branch, and context of a technical debt finding automatically. This ensures accountability and traceability for every out-of-scope code review issue filed as a durable GitHub issue.

Yes, idempotent issue creation works with existing issue-tracking workflows. It operates within software engineering review processes to ensure filing out-of-scope code findings is repeatable without generating duplicate issues.