skills.rest
nexus-a1
nexus-a1COMMUNITY
Explore all skills by this author →
GitHub

commit

Stage changes and create conventional commits with pre-commit checks.

Updated Mar 29, 2026
Search Tags:#git#workflow#commit#pre-commit#ticket#conventional
One-click install
npx skills add https://github.com/nexus-a1/claude-skills --skill commit-nexus-a1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/nexus-a1/claude-skills/tree/main/skills/commit
Command: npx skills add https://github.com/nexus-a1/claude-skills --skill commit-nexus-a1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stage and commit changes with a conventional message, running pre-commit checks automatically and optionally prefixing with a ticket number.

Core Features & Use Cases

  • Enforces conventional commit format (type(scope): description) to standardize commit history.
  • Runs pre-commit checks automatically before committing to catch style, tests, or lint issues.
  • Supports optional ticket prefixes to link commits to work items and improve traceability.
  • Use Case: A developer commits a small change on a feature branch with a ticket number to ensure traceability and maintain a clean history.

Quick Start

Invoke the commit workflow to stage your changes and create a conventional commit message with pre-commit checks.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate conventional commit messages with pre-commit checks?▼

To automate conventional commit messages, this workflow stages your changes, enforces the type(scope): description syntax, and runs pre-commit checks automatically to catch lint or test issues before committing.

Can I link a git commit to a ticket number automatically?▼

Yes, you can link a git commit to a ticket number by providing the ticket ID, which the workflow uses to prefix the conventional commit message and improve project traceability.

What is the conventional commit format for a feature branch?▼

The conventional commit format for a feature branch is type(scope): description, which this workflow strictly enforces to ensure a clean and standardized git history across small changes.

Does this workflow run pre-commit checks before creating a conventional commit?▼

Yes, the workflow runs pre-commit checks automatically before creating a conventional commit, catching style, tests, or lint issues to ensure a clean history on your feature branch.

When should I use an automated conventional commit workflow?▼

You should use an automated conventional commit workflow when committing small changes on feature branches, ensuring strict message syntax validation and clean history without manual formatting checks.

Do I need to install dependencies to enforce conventional commit syntax?▼

No, you do not need to install external dependencies to enforce conventional commit syntax, as the workflow operates independently to stage changes, validate messages, and run pre-commit checks.

Related Skills

Explore More Software Engineering Skills→
OmexITOmexIT
13

finalize

Automate linting, tests, cleanup, commit, and PR generation for code changes.

Community
Advanced
VYRE-StudiosVYRE-Studios

commit-push-pr

Commit staged changes, push the branch, and open a pull request via GitHub CLI.

Official
Intermediate
zeronx798zeronx798

requesting-code-review

Scan staged git changes for security issues and quality regressions.

Community
Advanced
eykdeykd

commit

Create git commits following the conventional commit format.

Community
Intermediate