arrive-status

List affected systems and components and compute a reviewability score for ARRIVE-governed changes.

Updated Feb 9, 2026

Search Tags:#components #governance #score #systems #change-impact #reviewability #arrive-status

Ready to run

npx skills add https://github.com/srswart/good-control --skill arrive-status

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: arrive-status
Source: https://github.com/srswart/good-control/tree/main/.cursor/skills/arrive-status
Command: npx skills add https://github.com/srswart/good-control --skill arrive-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ARRIVE Status helps teams quickly understand the impact of changes by listing impacted systems and components and by providing a calculated reviewability score to guide governance decisions.

Core Features & Use Cases

Detects impacted systems and components using ARRIVE's change analysis across the repository working directory.
Generates a structured reviewability score with a color indicator and detailed breakdown, including potential risk signals.
Guides operators through required gates, notices if resident components are touched, and suggests split checkpoints for Yellow/Red scores.

Quick Start

Run arrive status to detect impacted systems, then run arrive score to view the reviewability breakdown.

Frequently Asked Questions about arrive-status

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

FAQPage Schema

How do I check the change impact of repository updates on affected systems?▼

To check change impact, analyze the repository working directory using ARRIVE's change analysis to list affected systems and components. This process identifies resident components and computes a reviewability score to guide governance decisions.

How do I calculate a reviewability score for code changes?▼

Calculate a reviewability score by running arrive score after detecting impacted systems. This generates a structured breakdown with color indicators and risk signals to guide governance and review readiness decisions.

What is change-impact analysis and when do I need it for governance?▼

Change-impact analysis identifies systems and components affected by repository modifications. You need it for ARRIVE-governed changes to detail gated actions, track resident components, and produce deterministic, auditable outputs for compliance.

Can I use ARRIVE tooling for multi-system governance artifacts?▼

Yes, ARRIVE tooling applies to governed changes across multiple systems and governance artifacts. It uses existing system definitions to detect impacted components and calculate reviewability scores for auditable governance.

What should I do when a reviewability score returns Yellow or Red?▼

When a reviewability score returns Yellow or Red, the system suggests split checkpoints to guide operators. It details required gates and notices if resident components are touched, helping manage elevated risk signals.

How do I identify gated actions for affected components in a repository?▼

Identify gated actions by applying ARRIVE tooling to repository changes. The system evaluates existing definitions to detail required gates and determine whether resident components are touched before producing an auditable output.