github-issue-grooming

To clean up GitHub issue backlogs, this Skill reads dependency notes in issue descriptions, creates phase-based milestones, and links prerequisites using native blocked-by relationships. It removes redundant labels while grouping issues by delivery stage.

Yes, native blocked-by relationships can model issue order and prerequisites. This requires GitHub CLI access and GraphQL mutation support to read issues and establish dependency links directly within the repository metadata.

Yes, GitHub CLI access and GraphQL mutation support are required. These tools allow the grooming process to read existing issues, create missing milestones, update issue metadata, and manage blocked-by relationships programmatically.

The best way to remove redundant labels is to migrate structural information into milestones and native dependency links. Once issues are grouped by delivery stage and connected via blocked-by relationships, phase labels become unnecessary and can be safely deleted.

Yes, issue grooming is designed for repositories with epics, phases, blockers, and dependency notes embedded in issue bodies. It extracts these notes to establish native GitHub relationships and create a cleaner, more navigable tracking system.

You should avoid automated issue grooming if your repository lacks dependency notes in issue descriptions or does not support GraphQL mutations. The process relies on extracting embedded phase and blocker information to function correctly.