git-commit

от github

Стандартизированные git-коммиты с использованием спецификации Conventional Commits, интеллектуальным анализом diff и генерацией сообщений. Автоматически определяет тип коммита (feat, fix, docs, refactor, perf, test, build, ci, chore, revert) и область действия на основе фактических изменений кода. Генерирует семантические сообщения коммитов в соответствии с общепринятым форматом с опциональными разделами тела и подвала. Интеллектуально группирует файлы для логической организации при необходимости с поддержкой шаблонной и интерактивной постановки. Обнаруживает критические изменения и...

npx skills add https://github.com/github/awesome-copilot --skill git-commit

Скачать ZIP GitHub

39.4k

Git Commit with Conventional Commits

Overview

Create standardized, semantic git commits using the Conventional Commits specification. Analyze the actual diff to determine appropriate type, scope, and message.

Conventional Commit Format

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Commit Types

Type	Purpose
`feat`	New feature
`fix`	Bug fix
`docs`	Documentation only
`style`	Formatting/style (no logic)
`refactor`	Code refactor (no feature/fix)
`perf`	Performance improvement
`test`	Add/update tests
`build`	Build system/dependencies
`ci`	CI/config changes
`chore`	Maintenance/misc
`revert`	Revert commit

Breaking Changes

# Exclamation mark after type/scope
feat!: remove deprecated endpoint

# BREAKING CHANGE footer
feat: allow config to extend other configs

BREAKING CHANGE: `extends` key behavior changed

Workflow

1. Analyze Diff

# If files are staged, use staged diff
git diff --staged

# If nothing staged, use working tree diff
git diff

# Also check status
git status --porcelain

2. Stage Files (if needed)

If nothing is staged or you want to group changes differently:

# Stage specific files
git add path/to/file1 path/to/file2

# Stage by pattern
git add *.test.*
git add src/components/*

# Interactive staging
git add -p

Never commit secrets (.env, credentials.json, private keys).

3. Generate Commit Message

Analyze the diff to determine:

Type: What kind of change is this?
Scope: What area/module is affected?
Description: One-line summary of what changed (present tense, imperative mood, <72 chars)

4. Execute Commit

# Single line
git commit -m "<type>[scope]: <description>"

# Multi-line with body/footer
git commit -m "$(cat <<'EOF'
<type>[scope]: <description>

<optional body>

<optional footer>
EOF
)"