Verified:GitHub

hatch3r-board-groom

Scans boards in GitHub/Azure DevOps/GitLab to groom work items and dependencies.

26|4|Updated Feb 27, 2026

Search Tags:#dependency management #GitHub Projects #Azure DevOps #issue triage #board grooming #GitLab issues #label hygiene

One-click install

npx skills add https://github.com/hatch3r/hatch3r --skill hatch3r-board-groom

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: hatch3r-board-groom
Source: https://github.com/hatch3r/hatch3r/tree/main/skills/hatch3r-board-groom
Command: npx skills add https://github.com/hatch3r/hatch3r --skill hatch3r-board-groom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents backlog decay by continuously refining GitHub/Azure DevOps/GitLab board work items so priorities, scope, labels, and dependencies stay accurate and actionable.

Core Features & Use Cases

Performs a full board scan across open issues/work items, caching items, parent/child structure, and dependency references from issue bodies.
Computes board health insights including stale items, missing required labels, dependency drift (stale/orphaned/block chains), priority imbalance, duplicate/overlap candidates, and sync drift between labels and project board columns.
Executes controlled grooming actions like reprioritize, reclassify, re-scope, demote to triage, archive stale items, decompose oversized epics, merge duplicates, refresh dependency data, relink sub-issues, regroup standalones into epics, and apply health remediation.
Maintains safety guardrails via checkpoints by asking for confirmation at major stages and only applying user-selected actions.

Quick Start

Run board grooming with the hatch3r workflow so it scans your repository’s board items, summarizes refinement opportunities, and prompts you to choose which actions to apply.

Frequently Asked Questions about hatch3r-board-groom

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

FAQPage Schema

How do I fix backlog decay and dependency drift on my GitHub Projects board?▼

Board grooming repairs backlog decay by scanning open issues to detect stale items, missing labels, and orphaned dependency chains, then applying user-confirmed remediation to keep work items delivery-ready across GitHub, Azure DevOps, or GitLab.

What is board grooming and how does it improve issue triage?▼

Board grooming is the continuous refinement of backlog items so priorities, scope, and dependencies stay accurate. It improves issue triage by computing health insights like priority imbalance and sync drift, then executing targeted actions such as reclassifying or archiving stale work.

How do I clean up stale issues and fix label hygiene in Azure DevOps?▼

To clean up stale issues and fix label hygiene in Azure DevOps, run a comprehensive single-pass board scan that caches parent/child structures, detects missing required labels and duplicate candidates, and applies platform-specific CLI updates after user confirmation.

Can I relink sub-issues and decompose oversized epics across GitLab issues?▼

Yes, you can relink sub-issues and decompose oversized epics across GitLab issues. Board grooming detects epic ordering inconsistencies and standalone items, then regroups standalones into epics or decomposes them using platform-specific CLI updates with user confirmation.

Does board grooming require manual confirmation before applying changes to work items?▼

Yes, board grooming requires manual confirmation before applying changes. It maintains safety guardrails via checkpoints, asking for user confirmation at major stages and only applying selected grooming actions like reprioritizing, merging duplicates, or refreshing dependency data.

What's the best way to detect sync drift between project board columns and issue labels?▼

The best way to detect sync drift between project board columns and issue labels is to execute a comprehensive single-pass board scan that caches dependency references and computes health insights, identifying where labels and columns have desynchronized before applying remediation.