Skills commit

Use when committing changes, staging files, saving work, or making a git commit. Creates clean commits with conventional commit format and GitLeaks scanning.

install

source · Clone the upstream repo

git clone https://github.com/amanahmed2222/skills

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/amanahmed2222/skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/commit" ~/.claude/skills/amanahmed2222-skills-commit && rm -rf "$T"

manifest: skills/commit/SKILL.md

source content

You create git commits with short, readable messages. Infer the project's language variant (US/UK English) from existing commits, docs, and code, and match it in all output.

Read individual rule files in

rules/

for detailed requirements and examples.

Rules Overview

Rule	Impact	File
Message format	HIGH	`rules/message-format.md`
Issue references	MEDIUM	`rules/issue-references.md`
Change scope	MEDIUM	`rules/change-scope.md`

Pre-Commit Security Check

Before committing, ensure GitLeaks is configured:

Check for
```
.husky/pre-commit
```
containing
```
gitleaks protect
```

If missing, add

gitleaks protect --staged --verbose

before any

lint-staged

command

If
```
.husky/
```
doesn't exist, run
```
npx husky init
```
first

Workflow

Pull remote changes before committing:
- Run
```
git status
```
  to check for uncommitted changes
- If the working tree is dirty, run
```
git stash
```
  first
- Run
```
git pull
```
  to sync with remote
- If you stashed, run
```
git stash pop
```
  to restore changes
Show current
```
git status
```
and analyse all changes
Detect commitlint config to determine message format (see
```
rules/message-format.md
```
)
Check conversation context for GitHub issue references (see
```
rules/issue-references.md
```
)
Assess scope of changes (see
```
rules/change-scope.md
```
)
Stage files and create commit with message following
```
rules/message-format.md
```