omc-gh-triage

Aggregate GitHub issues, PRs, CI statuses, and security alerts into a triage summary.

5|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/RobinNorberg/oh-my-copilot --skill omc-gh-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omc-gh-triage
Source: https://github.com/RobinNorberg/oh-my-copilot/tree/main/skills/omc-gh-triage
Command: npx skills add https://github.com/RobinNorberg/oh-my-copilot --skill omc-gh-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triaging GitHub projects can be time-consuming and error-prone. This skill surfaces open issues, PRs needing review, failing CI runs, and security alerts to help you prioritize work quickly.

Core Features & Use Cases

  • Open issue/PR triage: quickly identify items needing attention across issues, PRs, CI, and alerts.
  • Configuration-driven insight: reads .omcp/config.json to tailor data by owner/repo and default branch.
  • Actionable summary: presents a prioritized overview with recommended actions and next steps for responses and triage.
  • Guided workflow: step-by-step procedures for gathering data and rendering a triage report.

Quick Start

Run the triage workflow with gh triage or github triage to see a prioritized GitHub health summary.

Frequently Asked Questions about omc-gh-triage

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

FAQPage Schema
How do I triage GitHub issues and pull requests efficiently?

GitHub triage aggregates open issues, pending PR reviews, failing CI workflows, and security alerts into a structured summary with recommended actions. This helps you prioritize project health signals and address critical items quickly.

What is the best way to monitor failing CI runs and security alerts across repositories?

Monitoring CI runs and security alerts involves applying triage workflows to your default branch using GitHub CLI. The skill aggregates these health signals into a single report, highlighting failing workflows and vulnerabilities that need immediate attention.

Do I need GitHub CLI to generate a project health and triage summary?

Yes, generating the triage summary requires the GitHub CLI (gh) to gather data. It reads repository configuration from a .omcp/config.json file to identify the owner, repo, and default branch before running the data collection steps.

How do I configure repository settings for automated GitHub triage?

Configuring automated triage requires creating a .omcp/config.json file containing a github object. You must specify the owner, repo, defaultBranch, and an optional labelTriage value to tailor the data gathering to your specific software project.

Can I use this triage workflow for any software project on GitHub?

Yes, you can apply this triage workflow to typical software projects on GitHub. It focuses on standard signals like open issues, pending reviews, failing workflows, and security alerts, making it suitable for general repository health monitoring.