1-triage-issues

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

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

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 repo 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 actions: Outputs two ranked tables plus a concrete recommended order of work, 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, with a recommendation to take it over via maintainer edits. ## Quick Start Ask the assistant to triage the open issues and PRs in stickerdaniel/linkedin-mcp-server and rank them by urgency, optionally passing a label like bug as a filter.

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 to scan all open issues and PRs via the GitHub CLI, score them on severity, reach, age, mergeability, and contributor history, and receive a ranked table with a recommended order of action. You can pass an optional label or keyword to narrow the scope.

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

The Skill checks mergeable and mergeStateStatus fields, CI statusCheckRollup results, diff scope, and test coverage for each PR. It also greps the diff for locale-dependent button text like Connect or Follow, which is a hard fail for scraping changes.

Does this Skill modify the repository or run code?▼

No, it is strictly read-only. It only runs gh issue list, gh pr list, gh search, and gh pr diff commands, and never checks out branches, starts the MCP server, or executes scrapers.

Can I filter the triage to only bug issues?▼

Yes, pass an optional argument such as a label name like bug or enhancement, or a freetext keyword. Both the issue and PR lists are filtered down before scoring begins.

Why does the Skill flag certain PRs as unsafe even when CI passes?▼

Locale-dependent string matching on button text and DOM class-name selectors are treated as hard fails regardless of CI status, because the project's scraping rules require locale-independent detection. Scope creep and missing tests also block a merge recommendation.

What are the limitations of this triage approach?▼

It does not reproduce bugs or verify fixes; those belong to downstream skills like /2-repro-issue and /3-verify-pr-fix. Scores rely on GitHub metadata and PR diffs, so issues lacking detail may be under-scored.