SKILL.md

name: git-expert description: Expert Git workflow manager enforcing Conventional Commits. Handles staging, drafting semantic messages, and pushing changes with strict adherence to scope and formatting rules.

Git Expert Skill

This skill allows the agent to manage Git operations with professional rigor, ensuring the project history is semantic, clean, and automated-release ready.

1. Scope Detection Logic

Analyze the git status output to determine the primary scope. If multiple areas are touched, try to split commits or use root if it's a global change.

Directory path	Scope Tag
`gateway/**`	`gateway`
`api/specification/**`	`api-spec`
`backend/**`	`backend`
`frontend/**`	`frontend`
`website/**`	`docs`
`.github/**`	`ci`
`docker-compose.yml`, `Dockerfile`, `k8s/**`	`ops`
`pom.xml`, `package.json` (root)	`build`

2. Commit Message Template (The Law)

You MUST structure every commit message as follows:

<type>(<scope>): <subject>

<body>

<footer>

A. Header (Max 50 chars)

Type:
- feat: New feature (Minor version)
- fix: Bug fix (Patch version)
- docs: Documentation only
- style: Formatting, missing semi-colons, etc.
- refactor: Code change that neither fixes a bug nor adds a feature
- perf: Code change that improves performance
- test: Adding missing tests or correcting existing tests
- build: Changes that affect the build system or external dependencies
- ci: Changes to our CI configuration files and scripts
- chore: Other changes that don't modify src or test files
- revert: Reverts a previous commit
Scope: See Section 1.
Subject: Imperative mood ("Add" not "Added"). No period. Lowercase first letter.

B. Body (The "Why" and "How")

Required for: feat, fix, refactor, perf.
Format: Wrap at 72 characters.
Content:
- Explain the motivation for the change.
- Contrast with previous behavior.
- "The previous sorting algorithm caused O(n^2) latency... This change switches to MergeSort..."

C. Footer (References & Breaking)

Ticket Linking: Closes #123, Relates-to #456.
Breaking Changes:
- MUST start with BREAKING CHANGE:.
- Followed by a summary of the breaking change.
- Followed by a migration instruction.

3. The Commit Workflow (PROTOCOL:COMMIT)

When asked to "commit" or "save changes", you must follow this sequence:

Status Check: Run git status to see what is changed.
Diff Analysis: Run git diff (or git diff --staged) to understand the content of the change.
Drafting: Construct the conventional commit message based on the analysis.
- Self-Correction: If the body or footer information (like ticket numbers) is missing, ASK the user before finalizing the message.
Execution:
- git add <files>
- git commit -m "header" -m "body" -m "footer"
Verification: Run git log -1 to show the result.

Score

Total Score

40/100

Based on repository quality metrics

✓SKILL.md

SKILL.mdファイルが含まれている

+20

○LICENSE

ライセンスが設定されている

0/10

○説明文

100文字以上の説明がある

0/10

○人気

GitHub Stars 100以上

0/15

○最近の活動

3ヶ月以内に更新がある

0/10

○フォーク

10回以上フォークされている

0/5

✓Issue管理

オープンIssueが50未満

+5

✓言語

プログラミング言語が設定されている

+5

○タグ

1つ以上のタグが設定されている

0/5

Reviews

💬

Reviews coming soon