arrive-absorb

Generate initial ARRIVE governance artifacts and a report from an existing repository.

Updated Feb 9, 2026
One-click install
npx skills add https://github.com/srswart/good-control --skill arrive-absorb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arrive-absorb
Source: https://github.com/srswart/good-control/tree/main/.cursor/skills/arrive-absorb
Command: npx skills add https://github.com/srswart/good-control --skill arrive-absorb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Absorb an existing repository into ARRIVE governance by generating an initial draft of governance artifacts and a report.

Core Features & Use Cases

  • Scans a repository to produce a draft ARRIVE registry and system definitions.
  • Generates per-component advances and an unknowns report to guide governance work.
  • Useful for onboarding legacy codebases into ARRIVE for structured evolution and compliance.

Quick Start

Run arrive absorb draft using your repository identifiers to generate initial ARRIVE artifacts and a governance report.

Frequently Asked Questions about arrive-absorb

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

FAQPage Schema
How do I onboard an existing repository into ARRIVE governance?

To onboard an existing repository into ARRIVE governance, run the arrive absorb draft command using your repository identifiers. This generates an initial draft of governance artifacts and a report without overwriting existing ARRIVE files.

What is ARRIVE onboarding for legacy codebases?

ARRIVE onboarding is the process of integrating legacy or current codebases into structured governance. It scans the repository to produce a draft ARRIVE registry, system definitions, and per-component advances for compliance and evolution.

What files are generated when absorbing a repo into ARRIVE?

Absorbing a repo into ARRIVE generates deterministic outputs including arrive/registry.yaml, arrive/systems/**/system.yaml, arrive/systems/**/advances/*.md, and arrive/absorb/report.md to guide governance work.

Can I use arrive-absorb on a codebase that already has ARRIVE files?

Yes, you can use arrive-absorb on codebases with existing ARRIVE files. The process ensures deterministic outputs and does not overwrite existing ARRIVE files, preserving current governance artifacts.

Does arrive-absorb support drafting governance artifacts across multiple systems and components?

Yes, arrive-absorb applies to legacy or current codebases requiring ARRIVE onboarding and governance drafting across systems and components. It generates per-component advances and an unknowns report to guide governance work.

What is the best way to generate an initial ARRIVE registry and system definitions?

The best way to generate an initial ARRIVE registry and system definitions is to run arrive absorb draft with your repository identifiers. This produces deterministic draft governance artifacts and a report for structured evolution.