Commit
Create a well-formatted conventional commit with proper message structure. Use when ready to commit changes.From its SKILL.md
npx -y skills add joris887/exosuit --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
- 4 stars4 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.3 KB, as published. Nobody here has run it
commit
Create a conventional commit for staged changes.
1. Review Changes
git status
git diff --staged
2. Determine Commit Type
Based on changes, select appropriate type:
- feat: New feature
- fix: Bug fix
- docs: Documentation only
- style: Formatting, no code change
- refactor: Code restructuring
- perf: Performance improvement
- test: Adding/updating tests
- build: Build system or dependency changes
- ci: CI configuration changes
- chore: Maintenance tasks
3. Generate Commit Message
Format:
<type>(<scope>): <short description>
<detailed body if needed>
Co-Authored-By: Claude <[email protected]>
Arguments provided: $ARGUMENTS
4. Execute Commit
git commit -m "$(cat <<'EOF'
<type>(<scope>): <description>
<body>
Co-Authored-By: Claude <[email protected]>
EOF
)"
5. Verify
git log -1 --oneline