c-12-closeout

Enforce explicit commit approval and memory-ledger synchronization for worktree-backed edits.

27|4|Updated Mar 21, 2026

Search Tags:#git #worktree #external-memory #code-commit #approval-gate #memory-ledger #closeout

Ready to run

npx skills add https://github.com/Foxfire1st/agents-remember --skill c-12-closeout

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: c-12-closeout
Source: https://github.com/Foxfire1st/agents-remember/tree/main/.cursor/skills/c-12-closeout
Command: npx skills add https://github.com/Foxfire1st/agents-remember --skill c-12-closeout

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Closeout enforces explicit commit approvals and memory-ledger alignment to ensure worktree-backed edits are finalized safely and verifiably.

Core Features & Use Cases

Enforces an explicit approval gate before code, memory, and ledger changes are committed.
Coordinates with the worktree manager to synchronize code and memory state and prevent drift.
Useful in multi-user environments where external memory governance and traceability are required for deployments.

Quick Start

Use the c-12-closeout tooling to preview proposed commits and require explicit developer approval before applying the closeout.

Frequently Asked Questions about c-12-closeout

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

FAQPage Schema

How do I require explicit approval before committing code and memory changes in a git worktree?▼

To require approval before committing code and memory changes in a git worktree, enforce an explicit approval gate during closeout. You preview proposed commits and require developer approval before applying any finalization.

What is memory-ledger synchronization for code commits?▼

Memory-ledger synchronization for code commits is the process of aligning external memory state with code changes during finalization. It ensures worktree-backed edits are verifiable and prevents state drift across code and memory contexts.

Do I need external-memory mode and a shared worktree to enforce commit approval gates?▼

Yes, you need external-memory mode and a code-memory shared worktree to enforce commit approval gates. This closeout process operates on the worktree manager workflow and requires explicit preview and apply steps.

How do I prevent state drift when finalizing worktree-backed tasks?▼

To prevent state drift when finalizing worktree-backed tasks, coordinate with the worktree manager to synchronize code and memory state. This ensures gate-controlled closeout aligns all contexts before finalizing the commit.

When should I use an approval gate for code-memory closeout in multi-user environments?▼

You should use an approval gate for code-memory closeout in multi-user environments when external memory governance and traceability are required. It provides auditable, explicit commit approvals to finalize worktree-backed tasks safely.