git-commit
Generates well-structured git commit messages following conventional commit standards and best practices. Creates clear, descriptive commits with proper type prefixes (feat, fix, docs, refactor, etc.), concise subjects, and detailed bodies when needed. Use when committing code changes, creating git commits, writing commit messages, or when users mention "commit", "git commit", "commit message", "conventional commits", "changelog", or need help structuring version control messages. Ensures commits are atomic, descriptive, and follow team conventions.
What this skill does
# Git Commit Generates well-structured git commit messages following conventional commit standards and best practices. ## Key Principles 1. **Be specific**: Describe exactly what changed 2. **Be consistent**: Follow conventional commit format 3. **Be atomic**: One logical change per commit 4. **Be clear**: Write for others (including future you) 5. **Be complete**: Include why and context when needed 6. **Be conventional**: Follow standard format for automation ## Standard Format ``` <type>(<scope>): <subject> <body> <footer> ``` **Components:** - **type**: Category of change (required) - feat, fix, docs, refactor, perf, test, build, ci, chore, style, revert - **scope**: Area affected (optional) - auth, api, ui, db, etc. - **subject**: Brief description (required, ≤50 chars) - **body**: Detailed explanation (optional, wrap at 72 chars) - **footer**: Breaking changes, issue refs (optional) ## Basic Workflow 1. **Choose the commit type**: - `feat`: New user-facing functionality - `fix`: Bug fix for users - `docs`: Documentation only - `refactor`: Code restructuring without behavior change - `perf`: Performance improvement - `test`: Adding/updating tests - `build`: Dependency/build system changes - `ci`: CI/CD configuration changes - `chore`: Maintenance tasks - `style`: Code formatting - `revert`: Reverting previous commit 2. **Write subject line** (imperative mood, ≤50 chars): ``` ✅ feat(auth): add OAuth2 authentication ✅ fix(api): resolve race condition in user updates ❌ feat: added some stuff ❌ fix: bug fix ``` 3. **Add body if needed** (explain why, not just what): - Required for breaking changes - Recommended for complex changes - Wrap lines at 72 characters 4. **Include footer**: - Breaking changes: `BREAKING CHANGE: description` - Issue references: `Closes #123`, `Fixes #456` ## Quick Examples **Simple feature:** ``` feat(auth): add password reset endpoint ``` **Bug fix with context:** ``` fix(api): prevent null pointer in user preferences User preferences API crashed when optional fields were null. Added null checks and default values. Closes #456 ``` **Breaking change:** ``` feat(api)!: change response format to JSON:API spec BREAKING CHANGE: API responses now follow JSON:API format. Update client code to parse data from `data` key instead of root level. Closes #789 ``` ## Reference Documentation For detailed guidance, load these reference files as needed: - **[commit-types.md](references/commit-types.md)**: Complete list of commit types with examples - **[quick-reference.md](references/quick-reference.md)**: Decision trees and checklists - **[best-practices.md](references/best-practices.md)**: Atomic commits, meaningful messages, issue references - **[writing-guidelines.md](references/writing-guidelines.md)**: Subject line rules, scope selection, body formatting - **[common-scenarios.md](references/common-scenarios.md)**: Examples for typical development situations - **[common-mistakes-to-avoid.md](references/common-mistakes-to-avoid.md)**: Anti-patterns and how to fix them - **[team-conventions.md](references/team-conventions.md)**: Customizing conventions for teams - **[commit-message-structure.md](references/commit-message-structure.md)**: Detailed format specifications - **[commit-message-templates.md](references/commit-message-templates.md)**: Ready-to-use templates - **[commit-workflow.md](references/commit-workflow.md)**: Integration with git workflows - **[examples-by-project-type.md](references/examples-by-project-type.md)**: Examples for web apps, libraries, mobile, microservices - **[advanced-patterns.md](references/advanced-patterns.md)**: Complex scenarios and edge cases - **[commit-message-convention.md](references/commit-message-convention.md)**: Enforcement tools and configurations
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.