tribunal

Verify code review feedback against the codebase before implementing changes.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Milovan-Crowley/Consilium --skill tribunal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tribunal
Source: https://github.com/Milovan-Crowley/Consilium/tree/main/generated/claude/skills/tribunal
Command: npx skills add https://github.com/Milovan-Crowley/Consilium --skill tribunal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews often generate unclear or technically questionable feedback. This Skill enforces a disciplined approach to verify requirements and reasoning before implementing changes, reducing regressions and misinterpretations.

Core Features & Use Cases

  • Structured feedback interpretation: restate requirements in your own words to confirm understanding.
  • Codebase verification: cross-check feedback against the actual codebase and tests.
  • Incremental implementation: apply changes one item at a time, validating each before proceeding.
  • Pushback with rationale: provide technical justification when feedback seems incorrect.

Quick Start

When you receive code-review feedback, restate the requirement, verify against the codebase, and implement items one by one with testing.

Frequently Asked Questions about tribunal

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

FAQPage Schema
How do I verify code review feedback before implementing changes?

To verify code review feedback, restate the requirements in your own words, cross-check the suggestions against the actual codebase and tests, and apply incremental changes one item at a time to ensure technical rigor.

What is the best way to pushback on incorrect code review comments?

The best way to pushback on code review comments is to provide technical justification by evaluating the feedback against the codebase, ensuring your response includes clear rationale for why the suggested change is incorrect.

How do I process pull-request feedback to avoid regressions?

Process pull-request feedback by following a structured six-step workflow: read, understand, verify, evaluate, respond, and implement, validating each item with testing to reduce regressions and misinterpretations.

Does this structured code review verification work with any project?

Yes, this code review verification process applies to any project. It requires no specific dependencies, relying on a disciplined six-step approach to clarify and technically verify feedback before implementation.

Why should I restate code review requirements before writing code?

You should restate code review requirements to confirm your understanding of the feedback. This structured interpretation prevents misinterpretations and ensures you implement the correct changes with technical rigor.