One-click install
npx skills add https://github.com/Collectively-Gary/GaryOS --skill commit-task-collectively-gary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit / task
Source: https://github.com/Collectively-Gary/GaryOS/tree/main/data/skills/commit/task
Command: npx skills add https://github.com/Collectively-Gary/GaryOS --skill commit-task-collectively-gary

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It ensures that completed task actions are durably committed—either by recording local artifacts as receipts or by executing commit-time entity merge operations with correct tombstoning, stage migration, and operator-safe failure handling.

Core Features & Use Cases

  • Pre-commit entity bootstrap enforcement (when applicable): Runs the required bootstrap procedure for any context_refs entries marked as proposed_entity, guaranteeing that related entities exist before commit writes proceed.
  • Two commit modes via dispatch: Supports generic task committing and the entity-merge variant that migrates loser stages, extends winner aliases, and writes merge trails plus receipts.
  • Crash-safe idempotency and reconciliation: Re-derives counters from on-disk truth, short-circuits when merges were already applied, and prevents duplicate merge trail or receipt entries across retries.
  • Operator-gated failure escalations: Detects validation failures, unsafe merge collisions, missing artifacts, and missing credentials, and escalates with actionable awaiting_operator states instead of writing inconsistent state.

Quick Start

Ask the system to commit a playbook: task action with task_variant: entity-merge for the approved entity merge, so it can tombstone the loser, migrate stages, extend winner aliases, and write the final receipts.

Frequently Asked Questions about commit / task

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

FAQPage Schema
How do I idempotently commit task actions to durable filesystem state?

To idempotently commit task actions, the system turns drafts into durable filesystem state and receipts by re-deriving on-disk counters and short-circuiting if merges were already applied. This prevents duplicate entries across retries.

What happens during an entity merge commit when there are concurrent merge races?

During an entity merge commit, the system reconciles concurrent merge races, tombstones loser entities, migrates stages to the winner, and extends winner aliases safely. It escalates unsafe collisions to an operator-gated state rather than writing inconsistent data.

Why do I need a pre-commit bootstrap for proposed entity context refs?

A pre-commit bootstrap for proposed entity context refs is required to guarantee that related entities actually exist on disk before any commit writes proceed. This enforcement prevents missing artifact failures and ensures filesystem state consistency.

How does the commit process handle validation failures and missing credentials?

The commit process handles validation failures and missing credentials by detecting them and escalating with actionable awaiting_operator states. It gates these failures to prevent writing inconsistent filesystem state or invalid external_refs receipts.

Can I commit task work that requires operator-mediated sends to external destinations?

Yes, you can commit task work requiring operator-mediated sends to external destinations. The system applies commit logic to these task actions and writes specific external_refs receipts with correct subkinds and failure-mode escalations.