skills.rest
AdelysAlberto
AdelysAlbertoCOMMUNITY
Explore all skills by this author →
Website𝕏@adelysalbertoGitHub

commits

Enforces conventional commit message format with branch IDs in Git workflows.

1|Updated Jul 18, 2025
Search Tags:#git#version control#conventional commits#biome#commit message#code standards#branch id
One-click install
npx skills add https://github.com/AdelysAlberto/md-configs-and-agents --skill commits-adelysalberto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commits
Source: https://github.com/AdelysAlberto/md-configs-and-agents/tree/main/agents-hermes/skills/commits
Command: npx skills add https://github.com/AdelysAlberto/md-configs-and-agents --skill commits-adelysalberto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often produce inconsistent commit messages that lack traceability to branches and tickets, making history hard to search and audit. This Skill standardizes every commit to a conventional format prefixed with the branch's numeric ID. ## Core Features & Use Cases - Standardized Commit Format: Enforces the pattern #<BRANCH_ID> <type>(<scope>): <description> so every commit links back to its branch. - Commit Type Taxonomy: Provides a defined set of types (feat, fix, docs, style, refactor, test, chore, perf, ci, build) with clear usage rules. - Pre-Commit Quality Gates: Requires running pnpm fix and pnpm check (Biome) before committing and forbids bypassing hooks with --no-verify. - Use Case: While working on branch feature/249517, stage your changes and let the agent produce a compliant message like #249517 feat(auth): add Google OAuth login support after verifying lint checks pass. ## Quick Start Commit my staged changes following the team's conventional commit standard with the current branch ID.

Frequently Asked Questions about commits

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

FAQPage Schema
How do I write a conventional commit message with a branch ID?▼

Extract the numeric ID from your branch name using git branch, then format the message as #<ID> <type>(<scope>): <description>. For example, on branch feature/249517 use git commit -m "#249517 feat(auth): add Google OAuth login support".

What commit types should I use in conventional commits?▼

Use feat for new features, fix for bug fixes, docs for documentation, style for formatting, refactor for restructuring, test for tests, chore for config and dependencies, perf for performance, ci for pipelines, and build for build system changes.

How do I get the branch ID before committing in Git?▼

Run git branch | grep '*' to show the current branch, then extract the numeric portion. For example, branch feature/249517 yields ID 249517, which prefixes the commit message.

Should I run lint checks before every commit?▼

Yes. Run pnpm fix to apply Biome auto-fixes and pnpm check to verify no remaining issues before committing. Do not use --no-verify to bypass pre-commit hooks unless explicitly authorized.

When is it acceptable to use git commit --no-verify?▼

Only when explicitly authorized. The standard forbids bypassing pre-commit hooks with --no-verify because hooks enforce code quality checks that keep the repository consistent.

Related Skills

Explore More Software Engineering Skills→
shysssthanhtrishysssthanhtri

conventional-commit

Generate Conventional Commit messages from staged Git diffs with Jira ticket IDs.

Community
Intermediate
sumrae412sumrae412
2

shipping-workflow

Automate conventional commits, pull requests, and 10-step code review before merging.

Community
Advanced
erfanzarerfanzar
27

requesting-code-review

Automate pre-commit code review with static checks, linting, and auto-fixes.

Community
Advanced
JiangAustinJiangAustin

chinese-commit-conventions

Standardize Chinese Git commit messages with commitlint, husky, and commitizen.

Community
Intermediate