Commit
Agent skills for context management and guardrails — works with any coding agent harness.
npx -y skills add eeshansrivastava89/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
- 2 stars2 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
Create a git commit with conventional message format
SKILL.md
1.2 KB, as published. Nobody here has run it
Commit Workflow
Create a focused git commit with a conventional message.
Steps
- Run
git statusto see all changes - Run
git diff --stagedto see staged changes - Run
git diffto see unstaged changes - Analyze changes and draft commit message:
- Summarize what changed (not how)
- Use imperative mood ("Add feature" not "Added feature")
- Keep first line under 50 characters
- Add body if needed for context
- Show proposed commit message and ask for approval
- If approved:
- Stage relevant files (
git add) - Create commit with the message
- Show result
- Stage relevant files (
Commit Message Format
<type>: <short description>
<optional body explaining why, not what>
Types
feat: New featurefix: Bug fixrefactor: Code change that neither fixes nor addsdocs: Documentation onlytest: Adding or fixing testschore: Maintenance, dependencies, config
Rules
- Never commit without explicit user approval
- Never use
--forceor destructive operations - Don't commit secrets, credentials, or .env files
- Keep commits focused (one logical change)