skills.rest
ruchernchong
ruchernchongCOMMUNITY
Explore all skills by this author →
Website𝕏@ruchernchongGitHub

commit

Generate concise git commit messages and configure pre-commit checks.

1|Updated Jan 8, 2026
Search Tags:#git#security#commit#pre-commit#lint-staged#husky#gitleaks
One-click install
npx skills add https://github.com/ruchernchong/claude-kit --skill commit-ruchernchong
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/ruchernchong/claude-kit/tree/main/skills/commit
Command: npx skills add https://github.com/ruchernchong/claude-kit --skill commit-ruchernchong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes and secures git commits by guiding concise messaging and automating pre-commit checks.

Core Features & Use Cases

  • Enforces short (≤50 chars) commit messages for all changes to improve readability.
  • Automates pre-commit security checks with GitLeaks and Husky configuration.
  • Guides language conventions to maintain consistency across teams and projects.
  • Use Case: When preparing a bug fix or feature, generate a compliant commit message and ensure the repository is protected from secrets exposure.

Quick Start

Provide a short, compliant commit message for the staged changes and auto-configure required hooks if missing.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate concise git commit messages automatically?▼

Automated git commit messages are generated for staged changes by enforcing a 50-character limit and supporting optional issue footers to improve readability and standardize messaging across projects.

How do I set up Husky and GitLeaks pre-commit hooks?▼

Pre-commit hooks for Husky and GitLeaks are auto-configured when missing, automating security checks to prevent secrets exposure directly within the software project repository.

Why should I limit git commit messages to 50 characters?▼

Limiting git commit messages to 50 characters improves readability and enforces concise messaging conventions, ensuring that commit histories remain standardized and easy to scan across teams.

Can I add an issue number footer to a git commit message?▼

Optional issue footers can be appended to the git commit message, allowing developers to link staged changes directly to tracking issues while maintaining the strict character limit.

Does this pre-commit setup work without lint-staged installed?▼

Required tooling such as Husky and GitLeaks is auto-configured when missing, so the pre-commit checks function without requiring pre-existing lint-staged or hook installations.

What is the best way to prevent secrets from leaking in git commits?▼

Automating pre-commit security checks with GitLeaks during the commit process prevents secrets exposure by scanning staged changes before they are committed to the repository.

Related Skills

Explore More Software Engineering Skills→
trystan2ktrystan2k

husky

Install and maintain Husky git hooks in Node.js projects.

Community
Intermediate
yaronshereryaronsherer

smart-push

Automate Git commits, pushes, and GitHub Actions CI monitoring with auto-fixes.

Community
Advanced
ruchernchongruchernchong

security

Automate GitLeaks secret detection in Husky pre-commit workflows.

Community
Advanced
mintuzmintuz
3

commit-messages

Writes evidence-backed Conventional Commit messages from staged git diffs.

Community
Intermediate