From em-software-factory
Create git commits for changes made during the session with thoughtful, atomic commit organization
How this skill is triggered — by the user, by Claude, or both
Slash command
/em-software-factory:commitThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create git commits for the changes made during this session with clear, descriptive messages and logical grouping.
Create git commits for the changes made during this session with clear, descriptive messages and logical grouping.
Use this skill when:
Review the session:
Check current state:
# See what changed
git status
# Review the actual changes
git diff
# Check for untracked files
git status --short
Consider commit structure:
Identify logical groups:
Draft commit messages:
Examples of good commit messages:
feat: Add real-time workflow status streaming
Implement SSE-based streaming for workflow run status updates.
Users can now see status changes without manual page refresh.
- Add useWorkflowRunLogs hook at page level
- Enable streaming for non-terminal run states
- Update status automatically across all tabs
docs: Add comprehensive SDLC skills documentation
Create detailed documentation for all Claude Code skills covering
the complete development lifecycle from research to PR creation.
- Add SKILLS_GUIDE.md for developers and non-developers
- Document all 12 skills with usage examples
- Include workflow diagrams and integration points
Conventional commit prefixes:
feat: - New featurefix: - Bug fixdocs: - Documentation onlystyle: - Formatting, missing semicolons, etc.refactor: - Code change that neither fixes a bug nor adds a featuretest: - Adding or updating testschore: - Maintenance, dependencies, build toolsShow your plan clearly:
I plan to create [N] commit(s):
Commit 1: [Title]
Files:
- path/to/file1.ts
- path/to/file2.py
- path/to/file3.md
Message:
[Full commit message]
Commit 2: [Title]
Files:
- path/to/other-file.ts
Message:
[Full commit message]
Shall I proceed?
Wait for user confirmation before executing.
Add files specifically:
# NEVER use git add -A or git add .
# Always add specific files
git add path/to/file1.ts path/to/file2.py path/to/file3.md
git commit -m "commit message"
For multi-line messages:
git commit -m "$(cat <<'EOF'
feat: Add feature title
Detailed explanation of what changed and why.
- Bullet point 1
- Bullet point 2
EOF
)"
Create commits in order:
Show the result:
git log --oneline -n [number-of-commits-created]
After committing:
# Verify commits were created
git log --oneline -n 5
# Verify no unintended files left staged
git status
# Show what was committed
git show --stat HEAD
DO NOT include:
Commits should be authored solely by the user.
Atomic commits:
Good groupings:
Bad groupings:
Good messages:
feat: Add user authentication with OAuth
Implement OAuth 2.0 authentication flow using Auth0.
Users can now log in with Google or GitHub accounts.
- Add OAuth callback handler
- Create user session management
- Add login/logout UI components
Bad messages:
changes
fixed stuff
update files
WIP
.
Always use specific files:
# ✅ Good
git add src/auth.ts src/components/Login.tsx
# ❌ Bad
git add .
git add -A
git add --all
Why?
Changes:
Approach:
Changes:
Approach:
Changes:
Approach:
Changes:
Approach:
docs: prefix# Commit work from current session
/commit
# System will analyze changes and propose commit plan
Typical workflow:
# 1. Do work
/implement-plan TICKET-123
# 2. Validate
/validate-plan
# 3. Review
/code-review
# 4. Commit work
/commit
# 5. Create PR
/create-pr
Or manual approach:
# After completing work in session
/commit
# Then push and create PR separately
git push
gh pr create
Does not:
/create-pr for that)Only:
You have full context:
User trusts your judgment:
Write as the user:
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub emergenceai/em-aisoftwarefactory