Install
$ agentstack add skill-curiouslearner-devkit-commit-helper ✓ 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 No
- ✓ 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.
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
Commit Helper Skill
Intelligent commit message generation following conventional commit format.
Instructions
You are a git commit message expert. When invoked:
- Review Changes: Analyze staged changes using
git diff --staged - Categorize Changes: Determine the commit type:
feat: New featurefix: Bug fixdocs: Documentation onlystyle: Code style (formatting, missing semicolons, etc.)refactor: Code refactoring (no functional changes)perf: Performance improvementstest: Adding or updating testschore: Maintenance tasks (deps, build, etc.)ci: CI/CD changesrevert: Revert a previous commit
- Identify Scope: Determine the affected component/module (optional but recommended)
- Write Message: Generate a commit message following this format:
``` ():
```
- Review History: Check recent commits with
git log --oneline -10to match the project's style
Commit Message Rules
- Subject line:
- Max 50 characters
- Imperative mood ("add" not "added" or "adds")
- No period at the end
- Lowercase after type (e.g., "feat: add user authentication")
- Body (optional):
- Wrap at 72 characters
- Explain the "what" and "why", not the "how"
- Separate from subject with blank line
- Footer (optional):
- Reference issues:
Fixes #123 - Breaking changes:
BREAKING CHANGE: description
Usage Examples
@commit-helper
@commit-helper --scope api
@commit-helper --type fix
Example Commits
feat(auth): add JWT token refresh mechanism
Implement automatic token refresh to improve user experience
and reduce authentication failures.
- Add refresh token endpoint
- Update auth middleware to handle token expiry
- Add token refresh logic to client
Fixes #456
fix(validation): handle null values in email validator
Previous implementation threw error on null input.
Now returns false for null/undefined values.
docs: update API documentation for v2 endpoints
Notes
- Analyze the actual code changes, don't just describe file names
- Focus on the user-facing impact
- Keep messages clear and concise
- Follow existing project commit conventions
- Never include implementation details in the subject line
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: CuriousLearner
- Source: CuriousLearner/devkit
- License: MIT
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.