1-triage-issues

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

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

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-dependent string selectors, DOM class selectors, and test coverage for each open PR. - Contributor track record analysis: Reviews each PR author's prior merged versus closed-unmerged PRs to flag risky large diffs from unproven contributors. - Use Case: A maintainer asks "which PRs are production-ready?" and receives two ranked tables — top issues and PR readiness — plus a concrete recommended order of action for the week. ## 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 two ranked tables with a recommended order of action.

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

The Skill verifies mergeable and mergeStateStatus fields, confirms all CI status checks pass, audits the diff for scope creep and locale-dependent strings, and checks whether tests were added before declaring a PR ready.

Can I filter the triage scan to specific labels or keywords?▼

Yes, pass an optional argument such as a label name like bug or enhancement, or a freetext keyword, and the Skill narrows both the issue and PR lists before scoring them.

Does this Skill modify the repository or run code?▼

No, it is strictly read-only. It never checks out code, starts the MCP server, or runs scrapers; reproduction and PR verification are delegated to the separate /2-repro-issue and /3-verify-pr-fix skills.

Why are locale-dependent strings flagged in LinkedIn scraping PRs?▼

Matching button text like Connect or Follow breaks when the user's LinkedIn locale differs, so the project's scraping rules require locale-independent detection. Any PR using such string matches or CSS class selectors is flagged as a hard fail.