code-review

Reject code-review submissions not approved for their declared areas.

13|1|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/Sermilion/skill-bill --skill code-review-sermilion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/Sermilion/skill-bill/tree/main/tests/fixtures/shell_content_contract/schema_unapproved_area/code-review
Command: npx skills add https://github.com/Sermilion/skill-bill --skill code-review-sermilion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fixture baseline used to reject unapproved entries in declared_code_review_areas.

Core Features & Use Cases

  • Enforces approval policy across declared code-review areas to automatically reject unapproved submissions.
  • Validates alignment with area-specific descriptors and shell ceremony instructions within fixture packs.
  • Supports audit-ready governance for code-review workflows in multi-area scenarios.

Quick Start

Review the provided code-review area entries and reject any item not approved for its declared area.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I enforce code-review approval policies for specific software engineering areas?

The Skill applies governance rules across multiple declared code-review areas to automatically identify and block submissions that have not been explicitly approved for their declared area.

How does automated governance validation work for multi-area code reviews?

Governance validation checks submitted entries against a fixture baseline of declared code-review areas, verifying alignment with area-specific descriptors and shell-ceremony instructions to ensure audit-ready compliance.

Can I automatically reject unapproved code submissions using a fixture baseline?

Yes, you can automatically reject unapproved code submissions by applying a fixture baseline that checks declared_area descriptors and blocks any code-review entries lacking the required area approval.

What is the best way to manage audit-ready governance for code-review workflows?

The best way to manage audit-ready governance is to enforce approval checks across multiple declared code-review areas, ensuring only validated submissions matching shell-ceremony alignment are accepted into the system.

Do I need shell-ceremony alignment to pass code-review validation checks?

Yes, shell-ceremony alignment is required to pass code-review validation, as the governance rules explicitly enforce checks against declared_area descriptors and shell-ceremony instructions within fixture packs.