# Create Clear Conventional Git Commits

Inconsistent commits make project history difficult to review and maintain. This skill analyzes changes, stages logical groups, and creates standardized Conventional Commit messages.

## Install

```bash
npx skillstore add github/git-commit
```

## Metadata

- Status: approved
- Slug: github-git-commit
- Skillstore revision: r2
- Version status: missing
- Tree hash: 9e92688ccaf03d13bf9a59345cd33b5e3e87a1f256a7fc59542eebb431acea0c
- Author: github
- GitHub username: github
- License: MIT
- Repository: https://github.com/github/awesome-copilot/tree/main/skills/git-commit/
- Ref: c43861a65bb95efcae259cd161c9d6f4dc7eec6f
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 77
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/github-git-commit
- Manifest: https://skillstore.pages.dev/api/skills/github-git-commit/manifest

## Capabilities

- Inspects staged changes, working tree changes, and repository status.
- Infers a Conventional Commit type, scope, and concise description.
- Stages specific files, matching patterns, or selected patches.
- Creates single-line or multiline commits with bodies and footers.
- Formats breaking changes and issue references using established conventions.

## Use Cases

- Commit a focused feature: Review changes, stage related files, and create a clear feature commit.
- Standardize project history: Apply consistent types, scopes, descriptions, and issue references across contributions.
- Document a breaking change: Create a commit with a breaking-change marker, explanatory body, and footer.

## Prompt Templates

### Commit staged changes

```
Review my staged changes, propose a Conventional Commit message, and create the commit.
```

### Stage one logical change

```
Inspect my changes, stage only files for one logical update, propose a message, and commit them.
```

### Add type and issue

```
Create a fix commit for the auth scope, derive its description from the diff, and add Closes #123.
```

### Plan multiple commits

```
Divide my changes into logical groups, explain each group, then create separate Conventional Commits after confirmation.
```

## Limitations

- Requires Git, Bash access, and an existing repository.
- Does not push commits or change remote branches.
- Warns about secrets but does not provide a dedicated secret scanner.
- Cannot guarantee that repository hooks will accept the generated commit.

## Best Practices

- Review staged files and the proposed message before creating each commit.
- Keep each commit limited to one logical change.
- Use imperative descriptions under 72 characters and include relevant issue references.

## Anti Patterns

- Do not stage secret files, credentials, private keys, or unrelated changes.
- Do not bypass hooks or use destructive Git commands without explicit approval.
- Do not combine unrelated features, fixes, and maintenance work in one commit.

## Security Audit

- Audited at: 2026-07-23T18:00:52.849\+00:00
- Summary: All 28 static findings are false positives. Backticks are Markdown formatting, the here-document invokes local cat with a quoted delimiter, and sensitive filenames appear only in a warning. No prompt injection or harmful intent was found.

## Stats

- Views: 189
- Downloads: 71
- Favorites: 0
- Popularity score: 0