skills.rest
cipherstash
cipherstashOFFICIAL
Explore all skills by this author →
Website𝕏@cipherstashGitHub

Commit Workflow

Run pre-commit checks and create atomic conventional commits.

17|Updated Oct 13, 2025
Search Tags:#code quality#automation#git#workflow#version control#commit#conventional commits
One-click install
npx skills add https://github.com/cipherstash/cipherpowers --skill commit-workflow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Commit Workflow
Source: https://github.com/cipherstash/cipherpowers/tree/main/plugin/skills/commit-workflow
Command: npx skills add https://github.com/cipherstash/cipherpowers --skill commit-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent commit practices lead to messy history, difficult debugging, and poor collaboration. This Skill enforces a structured process for high-quality, atomic commits, saving you time and reducing complexity in version control.

Core Features & Use Cases

  • Pre-commit Checks: Automatically runs linters, formatters, tests, and builds before committing, catching issues early.
  • Atomic Commit Composition: Guides splitting distinct changes into separate, logical commits for cleaner history.
  • Conventional Commit Messages: Enforces a standardized format for clear, searchable commit history and automated release notes.
  • Use Case: After completing a bug fix, use this Skill to ensure your changes are clean, tested, and documented with a conventional commit message, making future rollbacks or feature tracking effortless.

Quick Start

In a Claude Code session, after making changes:

/commit

The Skill will guide you through:

1. Running pre-commit checks (mise run check, mise run test)

2. Reviewing staged changes and diff (git status, git diff --staged)

3. Determining commit strategy (single vs. multiple atomic commits)

4. Writing a conventional commit message (e.g., feat(auth): add password reset)

Frequently Asked Questions about Commit Workflow

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

FAQPage Schema
How do I enforce consistent commit messages across my team?▼

Conventional commits standardize message format with type, scope, and description (e.g., feat(auth): add password reset). This Skill automatically validates and guides commit messages, ensuring searchable history and automated release notes for all contributors.

Can I run pre-commit checks like linting and tests before committing?▼

Yes. This Skill automatically runs linters, formatters, tests, and builds before committing, catching issues early and preventing low-quality code from entering version control.

How do I split my changes into atomic, logical commits?▼

Atomic commits group distinct changes separately for cleaner history and easier debugging. This Skill guides you through reviewing staged changes and determining whether to create single or multiple commits based on logical boundaries.

What's the best way to improve commit history quality in Git?▼

Structured commit practices—pre-commit validation, atomic grouping, and conventional formatting—eliminate messy history and make rollbacks, feature tracking, and collaboration significantly easier.

Do I need to know Git commands to use this workflow?▼

No. This Skill handles Git operations (staging, diffing, committing) and guides you interactively through each step, making the workflow accessible even if you're new to Git workflows.

Can this work when multiple agents contribute commits to the same codebase?▼

Yes. Enforcing conventional commits and pre-commit checks across all contributors ensures consistency, quality gates, and synchronized code practices regardless of who makes the changes.

Related Skills

Explore More Software Engineering Skills→
guille-galloguille-gallo

setup-pre-commit

Automate pre-commit hook setup with Husky and lint-staged for Git repositories.

Community
Intermediate
koralliskorallis
90

changelog-generator

Generates changelogs from Git history, commit messages, and pull requests.

Community
Basic
baphledbaphled
1

check-compliance

Run linting, formatting, security scans, and tests before committing code.

Community
Intermediate
mjbellantonimjbellantoni

squash-merge

Draft standardized commit messages and squash merge GitHub pull requests via gh CLI.

Community
Intermediate