custom-git-committing

Creates git commits following conventional-commit style with pre-commit hook enforcement.

1|Updated Apr 3, 2021
One-click install
npx skills add https://github.com/NaoyaMiyagawa/dotfiles --skill custom-git-committing-naoyamiyagawa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: custom-git-committing
Source: https://github.com/NaoyaMiyagawa/dotfiles/tree/main/.ai/skills/custom-git-committing
Command: npx skills add https://github.com/NaoyaMiyagawa/dotfiles --skill custom-git-committing-naoyamiyagawa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Inconsistent commit messages, skipped pre-commit hooks, and lost verification work make git history hard to review and audit. This Skill enforces disciplined commit practices so every change is traceable and reviewable. ## Core Features & Use Cases - Conventional Commit Messages: Writes commit messages using conventional-commit prefixes (feat, fix, chore, docs, refactor, style, test, build, ci, perf, revert) without scopes, focusing on the why rather than the what. - Hook Enforcement: Never passes --no-verify or -n, ensuring linting and pre-commit hooks always run. - Vendored Code Workflow: Commits ported or copied code as a pristine raw copy first, then applies integration edits as a separate commit so reviewers can diff against the original. - Verification Code Records: Commits temporary debug or test code and its revert as separate commits, preserving a citable record in git history. - Use Case: When porting a utility module from another repository, commit the untouched copy first, then commit your adaptations separately so the reviewer sees exactly what changed. ## Quick Start Commit my staged changes following the custom git committing conventions and report the commit hash.

Frequently Asked Questions about custom-git-committing

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

FAQPage Schema
How do I write a conventional commit message in git?

Use a conventional-commit prefix such as feat:, fix:, chore:, docs:, refactor:, style:, test:, build:, ci:, perf:, or revert: without a scope in parentheses. Focus the message on why the change was made rather than what or how it was implemented.

How should I commit code copied from another repository?

Commit the raw, unmodified copy first as its own commit, then make your integration and adjustment edits in a separate follow-up commit. This lets reviewers diff your changes against the pristine copy instead of reviewing everything as new code.

Should I ever use git commit --no-verify to skip hooks?

No. Pre-commit hooks such as linting must always run, so never pass --no-verify or -n. Skipping hooks bypasses the checks that keep the codebase consistent and can let broken code into history.

Why commit temporary debug code if I plan to delete it?

Committing throwaway verification code and then committing its revert leaves a citable record in git history. Even though the net diff is zero, the probe remains visible for future reference instead of disappearing when squashed or left uncommitted.

What should I do after making a git commit?

Report the commit hash after committing. This gives a precise reference point for the change that can be cited in reviews, discussions, or follow-up work.