review-senior

Route artifact reviews to composed gstack skills and publish an aggregate verdict.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/chughtapan/safer-by-default --skill review-senior
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-senior
Source: https://github.com/chughtapan/safer-by-default/tree/main/skills/review-senior
Command: npx skills add https://github.com/chughtapan/safer-by-default --skill review-senior

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Safeguarding review processes by centralizing routing of artifacts to the correct set of composed gstack skills, so there is a single, read-only aggregate verdict instead of ad-hoc judgments.

Core Features & Use Cases

  • Dispatches artifacts to the appropriate gstack skill sets based on artifact kind.
  • Aggregates per-skill verdicts into a single final verdict and publishes it to the artifact thread or sub-issue.
  • Handles missing skills gracefully with DONE_WITH_CONCERNS and provides a fallback reviewer when needed.
  • Enforces the single-skill rule; routing table is the source of truth for artifact-kind to composed-skill mapping.
  • Provides auditability by embedding craft checks and consensus logic into the aggregate verdict.

Quick Start

Provide an artifact URL to the safer-by-default system and run the safer:review-senior dispatcher to route the artifact to the configured gstack skills and publish the aggregate verdict.

Frequently Asked Questions about review-senior

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

FAQPage Schema
How do I route artifact reviews to the correct skills automatically?

You can route artifact reviews by providing an artifact URL to the dispatcher, which reads the SPEC routing table to map the artifact kind to the correct composed skills and produces an aggregate verdict.

How does aggregate verdict generation work for PR diffs and design plans?

Aggregate verdict generation dispatches PR diffs, design plans, UI-change proposals, and LLM-prompt changes to configured skills, then combines per-skill verdicts into a single read-only result published to the artifact thread.

What happens if a required skill is missing during artifact review routing?

Missing skills during artifact review routing are handled gracefully with DONE_WITH_CONCERNS status, and the system provides a safe fallback reviewer to ensure the process completes with auditability.

Can I use a custom routing table for dispatching different artifact kinds?

The routing table is the source of truth for artifact-kind to composed-skill mapping and enforces a single-skill rule, meaning dispatching follows the SPEC routing table configuration strictly.

Why does my review dispatcher enforce a single-skill rule for artifacts?

The single-skill rule safeguards the review process by centralizing routing, ensuring a single read-only aggregate verdict instead of ad-hoc judgments from multiple uncoordinated skills.