# Draft Clear Commit Messages

Staged changes can be difficult to summarize clearly. This skill reviews the staged diff and drafts an editable commit message that explains the change and its purpose.

## Install

```bash
npx skillstore add abejitsu/draft-commit
```

## Metadata

- Status: approved
- Slug: abejitsu-draft-commit
- Skillstore revision: r3
- Version status: missing
- Tree hash: 6d33d8bff11f012f1c87f34df3526c90752d20e4bd6aa3b837bf37a7426503b2
- Author: AbeJitsu
- GitHub username: AbeJitsu
- License: MIT
- Repository: https://github.com/AbeJitsu/Game-Settings-Panel/tree/main/.claude/skills/draft-commit
- Ref: 80999bf530a7874d7bedf8ce202001ecb4c4f5e0
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Quality score: 72
- Public page: https://skillstore.pages.dev/skills/abejitsu-draft-commit
- Manifest: https://skillstore.pages.dev/api/skills/abejitsu-draft-commit/manifest

## Capabilities

- Reviews staged changes with git diff --cached.
- Classifies changes such as features, fixes, documentation, and refactoring.
- Drafts descriptive or conventional-style commit messages.
- Includes optional context and file-change counts in the draft.
- Handles empty staged changes by suggesting the next step.
- Leaves staging and committing under user control.

## Use Cases

- Prepare a feature commit: Turn staged implementation, tests, and documentation into a message that explains the delivered feature.
- Standardize team history: Use conventional formatting to create consistent commit messages during team development.
- Document a maintenance change: Describe a small fix or refactor with enough context for future maintainers.

## Prompt Templates

### Draft my staged commit

```
Review my staged changes and draft a concise commit message.
```

### Explain the change purpose

```
Review my staged changes and draft a commit message that explains what changed and why.
```

### Use conventional commits

```
Review my staged changes and draft a conventional commit message with a clear type, scope, and rationale.
```

### Create a detailed release-ready message

```
Analyze my staged changes. Draft a detailed commit message with the change summary, impact, rationale, and file counts.
```

## Limitations

- It analyzes only changes that are already staged.
- It infers intent from diffs and may need clarification for ambiguous changes.
- It does not stage files, create commits, or modify the repository.
- Its configuration defaults must be edited manually per project.

## Best Practices

- Stage only related changes before requesting a draft.
- Review the drafted message and edit it to match the actual intent.
- Use a consistent format that matches your project conventions.

## Anti Patterns

- Do not use one draft to describe unrelated staged changes.
- Do not accept inferred rationale without checking it against the work.
- Do not expect the skill to stage files or create the commit.

## Security Audit

- Audited at: 2026-07-18T09:56:31.033\+00:00
- Summary: Manual review of SKILL.md found a prompt-only workflow for reviewing staged Git changes and drafting commit messages. The invalid-frontmatter scan limitation is not a security risk, and no prompt injection, data exfiltration, or repository-modifying behavior was found.

## Stats

- Views: 267
- Downloads: 11
- Favorites: 0
- Popularity score: 0