665,000+ skills indexed

devsepnineCOMMUNITY

Explore all skills by this author →

Verified:Website 𝕏@devsepnine GitHub

commit-rules

Enforces Git commit messages with type, [PP-XXXX] ticket, and pre-commit security checks.

1|Updated Feb 24, 2026

Search Tags:#git #commit #pre-commit #code-quality #version-control #conventional-commits

One-click install

npx skills add https://github.com/devsepnine/hibi_ai --skill commit-rules-devsepnine

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: commit-rules
Source: https://github.com/devsepnine/hibi_ai/tree/main/src/skills/commit-rules
Command: npx skills add https://github.com/devsepnine/hibi_ai --skill commit-rules-devsepnine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes commit messages and enforces safe Git practices to improve traceability, accountability, and code review efficiency across teams.

Core Features & Use Cases

Enforced commit formats (type: [ticket] title) with allowed types (feat, fix, refactor, style, docs, test, chore).
Ticket number format [PP-XXXX] that must align with feature branches.
Pre-commit security checks to prevent secret leakage and enforce best practices.
Commit splitting guidance to keep changes small and independently reviewable.
Suitable for everyday development, code reviews, and release preparation.

Quick Start

Provide your intended commit type, ticket number, and a concise title to format the next commit per the rules.

Frequently Asked Questions about commit-rules

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

FAQPage Schema

How do I enforce conventional commit messages in git?▼

To enforce conventional commit messages, apply rules requiring a standardized type, ticket number, and title format, such as `feat: [PP-XXXX] title`. This standardizes git history and improves traceability across feature work and bug fixes.

What are the best pre-commit checks to prevent secret exposure?▼

Pre-commit checks to prevent secret exposure scan staged changes for sensitive data before finalizing the commit. This enforces safe Git practices and blocks accidental credential leakage during refactoring or documentation updates.

How do I format git commits for better code review efficiency?▼

Format git commits using an enforced structure with allowed types like feat, fix, or refactor, alongside a matching ticket number. This keeps changes small and independently reviewable, directly boosting code review efficiency.

Can I use a ticket number format to align commits with feature branches?▼

Yes, you can align commits with feature branches by enforcing a strict ticket number format like [PP-XXXX]. This ensures accountability and links commit history directly to the corresponding feature branch context.

Why should I split commits during a large refactoring task?▼

You should split commits during refactoring to keep changes small and independently reviewable. Commit splitting guidance prevents large, unmanageable diffs and ensures each logical change is isolated for safer version control.

Related Skills

Explore More Software Engineering Skills→

merge-to-staging

Merge the current feature branch into a fresh staging branch with automated conflict analysis.

commit-push-with-changelog

Enforces CHANGELOG.md updates and confirms pushes before executing git commits.

requesting-code-review

Automate pre-commit code review with static analysis and security scanning.

RyoMurakami1983

git-initial-setup

Automates GitLab project and repository setup for streamlined onboarding and management.