workflow-health-check

Audits GitHub PR, Issue, and pipeline health and applies safe automated fixes.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/kai-kou/gem-hunter --skill workflow-health-check-kai-kou
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workflow-health-check
Source: https://github.com/kai-kou/gem-hunter/tree/main/.claude/skills/workflow-health-check
Command: npx skills add https://github.com/kai-kou/gem-hunter --skill workflow-health-check-kai-kou

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Development workflows silently degrade: PRs conflict or stall as drafts, Issues get stuck in wrong status labels, pipelines lose coverage, and feedback loops stop being acted on. This Skill continuously audits that health and fixes safe problems automatically before they block delivery. ## Core Features & Use Cases - PR Health Audit: Validates base branches, detects merge conflicts and stale draft PRs, and routes review-pending PRs back into the review flow with guidance comments. - Issue State Audit: Resets stuck in-progress Issues, fixes duplicate status labels, flags long-idle Issues, and detects orphan Issues that no automation lane covers. - Feedback Loop & Routine Monitoring: Tracks retro-try Issue digestion rates, duplicate detection, scheduled routine heartbeats, and stalled sessions, with circuit breakers limiting auto-fixes to reversible actions (labels, comments, notifications). - Use Case: Run the full weekly audit to receive a report of detected problems, auto-applied label fixes, and items needing user attention, or run the lightweight daily mode covering only PR and Issue hygiene. ## Quick Start Ask the AI to run a workflow health check on this repository's open PRs and Issues.

Frequently Asked Questions about workflow-health-check

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

FAQPage Schema
How do I audit open pull requests for conflicts and stale drafts?▼

Run the full health check, which fetches open PRs via the GitHub API, checks mergeable_state for conflicts, and flags draft PRs untouched for over 24 hours. It posts guidance comments and applies status:blocked labels to PRs with conflicts older than 48 hours.

How to detect stuck or orphaned GitHub Issues automatically?▼

The Issue audit finds in-progress Issues idle over 4 hours and resets them to waiting status, removes duplicate status labels, and lists orphan Issues that fall outside every automation lane's scope. Orphans caused by missing labels get labels backfilled automatically.

What automated fixes does the workflow audit apply without approval?▼

Only reversible operations: adding or removing labels, posting GitHub comments, sending Slack notifications, and creating tracking Issues. It never modifies code, merges PRs, deletes branches, or closes Issues, and caps Issue creation at five per run.

What is the difference between the full and lightweight audit modes?▼

The lightweight mode runs only PR health and Issue state audits, intended for daily hygiene slots. The full mode adds pipeline consistency checks, root-cause recording, feedback-loop monitoring, routine heartbeat verification, and CLAUDE.md bloat auditing, intended for weekly runs.

Why does the audit skip GitHub operations in cloud environments?▼

Cloud sessions lack a real gh CLI, so all GitHub operations route through MCP tools like mcp__github__list_issues instead. Some operations such as label creation and milestone management have no MCP equivalent and are skipped in cloud runs.