commit

Generate pending-commit drafts and push changes with Build ID validation.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/bosmadev/claude --skill commit-bosmadev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/bosmadev/claude/tree/main/skills/commit
Command: npx skills add https://github.com/bosmadev/claude --skill commit-bosmadev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates the end-to-end commit drafting and safe execution process by turning code changes into a ready-to-commit narrative and guiding users through a two-phase workflow.

Core Features & Use Cases

  • Two-phase commit workflow: automatically generate a pending-commit.md and a Ready section for review before executing the commit.
  • Scope-prefix styling and auto-staging: creates a descriptive subject and pushes changes in a controlled, reviewable sequence.
  • Optional environment safety: supports .env encryption before commit when dotenvx is configured.

Quick Start

Invoke /commit to start the two-phase commit workflow and generate a ready-to-commit draft.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate a two-phase git commit workflow with pending reviews?▼

A two-phase git commit workflow generates a pending-commit.md draft for review before executing the push. It transforms tracked code changes into a ready-to-commit message, ensuring safe enforcement through pre-push validation.

What is a two-phase commit workflow and when do I need it for code review?▼

A two-phase commit workflow separates change staging from pushing by generating a pending-commit.md and a Ready section for review. You need it when your git projects require controlled, reviewable sequences and pre-push validation before changes are finalized.

How do I integrate Build ID and dotenvx encryption into my git push process?▼

To integrate Build ID and dotenvx encryption into your git push process, the workflow applies dotenvx encryption to your .env files and injects Build ID integration before enforcing a safe push during the second commit phase.

Can I use automated commit messages for git projects relying on a change-tracker?▼

Yes, you can automate commit messages for git projects relying on a change-tracker. The workflow transforms tracked changes into a descriptive subject with scope-prefix styling and auto-stages them into a ready-to-commit narrative.

Does automated git push validation work without dotenvx configured?▼

Automated git push validation works without dotenvx configured, but you lose the optional environment safety feature. The workflow still fulfills its phase-based pending-commit generation and safe push enforcement without .env encryption.

What is the best way to enforce a safe push sequence for automated code commits?▼

The best way to enforce a safe push sequence is using a phase-based workflow with pre-push validation. It creates a reviewable sequence by generating a pending-commit draft first, then applying safe push enforcement during execution.