Verified:GitHub

hatch3r-board-shared

Validate hatch3r board command configuration, authentication, and sync across GitHub, Azure DevOps, and GitLab.

26|4|Updated Feb 27, 2026

Search Tags:#GitHub Projects #board synchronization #dependency governance #issue workflow #Azure Boards #GitLab boards #run cache

One-click install

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

Or copy as Structured Prompt for Agent▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents board-command failures and drift by enforcing a shared, platform-agnostic checklist for configuration, authentication, board syncing, linkage, and reconciliation.

Core Features & Use Cases

Prerequisite validation: Verifies .hatch3r/hatch.json, owner/repo identity, platform authentication, and required board configuration (including null-option abort behavior).
Board sync enforcement: Mandates that every mutation is synced and that status/label changes are immediately reflected on the board.
Reliability mechanisms: Uses retry-then-halt with bounded retry budgets, records attempts in a run cache, and verifies results in an end-of-run reconciliation report.
Epic/sub-issue governance: Applies epic grouping and enforces dependency-label consistency for issues with ## Dependencies.
Platform detection & tool hierarchy: Reads configured platform from hatch.json, drives CLI-first operations, and uses Context7 MCP/web research where appropriate.

Quick Start

Have an AI agent run a board command and load this Skill first so it can validate prerequisites, perform required board mutations, and finish with reconciliation reporting.

Frequently Asked Questions about hatch3r-board-shared

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

FAQPage Schema

How do I keep GitHub Projects and Azure Boards synchronized without status drift?▼

Board sync enforcement mandates that every mutation is immediately synced to the board, ensuring status and label changes are consistently reflected across GitHub, Azure DevOps, and GitLab to prevent drift.

What happens if a board mutation fails during an issue workflow update?▼

When a board mutation fails, a retry-then-halt mechanism triggers with bounded retry budgets, records attempts in a run cache, and halts execution to prevent further inconsistent state propagation.

Do I need a configuration file to automate board grooming across GitLab boards?▼

Yes, you need the .hatch3r/hatch.json configuration file to automate board grooming across GitLab boards, as prerequisite validation verifies this file, owner/repo identity, and platform authentication before allowing any mutations.

How are issue dependencies and epic links governed during board refresh tasks?▼

During board refresh tasks, epic grouping is applied and dependency-label consistency is enforced for issues containing a '## Dependencies' section, ensuring dependency governance and proper epic linkage across the board.

Can I use CLI tools to manage issue workflows across multiple board platforms?▼

Yes, you can use CLI tools to manage issue workflows across multiple board platforms; the system reads your configured platform from hatch.json, drives CLI-first operations, and uses Context7 MCP or web research where appropriate.