rtk-triage

Correlate GitHub issues and pull requests to detect duplicates, gaps, and conflicts.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/Star1131/smart_insole --skill rtk-triage-star1131
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rtk-triage
Source: https://github.com/Star1131/smart_insole/tree/main/.claude/skills/rtk-master/.claude/skills/rtk-triage
Command: npx skills add https://github.com/Star1131/smart_insole --skill rtk-triage-star1131

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual overhead of reviewing GitHub issues and pull requests separately by combining them into one coordinated triage workflow that exposes duplicates, overlaps, gaps, and unresolved risks.

Core Features & Use Cases

  • Parallel collection: Gathers open and closed issues plus open pull requests so the backlog can be reviewed with current repository context.
  • Cross-analysis: Matches issue bodies, PR bodies, labels, and changed files to detect double coverage, security holes, dirty PRs, and items with no tracked fix.
  • Operational triage: Produces structured tables and a saved daily report for sprint planning, reviewer coordination, and release readiness checks.

Quick Start

Ask the AI to run the RTK triage workflow in French and save the resulting issue-and-PR analysis report to claudedocs.

Frequently Asked Questions about rtk-triage

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

FAQPage Schema
How do I cross-analyze GitHub issues and pull requests for backlog triage?

To cross-analyze GitHub issues and pull requests, this Skill correlates open issues, open PRs, and recent closures to detect duplicates, coverage gaps, and conflicting work. It matches issue bodies, PR bodies, labels, and changed files to expose overlaps for backlog triage.

What is the best way to find duplicate GitHub issues and conflicting pull requests?

Finding duplicate GitHub issues and conflicting pull requests is done by cross-analyzing issue and PR bodies, labels, and changed files. This Skill matches these data points in parallel to uncover double coverage and dirty PRs during repository triage.

Can I generate a daily GitHub triage report and save it to claudedocs?

Yes, you can generate a daily GitHub triage report and save it to claudedocs. The Skill produces structured tables from its issue and PR cross-analysis, allowing you to save the resulting operational triage report directly for sprint planning.

How do I identify coverage gaps and unresolved security risks in my GitHub backlog?

Identifying coverage gaps and unresolved security risks involves comparing open issues against open pull requests and recent closures. This Skill detects items with no tracked fix and security holes by cross-analyzing repository backlog data in a single workflow.

Does this GitHub triage workflow require any external dependencies or components?

No, this GitHub triage workflow requires no external dependencies or components. It operates independently to gather open and closed issues plus open pull requests, categorize them, and perform cross-analysis to find backlog gaps and PR conflicts.