arn-code-catch-up

Scan git history to identify untracked commits and generate CATCHUP_ records.

31|3|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/AppsVortex/arness --skill arn-code-catch-up
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: arn-code-catch-up
Source: https://github.com/AppsVortex/arness/tree/main/plugins/arn-code/skills/arn-code-catch-up
Command: npx skills add https://github.com/AppsVortex/arness --skill arn-code-catch-up

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates retroactive synchronization of commits with Arness artifacts by scanning git history and generating catch-up records.

Core Features & Use Cases

  • Scans git history to identify commits that lack Arness artifacts.
  • Generates CATCHUP_ records and boundary markers to document retroactive changes.
  • Uses templates to produce JSON CHANGE_RECORD.json envelopes and human-readable Markdown summaries.

Quick Start

Run /arn-code-catch-up to identify untracked commits and generate catch-up records.

Frequently Asked Questions about arn-code-catch-up

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

FAQPage Schema
How do I retroactively align git commits with artifacts?▼

To retroactively align commits with artifacts, this Skill scans a configurable window of git history to identify untracked commits and maps them to Arness artifacts. It then generates catch-up records to document the retroactive changes.

What is a catch-up record for untracked commits?▼

A catch-up record is a CATCHUP_ boundary marker generated to document retroactive changes. It pairs with a CHANGE_RECORD.json envelope and a human-readable Markdown summary to synchronize untracked commits with Arness artifacts.

Do I need git access to sync commits with Arness artifacts?▼

Yes, you need git access to sync commits with Arness artifacts. The scanning mechanism also requires plan templates and a specific template to generate the CHANGE_RECORD.json envelopes for the catch-up records.

How do I generate change records for untracked commits?▼

You generate change records by running the catch-up scan over your repository history. The scan identifies untracked commits and uses templates to produce CHANGE_RECORD.json envelopes alongside human-readable Markdown summaries.

Can I limit the git history scan window for catching up artifacts?▼

Yes, you can limit the git history scan window for catching up artifacts. The scan covers a configurable window to identify untracked commits and generate CATCHUP_ records only for that specific range.