skills.rest
Chulf58
Chulf58COMMUNITY
Explore all skills by this author →
GitHub

forge:health

Aggregate FORGE board health signals into severity-grouped reports.

1|Updated Apr 14, 2026
Search Tags:#pipeline#code-quality#forge#status-review#health-signals#board-metrics
One-click install
npx skills add https://github.com/Chulf58/FORGE --skill forge-health
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: forge:health
Source: https://github.com/Chulf58/FORGE/tree/main/skills/health
Command: npx skills add https://github.com/Chulf58/FORGE --skill forge-health

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Show FORGE health signals for this project, helping teams quickly identify code health issues and quality risks.

Core Features & Use Cases

  • Aggregate health signals: from board data via MCP when available, with a fallback to reading .pipeline/board.json.
  • Severity-grouped reports: present issues grouped by high, medium, and low with file, aspect, and notes.
  • Operational contexts: useful during reviews, audits, governance gates, and ongoing maintenance.

Quick Start

Inspect the latest health signals for your repository using the FORGE health workflow and review the summarized output.

Frequently Asked Questions about forge:health

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

FAQPage Schema
How do I check project health signals from a FORGE board during a code review?▼

To check project health signals, this Skill aggregates board data via the MCP tool or reads .pipeline/board.json, parsing and grouping code quality issues by severity to produce a structured health signals list for review.

What are code quality health signals and how do they help with pipeline maintenance?▼

Code quality health signals are aggregated metrics from board data that identify quality risks in a repository. They help teams spot issues quickly during planning gates, audits, and ongoing maintenance by grouping issues by high, medium, and low severity.

Do I need the MCP tool forge_read_board to review FORGE board metrics?▼

No, you do not need the MCP tool forge_read_board. The Skill uses it to aggregate board data when available, but includes a fallback to read local .pipeline/board.json files for health audits and governance gates.

Can I use this health signals summary for ongoing repository audits and planning gates?▼

Yes, you can use this health signals summary for operational contexts including ongoing maintenance, governance gates, and audits. It outputs a structured list grouped by severity with file, aspect, and notes for human review.

What is the best way to aggregate FORGE status review data for code quality risks?▼

The best way to aggregate FORGE status review data is parsing board metrics via MCP or local JSON fallback, which groups code quality risks by severity and outputs a structured list with file, aspect, and notes for quick human review.

Why does the health signals output group issues by severity with file and aspect notes?▼

Health signals output groups issues by severity with file and aspect notes to help teams quickly identify code health issues and quality risks during reviews, audits, and planning gates without manually parsing raw board metrics.

Related Skills

Explore More Software Engineering Skills→
Chulf58Chulf58

forge:overview

Inventory and summarize FORGE plugin ecosystem components from project files.

Community
Advanced
nuoyanruoshuinuoyanruoshui
47

milestone-review

Evaluate milestone readiness by consolidating sprint reports, codebase health, risks, and scope into a structured review with go/no-go recommendation.

Community
Advanced
HappyCowboyAIHappyCowboyAI

Pipeline Review Agent

Aggregate deal health across accounts into a manager-ready pipeline review.

Community
Advanced
Rune-kitRune-kit
82

sast

Run static analysis tools and normalize findings into unified severity levels.

Official
Advanced