commit-workflow

Validate worktree changes and synchronize documentation before committing.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/ephes/agent-stuff --skill commit-workflow-ephes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-workflow
Source: https://github.com/ephes/agent-stuff/tree/main/codex/skills/commit-workflow
Command: npx skills add https://github.com/ephes/agent-stuff --skill commit-workflow-ephes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aligns code changes with the broader development workflow by validating readiness for commit, ensuring synchronization with documentation and specifications, and preventing premature or inconsistent commits.

Core Features & Use Cases

  • Inspect the current worktree to determine if changes are commit-ready.
  • Synchronize implementation with related specs, tests, and documentation.
  • Create, or assist with creating, a clean commit only after all validations pass.

Quick Start

Validate the current worktree for commit readiness and perform the commit only when all checks pass.

Frequently Asked Questions about commit-workflow

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

FAQPage Schema
How do I validate my git worktree is ready for a commit?

To validate your git worktree for commit readiness, inspect current changes and enforce synchronization with related specs, tests, and documentation. This ensures all blockers are reported and resolved before you create a commit.

What is the best way to synchronize documentation and specs before committing code changes?

The best way to synchronize documentation and specs before committing is to assess your worktree changes and enforce documentation synchronization. This aligns implementation updates with related specs to prevent inconsistent commits.

How do I run targeted validations before finalizing a git commit?

You run targeted validations before finalizing a git commit by applying a commit workflow that inspects the worktree. It synchronizes specs, runs validations, and reports blockers to ensure changes are commit-ready.

Can I use a commit workflow to prevent premature commits during code refactoring?

Yes, you can use a commit workflow to prevent premature commits during code refactoring. It inspects the worktree, enforces documentation sync, and reports blockers, ensuring refactoring changes are fully validated before committing.

Why does my git commit workflow require tests and docs synchronization?

Your git commit workflow requires tests and docs synchronization to align code changes with the broader development workflow. This validation prevents premature or inconsistent commits by ensuring implementation matches related specifications.