Skip to content
Back to skills

Commit 65

ASecurity

Create well-formatted commits following conventional commit standards

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 27, 2026
toolsgobashgitapiperformancedocumentation

Works with

  • cli
  • api

Security analysis

A100/100

Scanned September 27, 2026

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

Installs into .claude/skills of the current project.

Are you the author of Commit 65?

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

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

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
description: Create well-formatted commits following conventional commit standards
triggers:
  - /commit
  - commit changes
  - commit this
allowed-tools:
  - Read
  - Glob
  - Grep
  - Bash(git status*)
  - Bash(git diff*)
  - Bash(git add*)
  - Bash(git commit*)
  - Bash(git log*)
---

# Commit Skill

Create clean, well-documented commits following conventional commit standards.

## Process

### 1. Review Current Changes
```bash
git status
git diff
git diff --staged
```

Before committing:
- Understand the scope of changes
- Identify if changes should be split into multiple commits
- Ensure no unintended files are staged

### 2. Stage Changes
Stage related changes together. Split unrelated changes into separate commits.

```bash
# Stage specific files
git add src/feature.ts src/feature.test.ts

# Stage all changes in a directory
git add src/components/
```

### 3. Write Commit Message

Follow **Conventional Commits** format:

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

<body>

<footer>
```

#### Commit Types

| Type | Use For |
|------|---------|
| `feat` | New feature |
| `fix` | Bug fix |
| `docs` | Documentation changes |
| `style` | Formatting (no code change) |
| `refactor` | Code restructuring |
| `perf` | Performance improvement |
| `test` | Adding/fixing tests |
| `chore` | Maintenance tasks |

#### Examples

**Feature:**
```
feat(auth): add password reset flow

- Add forgot password form
- Implement email service integration
- Add token validation endpoint

Closes #123
```

**Bug Fix:**
```
fix(cart): prevent duplicate items on rapid clicks

Added debounce to add-to-cart button to prevent
race condition causing duplicate entries.

Fixes #456
```

**Refactor:**
```
refactor(utils): consolidate date formatting functions

Merged 4 duplicate implementations into shared utility.
No behavior changes.
```

### 4. Commit

```bash
git commit -m "type(scope): subject"
```

For multiline messages:
```bash
git commit -m "$(cat <<'EOF'
feat(payments): add Stripe integration

- Configure Stripe client
- Add checkout session creation
- Implement webhook handlers

Closes #789
EOF
)"
```

## Pre-Commit Checklist

- [ ] Code builds without errors
- [ ] Tests pass
- [ ] No debug code (console.log, debugger)
- [ ] No secrets or API keys
- [ ] Commit message follows conventions

## Atomic Commits

Each commit should be:
- **Self-contained**: One logical change
- **Complete**: Doesn't break the build
- **Reversible**: Can be reverted independently

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…