1-triage-issues

Rank GitHub issues and pull requests by urgency, severity, and impact.

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/tr4m0ryp/linkedin-mcp-server --skill 1-triage-issues-tr4m0ryp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 1-triage-issues
Source: https://github.com/tr4m0ryp/linkedin-mcp-server/tree/main/.agents/skills/1-triage-issues
Command: npx skills add https://github.com/tr4m0ryp/linkedin-mcp-server --skill 1-triage-issues-tr4m0ryp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, pandas, numpy, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you efficiently prioritize issues and pull requests in your GitHub repository by ranking them based on urgency, implementation quality, and contributor track record.

Core Features & Use Cases

  • Issue Triage: Scan all open issues and PRs, ranking them by urgency, severity, user impact, age, and implementation quality.
  • PR Verification: Evaluate open PRs for mergeability, scope, locale safety, test coverage, and contributor history.
  • Use Case: When you need to decide which issues and PRs to tackle first as a core maintainer or when you want to ensure that your PRs are production-ready.

Quick Start

Run the triage skill with the argument 'bug' to filter and prioritize issues labeled as 'bug'.

Frequently Asked Questions about 1-triage-issues

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

FAQPage Schema
How do I prioritize GitHub issues and pull requests by urgency and impact?

You can prioritize GitHub issues by scanning and ranking them based on urgency, severity, user impact, age, and implementation quality. This allows you to systematically evaluate open PRs for mergeability, scope, and test coverage.

What factors are used to rank open issues during repository triage?

Issue triage ranks open items using urgency, severity, user impact, age, implementation quality, and contributor history. You can also filter and prioritize specific categories by running the triage process with arguments like 'bug'.

How do I verify if a pull request is production-ready before merging?

To verify if a pull request is production-ready, you evaluate it for mergeability, scope, locale safety, test coverage, and contributor history. This ensures your PRs meet quality standards before they are merged.

Do I need Python libraries and API access to triage GitHub issues?

Yes, you need GitHub API access and Python libraries like requests, pandas, and numpy for data processing and analysis. These dependencies are required to scan your repository and calculate the rankings.

Can I filter issue triage results to focus only on specific labels like bugs?

Yes, you can filter issue triage results by running the process with the argument 'bug'. This specifically filters and prioritizes issues labeled as 'bug' so you can tackle critical defects first.

Why are my pull requests being ranked low in the triage results?

Pull requests are ranked low when they have poor implementation quality, limited test coverage, or a weak contributor track record. Evaluating these factors helps maintainers decide which PRs require additional attention before merging.