commit-detection

majiayu000

Updated Today

1 views

Othergeneral

About

This skill analyzes git changes to determine the optimal conventional commit type (like fix, feat, docs). It examines modified files, change statistics, and keywords in diffs to categorize changes. Use it when analyzing commits or before committing to ensure proper commit message formatting.

Quick Install

Claude Code

Recommended

Plugin CommandRecommended

/plugin add https://github.com/majiayu000/claude-skill-registry

Git CloneAlternative

git clone https://github.com/majiayu000/claude-skill-registry.git ~/.claude/skills/commit-detection

Copy and paste this command in Claude Code to install this skill

Documentation

Commit Type Detection Skill

Expert knowledge for detecting the optimal conventional commit type.

Detection Algorithm

Step 1: Gather Data

# Get modified files
git diff --name-only
git diff --staged --name-only

# Get change statistics
git diff --stat
git diff --staged --stat

# Check for keywords in diff
git diff | grep -i "fix\|bug\|error" | head -5

Step 2: Categorize Files

Category	File Patterns
docs	`.md`, `.txt`, `.rst`, `README`, `CHANGELOG*`
test	`.test.`, `.spec.`, `__tests__/`, `test/`
config	`.json`, `.yml`, `.yaml`, `.toml`, `.*rc`
ci	`.github/*`, `.gitlab-ci.yml`, `Jenkinsfile`
build	`package.json`, `Makefile`, `webpack.`, `vite.`
style	Only whitespace, formatting changes
src	`.ts`, `.js`, `.py`, `.go`, `*.rs`, etc.

Step 3: Apply Rules

IF only docs files changed:
  → docs

IF only test files changed:
  → test

IF only config/build files changed:
  → chore

IF only CI files changed:
  → ci

IF diff contains "fix", "bug", "error", "issue", "resolve":
  → fix

IF new files added with business logic:
  → feat

IF files renamed/moved without logic change:
  → refactor

IF performance keywords ("optimize", "perf", "speed", "cache"):
  → perf

IF formatting only (whitespace, semicolons):
  → style

DEFAULT:
  → Use /commit-pro:commit for smart analysis

Step 4: Determine Scope

Extract scope from primary directory:

src/components/Button.tsx → ui or button
src/api/auth.ts → auth
lib/utils/date.ts → utils
server/routes/user.ts → user

Quick Reference

Type	When
`feat`	New functionality
`fix`	Bug correction
`docs`	Documentation only
`style`	Formatting only
`refactor`	Code restructure
`perf`	Performance
`test`	Tests only
`build`	Build/deps
`ci`	CI/CD config
`chore`	Maintenance

Examples

Example 1: Only README changed

Files: README.md
→ /commit-pro:docs

Example 2: New component + test

Files: src/Button.tsx, src/Button.test.tsx
→ /commit-pro:feat (primary is new feature)

Example 3: Fix in existing file

Files: src/api/auth.ts
Diff contains: "fix login bug"
→ /commit-pro:fix

GitHub Repository

majiayu000/claude-skill-registry

Path: skills/commit-detection

Related Skills

algorithmic-art

subagent-driven-development

Development

This skill executes implementation plans by dispatching a fresh subagent for each independent task, with code review between tasks. It enables fast iteration while maintaining quality gates through this review process. Use it when working on mostly independent tasks within the same session to ensure continuous progress with built-in quality checks.

View skill

executing-plans

Design

Use the executing-plans skill when you have a complete implementation plan to execute in controlled batches with review checkpoints. It loads and critically reviews the plan, then executes tasks in small batches (default 3 tasks) while reporting progress between each batch for architect review. This ensures systematic implementation with built-in quality control checkpoints.

View skill

cost-optimization

Other

This Claude Skill helps developers optimize cloud costs through resource rightsizing, tagging strategies, and spending analysis. It provides a framework for reducing cloud expenses and implementing cost governance across AWS, Azure, and GCP. Use it when you need to analyze infrastructure costs, right-size resources, or meet budget constraints.

View skill