# Create Clean Git Commits

Messy commit history makes reviews and rollbacks harder. This skill guides Claude, Codex, or Claude Code through commit strategy, messages, and verification.

## Install

```bash
npx skillstore add akabanakk/high-quality-commit
```

## Metadata

- Status: approved
- Slug: akabanakk-high-quality-commit
- Skillstore revision: r1
- Version status: missing
- Tree hash: 0eb221b7335fbb93f43e47833cf10a09a5232cdecb57b73b147d1e2ad1d14f29
- Author: AKABANAKK
- GitHub username: AKABANAKK
- License: MIT
- Repository: https://github.com/AKABANAKK/claude-code-marketplace/tree/main/akb7/skills/high-quality-commit
- Ref: 6eec4a59f63ff83440a84c18d1aef79743bc714e
- 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: 69
- Public page: https://skillstore.pages.dev/skills/akabanakk-high-quality-commit
- Manifest: https://skillstore.pages.dev/api/skills/akabanakk-high-quality-commit/manifest

## Capabilities

- Reviews branch status and commits against main.
- Chooses between new commit, amend, squash, and rebase workflows.
- Drafts conventional commit messages with subject, body, and footer guidance.
- Provides examples for review fixes, WIP cleanup, and staged feature work.
- Checks the latest commit and working tree after commit operations.

## Use Cases

- Prepare a feature branch: Choose between a new commit and an amend before opening a pull request.
- Clean up review changes: Fold review fixes into an existing commit when they belong to the same logical change.
- Organize complex work: Plan a small commit series for independent model, API, and UI changes.

## Prompt Templates

### Commit current work

```
Review my current Git changes and recommend a safe commit strategy. Ask before running commands that modify history.
```

### Amend review feedback

```
I applied review feedback on this branch. Check whether it should be amended into the previous commit or committed separately.
```

### Split related changes

```
Analyze my staged and unstaged changes. Propose logical commits with clear messages before making any commit.
```

### Prepare branch history

```
Review the branch history against main. Propose an interactive rebase plan, explain risks, and wait for approval before changes.
```

## Limitations

- It cannot know team Git policy unless the repository documents it.
- It may recommend history rewriting that needs user approval.
- It does not replace manual review for secrets or unrelated files.
- It does not resolve complex rebase conflicts by itself.

## Best Practices

- Review git status and diff before staging files.
- Ask for user approval before amend, rebase, force push, or reset.
- Write commit messages that explain why the change was needed.

## Anti Patterns

- Running git add -A without checking for secrets or unrelated files.
- Rewriting branch history after others have based work on it.
- Mixing unrelated features, fixes, and documentation in one commit.

## Security Audit

- Audited at: 2026-07-05T02:28:03.303\+00:00
- Summary: Most static findings are false positives from Markdown backticks, endpoint examples, and entropy heuristics. Confirmed risk remains because the skill asks agents to stage all files, amend commits, and rebase history. I found no prompt injection, network exfiltration, or obfuscated payload in the reviewed files.

## Stats

- Views: 170
- Downloads: 12
- Favorites: 0
- Popularity score: 0