로그인
trancong12102

commit

by @trancong12102 in Development
3
0
# Install this skill:
npx skills add trancong12102/agentskills --skill "commit"

Install specific skill from multi-skill repository

# Description

Generates Conventional Commits messages and can stage/commit changes. Use when asked to create git commit messages or perform a commit.

# SKILL.md

name: commit
description: Generates Conventional Commits messages and can stage/commit changes. Use when asked to create git commit messages or perform a commit.

Commit Message Generator (Conventional Commits)

Generate commit messages following Conventional Commits 1.0.0.

Execution Style

  • Be concise and direct; avoid preambles or long plans.
  • Use explicit formatting and exact output requirements.
  • Infer type, scope, and breaking from the changes when possible; ask only if truly ambiguous.
  • Prefer tool-driven git commands over manual edits.

Workflow

  1. Run git status and git diff HEAD.
  2. Stage only user-specified files; if user requests "all", use git add -A.
  3. Infer type/scope/breaking from the diff when possible; ask only if needed.
  4. Draft subject, body, and footers.
  5. Commit using HEREDOC:

```bash
git commit -m "$(cat <<'EOF'
():

EOF )" ``` 6. Output ` ` only. ## Scope Boundaries - Do: analyze changes, generate message, stage files, commit. - Don't: modify code, push, create branches, amend unless asked. ## Format 
<type>[optional scope][!]: <description>

[optional body]

[optional footer(s)]
## Spec Requirements - Type is required; scope is optional and uses `()`. - Description must follow `: ` and be a short summary. - Body is separated from subject by one blank line. - Footer is separated from body by one blank line and uses `: ` or ` #`. - Breaking change must use `!` or a `BREAKING CHANGE:`/`BREAKING-CHANGE:` footer. ## Types - `feat`: new feature (SemVer minor) - `fix`: bug fix (SemVer patch) - `perf`: performance improvement - `refactor`: restructure without behavior change - `style`: formatting only - `test`: add/update tests - `docs`: documentation only - `build`: build system/deps - `ci`: CI config - `chore`: other maintenance - `revert`: revert commit Breaking changes: use `!` or `BREAKING CHANGE:` footer (MAJOR). ## Subject - Max 72 chars (50 preferred). - Imperative, present tense; lowercase first letter. - No trailing period. ## Scope - Optional; use a noun for the affected module or area. - Omit if unclear. ## Body - Explain what/why, not how; wrap at 72. ## Footer - Common tokens: `BREAKING CHANGE`, `Refs`, `Closes`, `Fixes`, `Co-authored-by`, `Reviewed-by`, `Acked-by`. ## Examples 
feat: add email notifications for new messages

fix(cart): prevent ordering with empty shopping cart

feat(api)!: redesign authentication endpoints

Migrate from session-based auth to JWT tokens.

BREAKING CHANGE: /api/login now returns JWT instead of session cookie.

# Related Skills

facebook
feature-flags @facebook

Use when feature flag tests fail, flags need updating, understanding @gate pragmas, debugging...

★ 242,571
facebook
fix @facebook

Use when you have lint errors, formatting issues, or before committing code to ensure it passes CI.

★ 242,571
facebook
flags @facebook

Use when you need to check feature flag states, compare channels, or debug why a feature behaves...

★ 242,571

# Supported AI Coding Agents

This skill is compatible with the SKILL.md standard and works with all major AI coding agents:

⚡ Amp 🚀 Antigravity 🤖 Claude Code 🦀 Clawdbot 📝 Codex ▶️ Cursor 🤖 Droid 💎 Gemini CLI 🐙 GitHub Copilot 🪿 Goose 📊 Kilo Code 🔧 Kiro CLI 💻 OpenCode 🦘 Roo Code 🌲 Trae 🏄 Windsurf

Learn more about the SKILL.md standard and how to use these skills with your preferred AI coding agent.