Git Commit

git-commit

Stage meaningful diffs and create commits with WHY-focused messages. Use whenever making git commits.

SKILL.md

Full skill instructions

Use /git:commit slash command to stage meaningful diffs and create commits with WHY-focused messages.

Only commit when:
1. ALL tests are passing
2. ALL compiler/linter warnings have been resolved
3. The change represents a single logical unit of work
4. Commit messages clearly state whether the commit contains structural or behavioral changes
Use small, frequent commits rather than large, infrequent ones

Copy and run in your terminal

npx -y skills add https://github.com/majiayu000/claude-skill-registry-data --skill git-commit

data/git-commit/SKILL.md

Categories

remotion-best-practices
Best practices for Remotion - Video creation in React
570.5K installs
high-end-visual-design
Teaches the AI to design like a high-end agency. Defines the exact fonts, spacing, shadows, card structures, and animations that make a website feel expensive. Blocks all the common defaults that make AI designs look cheap or generic.
407.8K installs
full-output-enforcement
Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.
358.6K installs
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
229.5K installs