professional-commit-workflow

Automate Git commit workflows by running pre-commit checks that validate code quality, generate conventional commit messages with emojis, and create atomic commits. This Skill detects your project type (Java, Python, React, or documentation), applies project-specific validators, analyzes staged changes, and orchestrates the full workflow end-to-end using Python scripts with zero external dependencies.

Yes, emoji-conventional commits work across Java, Python, React, and documentation projects. This Skill auto-detects your project type, applies the appropriate validation rules and commit types from its JSON configuration, and generates consistently formatted commits regardless of language or framework.

The Skill analyzes your staged diff, detects multiple logical changes, and recommends atomic commits—separate commits for each distinct change. This prevents mixing unrelated code into a single commit and keeps your Git history clean and reviewable.

Configure validation rules in commit_types.json and validation_rules.json. The Skill reads these JSON files, applies project-specific checks based on detected project type, runs validators against your staged code, and blocks commits if checks fail unless you use the --no-verify flag.

Yes, the Skill supports optional pushing to remotes after creating commits. Use the standard workflow command, and it will orchestrate staging analysis, validation, commit creation, and optional push as a single automated workflow.

The Skill requires Python and operates on repositories with Java, Python, React, or documentation projects. It cannot handle merge conflicts, requires explicit staging before use, and depends on correctly configured validation_rules.json and commit_types.json for accuracy.