gh-triage

Automate triage of GitHub Pull Request review comments by filtering false positives.

2|Updated Feb 17, 2017
One-click install
npx skills add https://github.com/John2143/dotfiles --skill gh-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-triage
Source: https://github.com/John2143/dotfiles/tree/main/.claude/skills/gh-triage
Command: npx skills add https://github.com/John2143/dotfiles --skill gh-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

This Skill simplifies the process of triaging review comments in GitHub PRs, automatically filtering out false positives and irrelevant issues, saving time and reducing cognitive load.

Core Features & Use Cases

  • Automated Triage: Deduplicates and filters automated review findings from GitHub PR comments.
  • Customizable: Allow users to specify a PR number or upload a JSON file with findings.
  • Use Case: Quickly assess and respond to GitHub PR comments with accurate, filtered information, enhancing the review process.

Quick Start

Triage review comments for PR #7 with /skill:gh-triage --pr 7.

Frequently Asked Questions about gh-triage

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

FAQPage Schema
How do I automate GitHub PR review comment triage?

Automate GitHub PR review comment triage by running the Skill to deduplicate findings, filter false positives, and remove style-only nits. You can target a specific PR number or provide a custom findings JSON file for processing.

Does this PR triage tool filter out speculative issues and style nits?

Yes, this PR triage tool filters out speculative issues, style-only nits, and false positives. It processes automated review findings from GitHub PR comments to ensure you only assess accurate and relevant information.

Can I use a custom JSON file for GitHub PR findings instead of a PR number?

Yes, you can use a custom JSON file for GitHub PR findings instead of a PR number. The Skill handles both PR-specific automated review comments and manually provided findings JSON for flexible triage.

Do I need the GitHub API and Bash to triage pull request comments?

Yes, you need GitHub API access and Bash scripting capabilities to triage pull request comments. The Skill relies on the gh command-line tool to automate filtering and deduplicate review findings.

What is the best way to deduplicate automated review findings in GitHub?

The best way to deduplicate automated review findings in GitHub is using a triage Skill that processes PR comments and removes irrelevant issues. This reduces cognitive load by saving time spent manually reviewing false positives.