commit

Stage and commit baseline workflow changes with archive synchronization and consent checks.

5|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/friedbotstudio/baseline --skill commit-friedbotstudio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/friedbotstudio/baseline/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/friedbotstudio/baseline --skill commit-friedbotstudio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the risk and friction of finishing a workflow by coordinating the final archive, staging, consent, and commit steps in the right order. It helps prevent incomplete commits, missing closure stamps, and branch mistakes when closing out work.

Core Features & Use Cases

  • Validates that required workflow phases are complete before a commit can proceed.
  • Archives workflow state and related artifacts so the final commit lands the correct files together.
  • Checks branch topology, consent timing, and closure reconciliation to stop unsafe or partial commits.
  • Useful when you need to finish a Claude Code Baseline task, close an epic child, or commit staged changes with a clear reviewer-facing message.

Quick Start

Ask the assistant to prepare the current baseline work for commit and handle the required consent, staging, and branch checks.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I safely finish a git commit with workflow guardrails?

To safely finish a git commit, the workflow validates required phases, archives workflow state, and applies branch topology checks before staging named paths and executing the commit.

What is a consent-gated git commit and when is it needed?

A consent-gated git commit requires a valid consent token before proceeding, ensuring unsafe or partial commits are stopped when closing out baseline workflow tasks or epic children.

How do I archive workflow state before a final git commit?

Archiving workflow state synchronizes related artifacts and bundles so the final git commit lands the correct files together, preventing incomplete commits and missing closure stamps.

Does the commit workflow check branch topology before staging?

Yes, the commit workflow checks branch topology, consent timing, and closure reconciliation to stop unsafe or partial commits before explicitly staging named paths for the final git commit.

What happens if closure messages are not reconciled before a git commit?

If closure messages are not reconciled during preflight, the consent-gated git commit is blocked to prevent incomplete commits and missing closure stamps when finishing baseline workflow tasks.

Can I commit staged changes without a valid consent token?

No, a valid commit consent token is required to proceed with staging and committing baseline workflow changes, ensuring proper archive synchronization and branch-topology checks are satisfied.