arrive-log

Append a timestamped Changes Made entry to the current ARRIVE Advance file.

Updated Feb 9, 2026

Search Tags:#workflow #logging #governance #audit-trail #advance #arrive #changes-made

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates recording and organization of modifications in ARRIVE by appending a Changes Made entry to the current Advance, ensuring traceability and auditability.

Core Features & Use Cases

Append a Changes Made entry to the current ARRIVE Advance file to document what changed.
Validate the formatting and timestamping of the entry to maintain a consistent audit trail.
Suitable for teams using ARRIVE governance to capture decisions, changes, and rationale during development and reviews.

Quick Start

Update the current Advance by adding a new Changes Made entry with the appropriate commit summary

Frequently Asked Questions about arrive-log

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

FAQPage Schema

How do I append a changes made entry to the current ARRIVE Advance for audit traceability?▼

Recording changes in ARRIVE governance involves extracting the active advance context, prompting for a commit type and summary, and updating the advance file with a timestamped entry to maintain a consistent audit trail.

What is an ARRIVE audit trail entry and when do I need to log one?▼

An ARRIVE audit trail entry is a timestamped record of modifications appended to an Advance file. You need to log one during development work, planning sessions, or reviews to ensure governance changes remain traceable and auditable.

Do I need a specific framework to use ARRIVE logging for governance changes?▼

No specific framework is required as there are no dependencies. You only need an existing ARRIVE Advance file and a summary of the modifications made to record a timestamped entry for your governance audit trail.

What's the best way to document modifications made during ARRIVE planning sessions?▼

The best way to document modifications during ARRIVE planning sessions is to append a Changes Made entry to the current Advance file, which automatically validates formatting and timestamping to maintain a consistent audit trail.

How does the ARRIVE workflow validate the formatting of a changes made entry?▼

The ARRIVE workflow validates formatting by extracting the context of the active advance, prompting for a commit type and summary, and generating a properly formatted, timestamped entry to maintain a consistent audit trail.