skills.rest
Collectively-Gary
Collectively-GaryOFFICIAL
Explore all skills by this author →
GitHub

commit / default

Bootstrap proposed entities and record receipts before irreversible commit finalization.

Updated Aug 27, 2026
Search Tags:#workflow orchestration#provenance#receipt verification#commit stage#entity bootstrap#merged entity resolution#operator escalation
One-click install
npx skills add https://github.com/Collectively-Gary/GaryOS --skill commit-default
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit / default
Source: https://github.com/Collectively-Gary/GaryOS/tree/main/data/skills/commit/default
Command: npx skills add https://github.com/Collectively-Gary/GaryOS --skill commit-default

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents missing-entity commits from failing silently by bootstrapping proposed entities into a durable state, then enforcing that an irreversible commit step is only performed when a matching per-playbook commit recipe exists.

Core Features & Use Cases

  • Entity bootstrap for proposed_entity refs: Detects missing entity paths, creates the entity index with atomic create-or-detect semantics, and appends canonical trail entries.
  • Merged-entity redirect handling: Resolves merged_into chains (with a safety cap) to ensure provenance and receipts target the live successor, not a tombstone.
  • Append-only receipts and provenance safety: Writes external receipts into both the action trail and the entity stages/ trail, and converts context refs from proposed_entity to related_entity after a successful bootstrap.
  • Default commit refusal with escalation: If no per-playbook commit skill exists, routes to the operator instead of guessing an irreversible action.

Quick Start

Ask the agent running the commit stage to apply commit/default to any action whose playbook falls back to default and whose proposed entities must be bootstrapped before proceeding.

Frequently Asked Questions about commit / default

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

FAQPage Schema
How do I safely bootstrap missing entities before performing an irreversible commit finalization?▼

To safely bootstrap missing entities before commit finalization, the workflow detects missing entity paths, applies atomic create-or-detect semantics to generate the entity index, and appends canonical trail entries to prevent silent failures.

How does merged-entity redirect resolution work during provenance reconciliation?▼

Merged-entity redirect resolution works by traversing `merged_into` chains within a defined safety cap to ensure provenance and receipts target the live successor entity rather than a tombstone, maintaining accurate records during finalization.

What happens when a playbook lacks a dedicated commit recipe and falls back to default?▼

When a playbook lacks a dedicated commit recipe, the default behavior refuses to guess an irreversible action and instead routes the commit stage to an operator gate to prevent unsafe finalization.

How do I record verifiable receipts for entity bootstrap actions in an append-only trail?▼

Recording verifiable receipts involves writing external receipts into both the action trail and the entity `stages/` trail using append-only semantics with correct sequence numbering, ensuring durable provenance safety.

When should I correct context refs from proposed_entity to related_entity in a commit workflow?▼

Context refs should be corrected from `proposed_entity` to `related_entity` immediately after a successful entity bootstrap, ensuring subsequent workflow orchestration stages reference the newly created durable state accurately.

Does commit stage finalization work without existing per-playbook commit recipes?▼

No, commit stage finalization requires a matching per-playbook commit recipe. If absent, the system escalates to an operator gate rather than attempting irreversible finalization through default fallback.

Related Skills

Explore More Software Engineering Skills→
MihaiOnSoftwareMihaiOnSoftware
1

commit

Draft final-state git commit messages with enforced style rules.

Community
Basic
lookatitudelookatitude
6

guild-finish-branch

Present merge and cleanup options after verifying tests and determining a base branch.

Community
Advanced
yashvinthanyashvinthan

context-driven-development

Manage project context artifacts as code with Conductor methodology.

Community
Intermediate
samjhechtsamjhecht
4

verify-governance

Verify governance artifacts for existence, structure, consistency, and freshness.

Community
Intermediate