Skip to content
Back to skills

Commit Changes

ASecurity

Create clear, informative, and well-structured Git commit messages following best practices and conventional commit standards.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 27, 2026
code-qualitygogitapidocumentation

Works with

  • cli
  • api

Security analysis

A100/100

Scanned September 27, 2026

npx -y skills add David-Li0406/meta-skill-evloving --skill commit-changes --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Commit Changes?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Commit Changes
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/david-li0406-commit-changes/badge)](https://www.skillsdirectory.com/skills/david-li0406-commit-changes)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: commit-changes
description: |
  Create clear, informative, and well-structured Git commit messages following best practices and conventional commit standards.
---
# Commit Changes

## Instructions

1. **Analyze Changes**: Run `git diff --staged`, `git diff`, and `git status`
2. **Stage All**: Use `git add -A` if needed
3. **Understand Context**: What changed, why, type, scope, patterns
4. **Check Branch**: If on main/master, create descriptive branch first
5. **Generate Message**: Subject ≤72 chars, imperative, conventional type
6. **Execute**: `git commit -m "<message>"`

## Commit Message Format

```
<type>(<scope>): <subject>

<body>
```

### Types

| Type | Use Case |
|------|----------|
| `feat` | New feature |
| `fix` | Bug fix |
| `docs` | Documentation only |
| `style` | Formatting, no code change |
| `refactor` | Code restructuring |
| `test` | Adding/fixing tests |
| `chore` | Build, config, dependencies |

### Rules

- Imperative mood ("Add feature" not "Added feature")
- No trailing period
- Subject ≤72 characters
- Body explains **what/why**, not how
- No co-author credits or "Generated with..." tags

## Quality Standards

- Meaningful to someone reading git log months later
- Avoid generic: "fix bug", "update code"
- Group related changes conceptually
- Flag if changes too diverse for single message

## Edge Cases

| Situation | Action |
|-----------|--------|
| No changes | Inform user nothing to commit |
| Incomplete changes | Flag observation to user |
| On main/master | Create feature branch first |
| Too diverse | Note to user, suggest splitting |

## Examples

### Example 1: Feature Commit

```
feat(auth): add JWT token refresh mechanism

- Implement automatic token refresh before expiration
- Add refresh token storage in secure cookie
- Include retry logic for failed refresh attempts
```

### Example 2: Bug Fix Commit

```
fix(api): prevent null pointer on empty response

Handle case where API returns empty body instead of
throwing unhandled exception in response parser.
```

### Example 3: Refactor Commit

```
refactor(streamer): extract common mock to shared helper

- Move mockGRPCStreamClient to mock_query.go
- Consolidate 4 duplicate mock implementations
- Reduce test file coupling
```

### Example 4: Multi-scope Commit

```
test(streamer): consolidate redundant tests

- Remove TestRemoteStream_Success (duplicate of Recv_EventDelivery)
- Merge Close_Idempotent into TestRemoteStream_Close
- Delete tests with no real assertions
```

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…