creating-commits

A tagline for {{campaign-name}} campaign: {{tagline}}

Updated Dec 10, 2025
One-click install
npx skills add https://github.com/zookanalytics/claude-devcontainer --skill creating-commits
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: creating-commits
Source: https://github.com/zookanalytics/claude-devcontainer/tree/main/packages/git-workflow/skills/creating-commits
Command: npx skills add https://github.com/zookanalytics/claude-devcontainer --skill creating-commits

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces a rigorous git commit workflow by requiring a pre-commit quality check, ensuring changes are atomic, and mandating conventional commit formats to keep a clean, reviewable history.

Core Features & Use Cases

  • Enforces a mandatory TodoWrite checklist BEFORE any commit to guarantee all steps are completed.
  • Guides staging and commit processes to ensure atomic units of change and prevents leaking secrets in commits.
  • Validates commit messages to follow conventional formats and records a commit state signal for workflow traceability.

Quick Start

Load this skill, complete the TodoWrite checklist with all required items, then proceed to stage changes and commit following the workflow.

Frequently Asked Questions about creating-commits

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

FAQPage Schema
How do I enforce atomic commits with pre-commit checks in git?

Atomic commits with pre-commit checks are enforced by automating a rigorous git workflow that validates quality, prevents secret leakage, and stages isolated units of change before committing.

What is the best way to ensure conventional commit messages in a software development workflow?

Ensuring conventional commit messages involves validating commit formats against established standards and recording a commit state signal for traceability, keeping the project history clean and reviewable.

How do I prevent secrets from leaking into git commits?

Preventing secrets from leaking into git commits requires proactive secret protection checks during the staging process, ensuring sensitive data is validated and blocked before any changes are committed.

Can I automate a TodoWrite checklist before staging changes?

Automating a TodoWrite checklist before staging changes is required to guarantee all workflow steps are completed, ensuring safe staging and validated atomic changes prior to the final commit.

Does this git commit workflow support software development teams needing traceable changes?

This git commit workflow supports software development teams by providing validated, traceable changes through structured processes, explicit commit-state signals, and enforced conventional commit formats.

Why do my git commits fail pre-commit quality checks?

Git commits fail pre-commit quality checks when changes are not atomic, commit messages lack conventional formats, or the required TodoWrite checklist items are not completed prior to staging.