skills.rest
mindcockpit-ai
mindcockpit-aiOFFICIAL
Explore all skills by this author →
WebsiteGitHub

lint-debt

Scan lint suppression comments and sync them with GitHub issues.

11|1|Updated Feb 9, 2026
Search Tags:#automation#github#audit#code-quality#grep#lint#technical-debt
One-click install
npx skills add https://github.com/mindcockpit-ai/cognitive-core --skill lint-debt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lint-debt
Source: https://github.com/mindcockpit-ai/cognitive-core/tree/main/core/skills/lint-debt
Command: npx skills add https://github.com/mindcockpit-ai/cognitive-core --skill lint-debt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates discovery and tracking of lint suppression comments across a codebase, ensuring every lint bypass has a corresponding GitHub tracking issue to prevent hidden technical debt.

Core Features & Use Cases

  • Parse suppression comments across source and test directories, extract file, line, rule, and reason, and group occurrences by rule.
  • Cross-reference existing GitHub issues by label and title tag, create issues for untracked rules, reopen stale ones, and comment or suggest closure for resolved debt.
  • Use Case: Integrate in CI or post-edit hooks to generate dashboards, run git blame for aging analysis, and auto-create prioritized tracking issues for sprint planning.

Quick Start

Run the lint-debt scan to locate suppressions and then run the sync command to create any missing GitHub tracking issues.

Frequently Asked Questions about lint-debt

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

FAQPage Schema
How do I track lint suppressions and auto-create GitHub issues for technical debt?▼

To track lint suppressions, scan source and test directories for configurable patterns, group occurrences by rule, and cross-reference existing GitHub issues to automatically create missing tracking entries and synchronize your technical debt audit.

What is the best way to audit code quality bypasses across a repository?▼

The best way to audit code quality bypasses is using grep and git blame tooling to locate suppression comments, extract file and line details, and run aging analysis to identify untracked or stale technical debt across your codebase.

Do I need GitHub CLI to synchronize lint debt tracking issues?▼

Yes, you need authenticated GitHub CLI with configurable label and project settings to cross-reference existing issues, create new issues for untracked rules, and comment on or suggest closure for resolved technical debt.

Can I integrate lint suppression scanning into CI or post-edit hooks?▼

Yes, you can integrate lint suppression scanning in CI or post-edit hooks to generate dashboards, run git blame for aging analysis, and auto-create prioritized tracking issues for sprint planning.

How does the tool handle resolved or stale lint suppressions?▼

The tool handles resolved suppressions by cross-referencing existing GitHub issues by label and title tag, reopening stale ones, and suggesting closure for resolved technical debt to keep your audit accurate.

Related Skills

Explore More Software Engineering Skills→
i3ringiti3ringit
3

git-history-analyzer

Analyze git history to trace file evolution, contributors, and change patterns.

Community
Intermediate
ConsiliencyConsiliency
8

security-audit

Scan codebases for OWASP vulnerabilities and generate prioritized remediation reports.

Official
Intermediate
TeiNamTeiNam
12

security-scan

Scan agent configurations for security vulnerabilities and misconfigurations.

Community
Intermediate
workinprogress-aiworkinprogress-ai

devenv-tech-debt-audit

Audit software repositories for technical debt and architectural decay.

Official
Advanced