Commit
Use when the user wants to commit changes, save work, or create a git commit message.
Install
$ agentstack add skill-huzaifa525-claude-code-optimizer-commit ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ● Environment & secrets Used
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-huzaifa525-claude-code-optimizer-commit) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Generate a commit message and commit staged changes.
Steps
- Check staged changes
`` git diff --cached --stat git diff --cached ``
- Check recent commit style
`` git log --oneline -10 ``
- Generate commit message following Conventional Commits:
| Prefix | When to Use | |--------|------------| | feat: | New feature | | fix: | Bug fix | | refactor: | Code restructure, no behavior change | | docs: | Documentation only | | test: | Adding or fixing tests | | chore: | Build, deps, config changes | | perf: | Performance improvement | | style: | Formatting, whitespace | | ci: | CI/CD changes |
- Format rules
- Subject line: max 72 characters, imperative mood ("Add" not "Added")
- Body: wrap at 80 characters, explain WHY not WHAT
- If multiple changes: use bullet points in body
- Commit
``` git commit -m "type: short description
- Detail 1
- Detail 2"
```
- Show result
`` git log --oneline -1 ``
Pre-Delivery Checklist
Before committing, verify:
- [ ]
git diff --cachedwas read (not just--stat) - [ ] Commit prefix matches the change type (feat/fix/refactor/etc.)
- [ ] Subject line is under 72 characters
- [ ] Subject uses imperative mood ("Add" not "Added")
- [ ] No sensitive files staged (.env, credentials, keys)
- [ ] No unrelated changes bundled in the same commit
- [ ] Body explains WHY if the change is non-obvious
If nothing is staged
Run git status and tell the user what files are available to stage.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: huzaifa525
- Source: huzaifa525/claude-code-optimizer
- License: MIT
- Homepage: https://www.npmjs.com/package/claude-code-optimizer
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.