Is GitHub CLI required for all features?

While standard commits only require Git, the automated pull request creation feature requires the GitHub CLI (gh) to be installed and authenticated in your environment.

Can it help if my pre-commit hooks fail?

Absolutely. The skill analyzes hook error output, attempts to fix linting or formatting issues automatically, and re-stages the fixes before re-attempting the commit.

How does it handle protected branches like main?

It includes a branch guard that detects when you are on main or master and prompts you to create a new feature branch before committing your changes.

Does this skill support custom commitlint rules?

Yes, it automatically detects and respects local commitlint configurations including custom types, scopes, and header length limits found in your repository.

Conventional Commit Creator

Name: Conventional Commit Creator
Author: seedium

byseedium

0•

Developer Tools

Automates the creation of standardized Git commits following the Conventional Commits specification with built-in branch safety and automated PR workflows.

The Create Commit skill streamlines the version control process by automatically generating well-formatted commit messages based on staged changes. It intelligently detects commit types and scopes, honors local commitlint configurations, and ensures branch safety by preventing direct commits to protected branches. By handling pre-commit hook failures and offering integrated pull request creation via the GitHub CLI, it transforms manual Git tasks into a seamless, AI-driven workflow that maintains repository health and consistency.

Key Features

01Branch guard protection for main/master with automated feature branch creation

02Integrated pull request creation (draft or ready) via GitHub CLI

03Automated pre-commit hook failure recovery and targeted linting fixes

04Intelligent integration with local commitlint configurations and custom rules

05Automatic Conventional Commits message generation following industry standards

060 GitHub stars

Use Cases

01Standardizing commit history across a team using Conventional Commits

02Automating the description of complex diffs into structured, meaningful messages

03Safely migrating staged changes from protected branches to new feature branches

Key Features

01Branch guard protection for main/master with automated feature branch creation

02Integrated pull request creation (draft or ready) via GitHub CLI

03Automated pre-commit hook failure recovery and targeted linting fixes

04Intelligent integration with local commitlint configurations and custom rules

05Automatic Conventional Commits message generation following industry standards

060 GitHub stars

Use Cases

01Standardizing commit history across a team using Conventional Commits

02Automating the description of complex diffs into structured, meaningful messages

03Safely migrating staged changes from protected branches to new feature branches