bill-code-review

Route code-review requests to the matching stack-specific review skill.

13|1|Updated Mar 16, 2026

Search Tags:#orchestration #governance #shell #telemetry #code-review #stack-routing #platform-packs

Ready to run

npx skills add https://github.com/Sermilion/skill-bill --skill bill-code-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bill-code-review
Source: https://github.com/Sermilion/skill-bill/tree/main/skills/bill-code-review
Command: npx skills add https://github.com/Sermilion/skill-bill --skill bill-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This shell-based skill coordinates cross-stack code reviews, ensuring a stable, governance-backed review flow and reducing pileups across platform packs.

Core Features & Use Cases

Stack-detection routing to dominant platform pack
Enforced output structure, severities, and telemetry
Delegated or inline execution depending on pack contracts and capabilities
Use case: You want to review a PR across GitHub, GitLab, or other stacks and get a consistent report.

Quick Start

Tell the system to initiate a code review of the current branch across registered platform packs.

Frequently Asked Questions about bill-code-review

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

FAQPage Schema

How do I route code review requests across different platform stacks?▼

Code review requests are routed using stack-detection logic to the dominant platform pack, which then executes its inline review logic while enforcing shell contracts and deterministic output structures.

What is stack-routing for code reviews and when do I need it?▼

Stack-routing for code reviews coordinates cross-stack governance by delegating review execution to matching platform packs, needed when reviewing PRs across multiple stacks like GitHub or GitLab for consistent reports.

Can I use this code review orchestration tool for both GitHub and GitLab PRs?▼

Yes, code review orchestration applies to PRs across GitHub, GitLab, and other stacks by routing to the registered platform pack and executing delegated or inline review logic based on pack contracts.

How do I enforce consistent output structures and severities during a cross-stack code review?▼

Enforce consistent output structures and severities by applying governance-backed shell contracts during code review routing, which standardizes telemetry and surfaces clear failure modes across all platform packs.

What are the limitations of using a shell-based skill for code review orchestration?▼

Limitations of shell-based code review orchestration include dependency on registered platform packs for execution; if a matching pack contract is missing, the routing logic cannot execute the inline review.