reckoning

Categorize and prioritize GitHub PR feedback into an actionable triage report.

2|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/ppryde/pip-skills --skill reckoning-ppryde
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reckoning
Source: https://github.com/ppryde/pip-skills/tree/main/plugins/tribunal/skills/reckoning
Command: npx skills add https://github.com/ppryde/pip-skills --skill reckoning-ppryde

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps software teams transform scattered GitHub PR feedback into a single, actionable triage workflow by pulling all comments, categorising them, and presenting prioritized fixes and resolution steps.

Core Features & Use Cases

  • Gather PR details automatically from the repository, PR number, and remote metadata.
  • Fetch and merge inline comments, top-level issue comments, and review submissions to create a consolidated feedback view.
  • Categorise feedback by source and type, validate code-context, prioritise issues, and present an actionable plan with optional changes and thread resolution prompts.
  • Use cases include preparing a summary before a merge, tracking what was fixed, and coordinating bot and human reviews across multiple PRs.

Quick Start

Provide the repository and PR number or URL, then instruct Reckoning to triage and present the review feedback.

Frequently Asked Questions about reckoning

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

FAQPage Schema
How do I triage GitHub PR comments and reviews into an actionable plan?

Triage GitHub PR comments automatically by fetching inline comments, issue comments, and review submissions via REST and GraphQL, then deduplicating and categorizing them into a prioritized, actionable plan with optional fixes and thread resolution prompts.

What is the best way to consolidate scattered GitHub PR feedback before merging?

Consolidating GitHub PR feedback involves pulling all comments from multiple sources, validating code references, evaluating impact, and presenting a single prioritized triage report to coordinate bot and human reviews before merging.

How do I categorize and prioritize GitHub PR feedback from multiple sources?

Categorize GitHub PR feedback by source and type, validate code-context, evaluate impact, and prioritize issues to produce an actionable plan that optionally applies approved changes or resolves threads.

Can I automatically resolve GitHub PR threads after applying fixes?

You can resolve GitHub PR threads by applying user-driven actions through resolution prompts that apply approved changes or mark threads as resolved after validating code references and evaluating impact.

How does comment triage handle generated or binary files in PR reviews?

Comment triage handles generated or binary files by validating code references and evaluating impact during the categorization process, ensuring these files are appropriately managed within the actionable triage report.

Do I need to provide a PR URL to start triaging GitHub PR feedback?

To start triaging GitHub PR feedback, provide the repository and PR number or URL, then the skill automatically gathers PR details and remote metadata to fetch and merge all comments into a consolidated feedback view.