1-triage-issues

Ranks open GitHub issues and PRs by severity, mergeability, and contributor history.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers of the linkedin-mcp-server repository face a growing backlog of open issues and pull requests with no clear signal on what to tackle first. This Skill scans the live repository state and produces a ranked, evidence-backed priority list so maintainers can decide what to merge, fix, or investigate next. ## Core Features & Use Cases - Issue scoring: Rates every open issue on severity, reach (comments, reactions), age versus activity, and whether a fix PR already exists. - PR production-readiness audit: Checks mergeability, CI status, diff scope, locale-independent scraping selectors, test coverage, and contributor track record via the GitHub CLI. - Ranked report with next action: Outputs two ranked tables plus a concrete recommendation pointing to downstream reproduction or PR-verification skills. - Use Case: A maintainer asks "which PRs are production-ready?" and receives a table showing PR #386 is clean and mergeable while PR #366 has locale-dependent selectors and a stalled contributor. ## Quick Start Ask the assistant to triage the open issues and PRs in stickerdaniel/linkedin-mcp-server and rank them by urgency and merge readiness.

Frequently Asked Questions about 1-triage-issues

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

FAQPage Schema
How do I triage open GitHub issues and PRs as a maintainer?▼

Run this Skill against the repository to scan all open issues and PRs with the GitHub CLI. It scores each item on severity, reach, age, mergeability, and contributor history, then outputs ranked tables with a recommended next action.

How to check if a pull request is ready to merge?▼

The Skill verifies mergeable and mergeStateStatus fields, confirms all CI checks pass, audits diff scope, and greps for locale-dependent selectors like "Connect" or "Follow". A PR is only flagged ready when all checks pass.

Does this triage skill modify the repository or run code?▼

No, it is strictly read-only. It uses gh issue list, gh pr list, and gh search commands to gather data without checking out branches, starting the MCP server, or running scrapers.

Can I filter triage results by label or keyword?▼

Yes, pass an optional argument such as a label name like bug or enhancement, or freetext, to narrow the scope before scoring. Without an argument, every open issue and PR is scanned.

Why does the skill flag locale-dependent selectors in PRs?▼

LinkedIn button text like "Connect" or "Message" changes with user locale, so string-matching selectors break for non-English users. The repository's scraping rules require locale-independent detection, making such selectors a hard fail.

What are the limitations of automated issue triage?▼

Triage only ranks and recommends; it does not reproduce bugs or verify fixes. Confirmed reproduction requires the downstream /2-repro-issue skill, and PR validation requires /3-verify-pr-fix.