skills.rest
SeoJaeWan
SeoJaeWanCOMMUNITY
Explore all skills by this author →
GitHub

commit

Commit Git changes with Conventional Commits formatting and optional push.

1|Updated Mar 6, 2026
Search Tags:#git#workflow#commit#commitlint#hooks#branch#conventional-commits
One-click install
npx skills add https://github.com/SeoJaeWan/try-claude-code --skill commit-seojaewan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/SeoJaeWan/try-claude-code/tree/main/plugin/develop/skills/commit
Command: npx skills add https://github.com/SeoJaeWan/try-claude-code --skill commit-seojaewan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Commits Git changes following Conventional Commits rules to ensure standardized messages and easier release planning.

Core Features & Use Cases

  • Subject-limited commits: enforce a concise subject line (≤50 characters) per Conventional Commits.
  • Branch handling & use-case flexibility: decide to commit on the current branch or create a new branch, with optional push after commit.
  • Quality checks: run commitlint when configured, honor pre-commit hooks, and avoid editing git config or performing force-push.

Quick Start

Trigger a conventional commit on the current changes and optionally push the new commit to the remote after completion.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I format Git commits using Conventional Commits rules?▼

To format Git commits with Conventional Commits rules, apply structured prefixes to your changes while enforcing a concise subject line of 50 characters or less. This standardizes messages and simplifies release planning.

Can I create a new Git branch and push automatically after committing?▼

Yes, you can create a new Git branch and optionally push the new commit to the remote automatically after the commit completes. This workflow handles branch creation and pushing sequentially.

Does this commit workflow run commitlint and pre-commit hooks?▼

Yes, when configured, this commit workflow runs commitlint after the commit and honors existing pre-commit hooks. It ensures quality checks pass without editing Git config.

What are the limitations of using automated Conventional Commits formatting?▼

Limitations include strict enforcement of a maximum 50-character subject length and a strict policy against performing force-pushes or editing Git config, ensuring safe, non-destructive history management.

Why should I enforce a strict character limit on commit subjects?▼

Enforcing a strict subject length limit of 50 characters ensures concise, readable Git history. This practice aligns with Conventional Commits standards to facilitate easier release planning and automated changelog generation.

What is the best way to standardize Git workflow messages for release planning?▼

The best way to standardize Git workflow messages is applying Conventional Commits formatting to current changes. This enforces structured prefixes and concise subjects, streamlining release planning.

Related Skills

Explore More Software Engineering Skills→
theodrosyimertheodrosyimer

conventional-commit

Generate commitlint-compliant conventional commit messages from staged diffs.

Community
Intermediate
Sharper-FlowSharper-Flow
4

adv-ci-release

Automate release lifecycle with semver versioning and GitHub releases.

Official
Advanced
sunLeeesunLeee

check-commit-message

Validate Git commit messages against Conventional Commits rules.

Community
Intermediate
JannaelJannael
16

caveman-commit

Generates Git commit messages adhering to Conventional Commits format with strict subject and body rules.

Community
Intermediate