Smart Commit

Detect service changes, run validations, and format semantic commit messages.

381|261|Updated May 7, 2026
One-click install
npx skills add https://github.com/nudgebee/nudgebee --skill smart-commit-nudgebee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Smart Commit
Source: https://github.com/nudgebee/nudgebee/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/nudgebee/nudgebee --skill smart-commit-nudgebee

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The Smart Commit skill solves the problem of ensuring that commits are properly formatted and validated, particularly in a microservices architecture where service-specific validation is essential.

Core Features & Use Cases

  • Commit Validation: Automatically detects changed files and maps them to their respective services, running validations on each.
  • Service Mapping: Identifies and validates changes across various services with different languages and tools.
  • Commit Formatting: Generates service-scoped commit messages following semantic commit message standards.
  • Single Commit Policy: Ensures that Pull Requests targeting the main branch contain only one commit.
  • Quick Start: Automate your commit process and enforce best practices across your team.

Quick Start

Run the smart-commit skill with the commit message "fix(api-server): fix bug in user authentication".

Frequently Asked Questions about Smart Commit

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

FAQPage Schema
How do I automate commit validation for microservices architecture?▼

Automate commit validation by detecting changed files and mapping them to their respective microservices, then running associated build tool validations on each service before finalizing the commit.

How do I format semantic commit messages for service-scoped development?▼

Format semantic commit messages by mapping file changes to specific services and generating service-scoped commit text, such as prefixing messages with the affected service name like fix(api-server).

How do I enforce a single commit per pull request policy targeting the main branch?▼

Enforce a single commit per pull request policy by validating that PRs targeting the main branch contain only one commit, ensuring strict service-scoped development and semantic formatting compliance.

Do I need Git and build tools to run commit validation on microservices?▼

Yes, you need Git and various build tools to run commit validation on microservices, as the process requires detecting file changes and executing service-specific validations across different languages.

Can I run semantic commit formatting across services with different languages and tools?▼

Yes, you can run semantic commit formatting across services with different languages and tools by automatically identifying changed files, mapping them to various services, and applying service-specific validations.

What are the limitations of automating service-scoped commit message formatting?▼

Limitations of automating service-scoped commit formatting include its restriction to environments with a single commit per PR policy and its dependency on available build tools to execute service validations.