commit-workflow

Split mixed diffs into atomic Conventional Commits with emoji annotations.

42|9|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/drvoss/everything-copilot-cli --skill commit-workflow-drvoss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-workflow
Source: https://github.com/drvoss/everything-copilot-cli/tree/main/skills/workflow/commit-workflow
Command: npx skills add https://github.com/drvoss/everything-copilot-cli --skill commit-workflow-drvoss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers avoid noisy or ambiguous git history by turning mixed diffs into atomic, well-formatted Conventional Commits with emoji annotations and clear scopes, improving traceability and CI compliance.

Core Features & Use Cases

  • Staged inspection and verification: Review staged or unstaged changes and run optional pre-commit checks before committing.
  • Interactive hunk splitting: Use interactive staging to split mixed diffs into separate, logical commits so each commit contains a single purpose.
  • Conventional Commit + emoji templates: Provide a standardized commit message format with type, optional scope, imperative description, and emoji mapping for consistent history and changelogs.
  • Use Case: Split a single pull request with feature, docs, and refactor changes into separate commits like feat(api), docs(api), and refactor(utils) with emoji prefixes for readability.

Quick Start

Stage your changes, interactively select hunks to create one logical change per commit, and write an emoji-prefixed Conventional Commit message describing the single logical change.

Frequently Asked Questions about commit-workflow

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

FAQPage Schema
How do I split mixed git diffs into atomic conventional commits?

Conventional commits with emoji annotations standardize git history by adding a type, scope, and imperative description prefixed with an emoji. This format improves readability and generates consistent changelogs for repositories with enforced CI linting.

Does commitlint work with emoji-prefixed conventional commit messages?

Commitlint works with emoji-prefixed conventional commit messages by formatting them to maintain compatibility with CI linting rules. The Skill ensures message formatting includes the correct type, scope, and emoji mapping to pass verification checks.

What's the best way to separate feature and docs changes in a single git staging area?

The best way to separate feature and docs changes in a single git staging area is interactive hunk splitting. You review staged or unstaged changes, select specific hunks, and commit them individually as feat or docs types with appropriate scopes.

How do I run pre-commit checks before creating conventional commits?

You run pre-commit checks before creating conventional commits by inspecting staged changes and executing optional verification steps within the workflow. This ensures your atomic commits meet repository linting standards before finalizing the commit.

Can I create separate logical commits from unstaged changes without manually editing git diffs?

You can create separate logical commits from unstaged changes using interactive staging to split mixed diffs without manual editing. The Skill guides hunk selection and formats the commit message with the correct type, scope, and emoji prefix.