← All plugins

Plugin III — PR Review Workflow

Tribunal:
Reckoning

No comment goes unresolved.

PR comment review, categorisation, prioritisation, and resolution. Pulls every comment from a GitHub PR — bot or human — validates each against the actual current code, proposes fixes, applies them with your approval, and resolves the threads. Nine steps. Every time.

/tribunal:reckoning

The workflow

Nine steps. Every pull request.

Reckoning works through the same nine steps on every invocation. No shortcuts. No comments skipped.

01
Gather Auto-detects repo and PR number from your current branch
02
Check Verifies any bot reviews have finished running before fetching
03
Fetch Pulls all comments via three GitHub APIs (inline, issue-level, review submissions) + GraphQL for thread resolution status
04
Categorise Labels each comment by source (agent / human) and type (logic, security, tests, style, docs, suggestion, question, praise)
05
Validate Reads the actual code at each referenced location — catches bot false positives and stale comments from earlier commits
06
Prioritise Critical → High → Medium → Low, with duplicate detection and conflict flagging
07
Present Structured report with proposed fixes for each item
08
Action Applies fixes you approve — never auto-applies
09
Resolve Offers to resolve actioned threads on GitHub after all fixes are applied

Invocation modes

One skill. Four modes.

/tribunal:reckoning

Default triage

Fetches all unresolved comments on the current branch's open PR, runs the full nine-step workflow. The standard invocation.

/tribunal:reckoning PR progress report

Progress report

Shows a round-by-round table of all review feedback across the PR's lifetime — what's been fixed, what's outstanding, what's stale.

/tribunal:reckoning resolve threads

Resolve only

Lists all unresolved threads with their file:line references and asks which to resolve. Skips the triage workflow.

/tribunal:reckoning https://github.com/owner/repo/pull/42

Specific PR

Targets a specific PR rather than auto-detecting from the current branch.

Validation

Every comment verified against live code.

By default, Reckoning reads the actual code at every referenced file and line before presenting any comment. Bot reviewers frequently comment on outdated diffs. Line numbers shift as commits stack. Nothing is auto-dismissed — you see everything with the assessment clearly shown and make the final call.

Valid Comment accurately describes a current issue
Likely valid Probably correct — confirm before actioning
Uncertain Inconclusive — context required
Likely invalid Probably a false positive or stale comment

Supported reviewers

Bot or human — all testimonies heard.

Reckoning recognises automated agents and categorises their feedback accordingly. Human reviewers are tracked separately and weighted differently.

CodeRabbitcoderabbitai
Cubiccubic-*
Augmentaugment-*
GitHub Copilotcopilot
Dependabotdependabot
Renovaterenovate
Codecovcodecov
SonarCloudsonarcloud
Snyksnyk
Any [bot]username ending in [bot], -bot, _bot