skills.rest
N0K0
N0K0COMMUNITY
Explore all skills by this author →
WebsiteGitHub

lint-issues

Audits open GitHub issues for workflow consistency and compliance gaps.

Updated Mar 28, 2026
Search Tags:#issue management#github issues#consistency check#lint#dev workflow#workflow audit
One-click install
npx skills add https://github.com/N0K0/claude-plugins-backalley --skill lint-issues
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lint-issues
Source: https://github.com/N0K0/claude-plugins-backalley/tree/main/plugins/process/skills/lint-issues
Command: npx skills add https://github.com/N0K0/claude-plugins-backalley --skill lint-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually checking GitHub issues for workflow compliance is time-consuming and error-prone, leading to mislabeled issues, incomplete specifications, and broken cross-issue references that disrupt development progress and waste team time.

Core Features & Use Cases

  • Label & State Validation: Ensures issues have exactly one correct workflow label, and that label state matches issue content (e.g., has-spec issues have non-empty bodies, in-progress issues have checklists and local branches).
  • Spec & Checklist Audits: Verifies issues with has-spec or in-progress labels include all 5 required spec sections, and flags stale in-progress issues, fully checked issues ready for review, or in-progress issues with no completed checklist items.
  • Cross-Issue Consistency Checks: Confirms parent issue references and umbrella tasklist links point to valid, correctly statused issues.
  • Use Case: Development teams using GitHub Issues for structured workflows can run this audit before sprint planning to catch and fix workflow violations that would otherwise block development.

Quick Start

Ask Claude to run the lint-issues skill to audit all open GitHub issues in your current repository for workflow consistency and receive a grouped report of errors and warnings.

Frequently Asked Questions about lint-issues

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

FAQPage Schema
How do I audit GitHub issues for workflow consistency and spec completeness?▼

You can audit GitHub issues for workflow consistency by running a lint check that validates label correctness, spec completeness, checklist health, and cross-issue reference accuracy across all active issues. This generates a severity-grouped report of compliance gaps without modifying any issue data.

Why do my GitHub issues have mislabeled workflow states and broken cross-issue references?▼

Mislabeled issues and broken cross-issue references happen when manual checks fail to catch workflow violations. An automated consistency audit validates that has-spec issues have non-empty bodies with required sections and that parent issue references point to valid, correctly statused issues.

What's the best way to check if in-progress GitHub issues have local branches and valid checklists?▼

The best way to check in-progress issues is to run an audit that cross-references GitHub issue data with local git state to verify branch existence, while also evaluating checklist health to flag stale issues or those with no completed checklist items.

Does the GitHub issue workflow audit require the gh plugin and local git access?▼

Yes, the GitHub issue workflow audit requires the gh plugin for issue data retrieval and local git state to verify branch existence for in-progress issues. These dependencies are needed to validate label states against repository conditions and generate the compliance report.

Can I validate GitHub issue labels and tasklist links before sprint planning without modifying data?▼

Yes, you can validate GitHub issue labels and tasklist links without modifying data by running a read-only audit. It checks that issues have exactly one correct workflow label and confirms umbrella tasklist links point to valid issues, outputting a report of errors and warnings.

When should I avoid using an automated GitHub issue consistency checker?▼

You should avoid using an automated GitHub issue consistency checker if your team does not use structured development workflows with standardized labels like has-spec or in-progress, because the audit specifically validates compliance against those predefined workflow conventions.

Related Skills

Explore More Software Engineering Skills→
Steve-Smith-CODESteve-Smith-CODE

speckit-taskstoissues

Convert local task lists into GitHub issues with duplicate detection.

Community
Advanced
williamzujkowskiwilliamzujkowski
17

broken-reference

Scan Markdown files for broken cross-references and report remediation steps.

Community
Basic
Reading-Advantage-ThailandReading-Advantage-Thailand

git-workflow

Orchestrate spec-driven development workflows with GitHub issues and pull requests.

Official
Advanced
TeiNamTeiNam
12

laravel-verification

Automate Laravel project verification for CI/CD pipelines.

Community
Advanced