config-git

Original：🇺🇸 English

Translated

Interactive git configuration setup for user identity and project conventions. Use when setting up Git for a new project, configuring commit scopes/types, or creating project-specific Git settings.

2installs

Sourcefradser/dotclaude

Added on2026-02-21

NPX Install

npx skill4agent add fradser/dotclaude config-git

SKILL.md Content

View Translation Comparison →

Interactive Git Configuration

Set up Git user identity and create

.claude/git.local.md

with conventional commit scopes, types, and branch naming conventions.

Current Git Config Context: !

git config --list --show-origin

Phase 1: Verify User Identity

Goal: Ensure git user.name and user.email are configured

Actions:

Review the "Current Git Config Context" above
Check if
```
user.name
```
and
```
user.email
```
are set
If EITHER is missing, use
```
AskUserQuestion
```
to request the missing information
Set the values globally (or locally if user specifies) using
```
git config
```

Phase 2: Analyze Project Context

Goal: Understand project structure and existing commit patterns

Actions:

Run
```
ls -F
```
or
```
find . -maxdepth 2 -not -path '*/.*'
```
to detect project languages/frameworks
Run
```
git log --format="%s" -n 50
```
(if git repo exists) to analyze existing commit message patterns and scopes

Phase 3: Determine Scopes

Goal: Generate appropriate commit scopes based on project structure

CRITICAL - Scope Naming Rules:

ALL scopes MUST be short (single words or abbreviations only)
Single words: use as-is (e.g.,
```
<word1>
```
,
```
<word2>
```
,
```
<word3>
```
)
Multi-word names: MUST convert to first letters (e.g.,
```
<multi-word-name>
```
→
```
<mwn>
```
,
```
<another-example>
```
→
```
<ae>
```
)
MUST NOT use full multi-word names like
```
<multi-word-name>
```
or
```
<another-example>
```
as scopes

Actions:

Propose a list of commit scopes based on analysis
Ensure all scopes follow the naming rules above
Request user input ONLY if genuine ambiguity exists

Phase 4: Generate Configuration File

Goal: Create

.claude/git.local.md

with complete structure from example template

CRITICAL - Template Requirements:

Use the ENTIRE example file structure as template
Preserve ALL sections from the example:
- YAML frontmatter with
```
scopes
```
  ,
```
types
```
  ,
```
branch_prefixes
```
  , AND
```
gitignore
```
- "# Project-Specific Git Settings" section
- "## Usage" section with all bullet points
- "## Additional Guidelines" section with all bullet points

Actions:

Read the example configuration file:

${CLAUDE_PLUGIN_ROOT}/examples/git.local.md

Replace the
```
scopes
```
list with determined short scopes
Update
```
gitignore
```
technologies based on detected project languages/frameworks
Keep
```
types
```
as standard conventional commit types (unless user requests changes)
Keep
```
branch_prefixes
```
as shown in example (unless user requests changes)
Create or overwrite
```
.claude/git.local.md
```
in the project root
Read the file back to verify it matches the example's complete structure

Output:

.claude/git.local.md

file with project-specific configuration

Phase 5: Confirmation

Goal: Inform user of successful configuration

Actions:

Confirm configuration is complete
Show the location of the created file

config-git

NPX Install

Tags

SKILL.md Content

Interactive Git Configuration

Phase 1: Verify User Identity

Phase 2: Analyze Project Context

Phase 3: Determine Scopes

Phase 4: Generate Configuration File

Phase 5: Confirmation