Git save
Stage and commit code changes with Conventional Commits format. Use when: code changes are complete and ready to commit, after review approval, user says 'save', 'commit', 'ship it'. Don't use when: tests are failing or work is still in progress.From its SKILL.md
npx -y skills add brolag/neural-claude-code --skill git-saveAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 11 stars11 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.
SKILL.md
1.2 KB, as published. Nobody here has run it
/git-save — Commit Workflow
git status— identify changed filesgit diff— understand what changedgit log --oneline -5— match existing commit style- Stage specific files by name (never
git add -A) - Skip files that look sensitive (.env, credentials, keys)
- Draft commit:
type(scope): description
Commit Types
| type | when |
|---|---|
feat | new feature |
fix | bug fix |
refactor | restructure, no behavior change |
docs | documentation only |
test | tests added/updated |
chore | build, deps, config |
Rules
- NEVER commit if tests are failing
- NEVER commit .env or credential files
- NEVER auto-push (commit only, user pushes manually)
- Ask before committing if scope is unclear