commit

Creates git commits with bead-driven workflow and gitmoji formatting, staging specified files and pushing conditionally.

8|1|Updated Jan 21, 2024
One-click install
npx skills add https://github.com/azigler/dotfiles --skill commit-azigler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/azigler/dotfiles/tree/main/agents/skills/commit
Command: npx skills add https://github.com/azigler/dotfiles --skill commit-azigler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It standardizes how to create and push git commits that follow gitmoji formatting and a bead-by-bead workflow, reducing inconsistent commit messages and missed checkpoints.

Core Features & Use Cases

  • Beat-aligned commits and pushes: Creates exactly one commit per bead closure, with commits aligned to natural checkpoints between beads.
  • Consistent commit message structure: Enforces an emoji + scope subject line, supports an optional WHY body, and includes bead metadata plus co-author attribution.
  • Safety-focused staging rules: Guides selective staging (never git add -A or git add .) and warns against committing secrets like .env or credentials.
  • Worktree-aware pushing: Prevents pushing when operating in worktrees with branch names starting with worktree-agent-.

Quick Start

Run the commit workflow in order by closing the relevant bead, syncing bead state, staging only the specific changed files and the bead issues file, then creating the commit message using the required format and pushing to the remote if not in a worktree.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I format git commit messages with gitmoji and co-author attribution?

To format gitmoji commits, structure the subject line with an emoji and scope, add an optional WHY body, and append bead metadata plus co-author attribution to standardize codebase changes.

What is a bead-driven git workflow and when do I need to commit?

A bead-driven workflow structures git commits around bead closures, requiring exactly one commit per bead at natural checkpoints to avoid batching changes across multiple development stages.

How do I safely stage specific files without adding secrets to git?

To safely stage files, selectively add only specified changed files and the bead issues file, explicitly avoiding broad commands like git add -A or git add . to prevent staging secrets like .env.

Does this git commit workflow support pushing from worktree-agent branches?

This workflow restricts pushing from worktree-agent-* branches, enforcing worktree push rules to prevent unintended remote updates while still allowing commits to be created locally in agent worktrees.

What's the best way to avoid batching git commits during development?

The best way to avoid batching commits is to follow a bead-by-bead workflow, closing one bead at a time, staging only its specific files, and creating a single commit before pushing to the remote.