review

Name: review
Availability: InStock
Author: Pandaala

Audit Edgion code review findings and determine bug, tradeoff, or false positive closure paths.

Updated Aug 27, 2026

Search Tags:#code review #workflow automation #false positive #RFC compliance #finding triage #accepted tradeoff #skills knowledge base

Ready to run

npx skills add https://github.com/Pandaala/Edgion --skill review-pandaala

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review
Source: https://github.com/Pandaala/Edgion/tree/main/skills/04-review
Command: npx skills add https://github.com/Pandaala/Edgion --skill review-pandaala

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you consistently audit code review findings in the Edgion codebase by quickly determining whether an alleged problem is a real bug, an accepted tradeoff, or a known false positive.

Core Features & Use Cases

Per-finding review decision support: Use it to process a single review finding end-to-end, including enforcing workflow gates and updating the skills knowledge base.
Topic-based routing to canonical rules: Selects the right sub-skill guidance for security, TLS, observability, DSL, federation, plugins, and more.
Closed-findings handling: Uses the project’s closure log to avoid re-escalating findings already fixed or explicitly accepted.

Quick Start

Use the review skill to handle a single issue file from tasks/review-*/ after you tell it the issue ID or the path to the finding.

Frequently Asked Questions about review

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

FAQPage Schema

How do I classify code review findings as real bugs or accepted tradeoffs?▼

Code review finding triage uses topic-based routing to evaluate each issue against canonical rules for security, TLS, observability, and federation patterns, then guides the correct closure path.

How do I check if a code review finding is a known false positive?▼

Checking for a known false positive involves querying the project's CLOSED-FINDINGS log to avoid re-escalating findings that were already fixed or explicitly accepted as tradeoffs.

Does code review workflow automation enforce RFC and Gateway-Aware constraint checks?▼

Workflow automation enforces RFC and Gateway-Aware constraint checks, scope gates, explicit verdict presentation, and mandatory subagent review to ensure operational compliance during finding triage.

Can I route code review findings to specific rules for TLS and observability patterns?▼

You can route findings to canonical sub-skill guidance for specific domains including security, TLS, observability, DSL, plugin runtime, federation, and performance pattern evaluation.

What is the best way to triage a single code review finding end-to-end?▼

The best way to triage a single finding end-to-end is to provide the issue ID or path to the review file, allowing the workflow to enforce gates, check constraints, and update the skills knowledge base.