commit
Conventional Commit Generator
Workflow
-
Run
git statusandgit diff HEADto analyze changes -
Stage files: user-specified only, or
git add -Afor all -
Commit using HEREDOC format:
git commit -m "$(cat <<'EOF' <type>(<scope>): <description> EOF )" -
Output:
<hash> <subject>
DO NOT: Modify code, push (unless asked), amend without request
Format
<type>[scope][!]: <description>
Types: feat, fix, perf, refactor, style, test, docs, build, ci, revert, chore
Subject: Imperative mood ("Add" not "Added"), capitalize first letter, no period, ~50 chars (max 72)
Scope: Optional noun for affected area (e.g., auth, api, parser)
Breaking changes: Add exclamation mark before colon: feat(api)!: Remove deprecated endpoints
Issue references: Use footer: Closes #123 or Fixes #456
Body (when needed)
Add body for non-trivial changes. Explain what and why, not how. Wrap at 72 chars.
More from trancong12102/ccc
test-driven-development
Guides strict Test-Driven Development (TDD) using the Red-Green-Refactor cycle. Ensures no production code is written without a prior failing test. Use this skill when implementing new features, fixing bugs, or refactoring code to ensure high test coverage and design quality. Triggers on phrases like 'TDD', 'write tests first', 'test-driven', 'red-green-refactor', 'watch it fail', 'test first', or 'behavior driven'.
8logging-best-practices
Logging best practices focused on wide events (canonical log lines) for powerful debugging and analytics
6design-postgres-tables
|
6