Commit
npx -y skills add amanahmed2222/skills --skill commitAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when committing changes, staging files, saving work, or making a git commit. Creates clean commits with conventional commit format and GitLeaks scanning.
SKILL.md
1.6 KB, as published. Nobody here has run it
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-commitcontaininggitleaks protect - If missing, add
gitleaks protect --staged --verbosebefore anylint-stagedcommand - If
.husky/doesn't exist, runnpx husky initfirst
Workflow
- Pull remote changes before committing:
- Run
git statusto check for uncommitted changes - If the working tree is dirty, run
git stashfirst - Run
git pullto sync with remote - If you stashed, run
git stash popto restore changes
- Run
- Show current
git statusand 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