Browse / Productivity Workflow / Commit Workflow

Commit Workflow

Creates well-structured, conventional Git commit messages based on staged changes.

SkillProductivity WorkflowCommunicationDocs StandardsOrchestrationGithub

The source repository doesn't declare a license. Check its terms before reusing the code.

Key features

  • Analyzes only staged files for precise commit creation (`git diff --cached`)
  • Enforces a conventional commit message format (e.g., `feat:`, `fix:`, `refactor:`)
  • Advocates for a single logical change per commit for a cleaner history
  • Integrates an automated workflow via the `/commit-creator` agent
  • Prompts for documentation (README.md) updates to reflect new features or changes

Use cases

  • Committing new features or bug fixes to a project.
  • Writing a clear and conventional commit message for staged changes.
  • Ensuring project documentation is updated alongside code changes in a commit.

FAQ

What does the Commit Workflow skill do?

This skill analyzes your staged files (`git diff --cached`) to automatically generate well-structured, conventional Git commit messages (e.g., `feat:`, `fix:`, `refactor:`), ensuring a clean and consistent project history.

When should I use this skill?

Use this skill whenever you're ready to commit changes. Simply ask Claude to "write a commit message" or "commit these changes," or use the `/commit-creator` agent for a fully automated workflow.

What are the key capabilities of this skill?

It precisely analyzes only staged files, enforces the Conventional Commits standard, prompts you to update documentation (like README.md) for new features, and integrates with an automated `/commit-creator` agent for one-command execution.

How does this skill improve my workflow?

It saves time by automating message creation, enforces a professional commit style across your project, and promotes best practices like documenting new features and making single-purpose commits for a readable Git history.