config-git_skill

Overview

This skill provides an interactive git configuration setup that ensures user identity is set and generates a project-specific .claude/git.local.md file. It analyzes the repository, proposes concise conventional commit scopes, and writes a complete configuration file using a required template structure. The process is interactive only when necessary and verifies the created file.

How this skill works

The skill inspects the current git config and prompts for missing user.name or user.email, applying the values globally or locally per user choice. It scans the project filesystem and recent commit messages to infer languages, frameworks, and commit scope candidates. Scopes are normalized to strict single-word or abbreviated forms per naming rules, then merged into the example template and written to .claude/git.local.md. The created file is read back to confirm template integrity and placement.

When to use it

• Setting up a new development environment or machine to ensure git identity and project conventions are consistent
• Onboarding a repository to enforce conventional commit scopes and branch prefixes
• Standardizing commit message scopes across a team or monorepo
• When creating or updating project-specific git ignore entries based on detected languages
• Before introducing automated tools that rely on conventional commit metadata

Best practices

• Keep all commit scopes short: single words or letter abbreviations for multi-word components
• Use global git identity for personal machines; prefer local config for shared or CI contexts
• Review proposed scopes and only request clarification if ambiguous components are detected
• Preserve the template structure exactly; change only scopes, gitignore entries, or requested types/branches
• Run the verification step to ensure the .claude/git.local.md file matches the required example layout

Example use cases

• A developer clones a repo and runs the skill to set global git.name and git.email and create the project config
• A maintainer scans recent commit messages to derive relevant scopes and injects them into the project template
• A team standardizes branch prefixes and commit types across multiple repositories with consistent git.local.md files
• A project adds language-specific gitignore entries automatically after the skill detects frameworks and toolchains