pr-triage-and-summary

Inspect pull request diffs and summarize implementation changes and risks.

3|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/ldilov/harness-forge --skill pr-triage-and-summary
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-triage-and-summary
Source: https://github.com/ldilov/harness-forge/tree/main/skills/pr-triage-and-summary
Command: npx skills add https://github.com/ldilov/harness-forge --skill pr-triage-and-summary

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Concisely convert a pull request's change set into an implementation summary and risk assessment to accelerate code reviews.

Core Features & Use Cases

  • Inspect changed files, tests, docs, and validation evidence
  • Identify main change areas and summarize associated risks
  • Produce a compact handoff summary for engineers and stakeholders
  • Use Case: when a PR touches multiple components, generate a concise review brief and validation gaps

Quick Start

Submit the pull request diff to the agent and request a concise triage with changes, risks, and validation gaps.

Frequently Asked Questions about pr-triage-and-summary

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

FAQPage Schema
How do I generate a concise risk summary from a pull request diff?▼

Generate a pull request risk summary by submitting the diff to inspect changed files, tests, docs, and validation evidence, identifying risks and validation gaps to produce a compact handoff.

What is the best way to triage pull requests that span multiple files, tests, and docs?▼

Triage pull requests by inspecting changed files, tests, docs, and validation evidence to identify main change areas, summarize risks, and emit a compact implementation summary for code review workflows.

Can I get a concise review brief when a PR touches multiple components?▼

Yes, when a PR touches multiple components, submitting the diff produces a concise review brief containing the implementation summary, validation gaps, and risk assessment for stakeholders.

Does pull request triage work without external dependencies?▼

Pull request triage works without external dependencies, directly inspecting the submitted diff to identify change areas, summarize risks, and validate evidence for a compact handoff.

How do I identify validation gaps in a code review?▼

Identify validation gaps in a code review by submitting the pull request diff to inspect tests and validation evidence, summarizing missing checks and risks into a readable handoff.

When should I not use automated PR triage for code review?▼

Avoid automated PR triage for code review when diffs are trivial or single-file, as the compact implementation and risk summary is designed for changes spanning multiple files, tests, and docs.