skills.rest
mauriciodelrio
mauriciodelrioCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-usage

Enforces Git commit message, branch naming conventions via commitlint and Husky.

3|Updated Apr 12, 2026
Search Tags:#git#commitlint#conventional-commits#branch-naming#lint-staged#husky#pr-template
One-click install
npx skills add https://github.com/mauriciodelrio/delriodev-skills --skill git-usage
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-usage
Source: https://github.com/mauriciodelrio/delriodev-skills/tree/main/es-skills/software/git-usage
Command: npx skills add https://github.com/mauriciodelrio/delriodev-skills --skill git-usage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many teams struggle with inconsistent commit messages, branch names, and missing safeguards, leading to noisy history and integration issues.

Core Features & Use Cases

  • Conventional Commits enforcement: Guarantees clear, structured commit messages up to 150 characters.
  • Granular commit workflow: Encourages one logical change per commit and pushes only after feature completion.
  • Branch naming conventions: Enforces lowercase, hyphenated type/description format.
  • Automated linting and formatting: Uses Husky, lint‑staged, and commitlint to validate code and commit messages.
  • PR template and pre‑push checks: Ensures tests, type‑checking, and builds pass before integration.

Quick Start

Use the git-usage skill to apply standardized Git conventions throughout your repository.

Frequently Asked Questions about git-usage

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

FAQPage Schema
How do I enforce conventional commits in my Git repository?▼

You can enforce conventional commits in Git by using commitlint with Husky to validate commit messages up to 150 characters, ensuring structured project history before any commit is finalized.

What is the best way to automate branch naming conventions in a Git workflow?▼

Automating branch naming conventions in a Git workflow involves applying linting rules that enforce a lowercase, hyphenated type/description format, preventing inconsistent branches from being pushed to the remote repository.

Do I need Node.js and pnpm to use Husky and lint-staged for Git hooks?▼

Yes, you need a Node.js environment with pnpm to configure Husky and lint-staged, which together automate code formatting and pre-push checks to guarantee linear history and secure integration.

How does lint-staged integrate with Git pre-push checks?▼

Lint-staged integrates with Git pre-push checks by running automated validation, type-checking, and builds on staged files via Husky, ensuring tests pass before pull-request creation and code integration.

Can I use a PR template to enforce workflow conventions across my development team?▼

Yes, you can use a PR template alongside commitlint and pre-push checks to enforce workflow conventions, ensuring granular commits and consistent integration standards across development teams.

Related Skills

Explore More Software Engineering Skills→
remoodleremoodle
2

pnpm

Manage Node.js packages and dependencies using pnpm CLI commands.

Official
Intermediate
notquenotque
415

pr-pipeline

Automate pull request pipelines from staged changes to PR creation with gate-enforced reviews.

Community
Advanced
caseymanoscaseymanos

git-hooks

Configure Husky Git hooks for pre-commit linting, pre-push testing, and commit message validation.

Community
Advanced
tailcallhqtailcallhq
7.5k

minimal-skill

Resolves simple Forge tasks using built-in capabilities only.

Official
Basic