prioritize

Analyze GitHub pull requests, issues, and CI status to generate a prioritized work shortlist.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/NicoVIII/claude-config --skill prioritize-nicoviii
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prioritize
Source: https://github.com/NicoVIII/claude-config/tree/main/skills/prioritize
Command: npx skills add https://github.com/NicoVIII/claude-config --skill prioritize-nicoviii

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires dotnet, gh, and includes scripts (resource) components.

What problem does it solve?

This skill solves the cognitive overload of managing multiple GitHub repositories by automatically identifying which issues, PRs, and alerts require immediate human attention.

Core Features & Use Cases

  • Automated Triage: Scans all owned repositories to surface critical items like failing CI, security alerts, and pending review requests.
  • Contextual Ranking: Prioritizes tasks based on external dependencies (people waiting on you) and system health (broken builds).
  • Use Case: Use this when you are overwhelmed by a large backlog and need a clear, objective shortlist of the most important tasks to tackle across your entire GitHub portfolio.

Quick Start

Run the prioritize skill to generate a ranked list of tasks across all your GitHub repositories.

Frequently Asked Questions about prioritize

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

FAQPage Schema
How do I triage my GitHub backlog across multiple repositories?

To triage your GitHub backlog, this skill scans all non-archived repositories you own to generate a prioritized work shortlist. It analyzes pull requests, issues, and CI status to surface critical items requiring immediate attention.

How does automated GitHub issue prioritization handle failing CI builds?

Automated GitHub issue prioritization handles failing CI builds by ranking system health alerts and broken builds as high-priority tasks. It inspects CI status and uses shell scripts for deep-dive log inspection to identify blockers.

What's the best way to find pending pull request reviews across all my GitHub repos?

The best way to find pending pull request reviews is using automated triage to scan all your owned GitHub repositories. It identifies pending review requests and ranks them based on external dependencies like people waiting on you.

Do I need the dotnet and gh CLI tools to run automated GitHub triage?

Yes, you need the dotnet and gh CLI tools installed. The skill utilizes F# via the dotnet dependency for data gathering and the gh CLI to interact with your GitHub repositories and analyze repository activity.

Can I use this automated triage for archived GitHub repositories?

No, you cannot use this automated triage for archived GitHub repositories. The skill specifically operates across all non-archived repositories owned by the user to ensure it only evaluates active project activity.

Why use F# and shell scripts for GitHub task prioritization?

F# and shell scripts are used for GitHub task prioritization to ensure consistent, objective task ranking. F# handles data gathering from repository activity, while shell scripts perform deep-dive log inspection for failing CI builds.