commit-detection

Detect conventional commit types from git changes and file patterns.

22|3|Updated Jan 10, 2026

Search Tags:#git #developer tools #code review #versioning #commit #conventional commits

Ready to run

npx skills add https://github.com/fusengine/agents --skill commit-detection

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-detection
Source: https://github.com/fusengine/agents/tree/main/plugins/commit-pro/skills/commit-detection
Command: npx skills add https://github.com/fusengine/agents --skill commit-detection

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers determine the most appropriate conventional commit type (e.g., feat, fix, chore) based on the nature of their code changes, ensuring consistent and informative commit messages.

Core Features & Use Cases

Automated Commit Type Suggestion: Analyzes git diffs and file patterns to suggest commit types.
Scope Determination: Identifies the relevant scope for a commit message based on file paths.
Use Case: Before committing a bug fix, this skill will analyze the changed files and diff content to suggest the fix commit type, potentially with a scope like api if the fix is in the API layer.

Quick Start

Use the commit-detection skill to analyze the current staged changes and suggest a commit type.

Frequently Asked Questions about commit-detection

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

FAQPage Schema

How do I determine the correct conventional commit type from my git diff?▼

To determine the correct conventional commit type from a git diff, analyze modified files, change statistics, and diff content. Categorize files into types like docs, test, config, and src to apply predefined rules for suggesting commit types such as feat or fix.

How does commit scope detection work for changes in a specific directory?▼

Commit scope detection works by identifying the primary directory of changed files in your git repository. It analyzes file paths from your staged changes to determine the relevant scope, ensuring consistent and informative commit messages for specific modules.

Can I automatically suggest a fix commit type by analyzing modified test and src files?▼

Yes, you can automatically suggest a fix commit type by analyzing modified test and src files. The mechanism categorizes modified files by type and applies predefined rules to the diff content, determining whether a fix, feat, or chore type is appropriate.

What is the best way to categorize git changes for conventional commits?▼

The best way to categorize git changes for conventional commits is to group modified files into predefined types like docs, test, config, and src. This categorization applies predefined rules to analyze change statistics and suggest the optimal commit type.

Does this conventional commit detection work without external dependencies?▼

Yes, conventional commit detection works without external dependencies. It uses internal references to analyze git changes and file patterns, requiring only your staged git diff to suggest the commit type and scope.

Why does my commit type suggestion default to chore for configuration file changes?▼

Your commit type suggestion defaults to chore for configuration file changes because the detection mechanism categorizes config files separately from src or docs. It applies predefined rules to these file patterns to ensure the commit type matches the maintenance nature of the changes.