How does it handle security concerns?

The skill includes a built-in sanity check step to inspect staged changes for secrets, tokens, and accidental debug logging before the commit is finalized.

Does this skill support Conventional Commits?

Yes, this skill is specifically designed to enforce and generate commit messages that follow the Conventional Commits specification (type(scope): summary).

Does it work with Windows PowerShell scripts?

Yes, it includes specific logic for executing committer.ps1 scripts, including handling execution policy blocks using pwsh.

Can I verify my code before committing?

Yes, the workflow includes a step to run the repo's fastest meaningful verification, such as unit tests or linting, before proceeding.

Can I use this to split one large file into multiple commits?

Absolutely. The workflow encourages patch staging (git add -p), allowing you to select specific code blocks (hunks) to include in different commits.

Commit Work

Name: Commit Work
Author: Masked-Kunsiquat

byMasked-Kunsiquat

Developer Tools

Automates the creation of logically split, high-quality Git commits using Conventional Commit standards.

About

Commit Work is a specialized Claude Code skill designed to streamline the version control process by guiding users through logical staging and documentation. It helps developers break down large sets of changes into manageable, atomic commits, enforces the Conventional Commits specification for standardized messaging, and includes sanity checks to prevent the accidental inclusion of secrets or debug logs. By following a structured workflow that includes patch staging and pre-commit verification, it ensures a clean, readable, and professional repository history.

Key Features

Interactive patch staging (git add -p) guidance
Logical change splitting and atomic commit scoping
Pre-commit sanity checks for secrets and debug code
Integration with custom staging scripts like committer.ps1
Automated Conventional Commits message generation
0 GitHub stars

Use Cases

Enforcing consistent commit message standards across a development team
Reviewing and staging specific hunks of code within a single file
Splitting a large session of mixed refactoring and feature work into separate commits

About

Key Features

Interactive patch staging (git add -p) guidance
Logical change splitting and atomic commit scoping
Pre-commit sanity checks for secrets and debug code
Integration with custom staging scripts like committer.ps1
Automated Conventional Commits message generation
0 GitHub stars

Use Cases

Enforcing consistent commit message standards across a development team
Reviewing and staging specific hunks of code within a single file
Splitting a large session of mixed refactoring and feature work into separate commits