git-commit-composer
π―Skillfrom edanstarfire/claudecode_webui
Generates well-structured, semantic git commit messages by guiding developers through a standardized commit message composition process.
Installation
npx skills add https://github.com/edanstarfire/claudecode_webui --skill git-commit-composerSkill Details
Create well-formatted semantic commit messages following project conventions. Use when committing changes to ensure consistent, descriptive commit history.
Overview
# Git Commit Composer
Instructions
When to Invoke This Skill
- Ready to commit changes after implementation
- Need to create descriptive commit message
- Following semantic commit conventions
- Linking commits to issues or PRs
Commit Message Format
#### Structure
```
```
#### Components
Type (required):
feat- New featurefix- Bug fixchore- Maintenance, dependencies, toolingdocs- Documentation changesrefactor- Code restructuring without behavior changetest- Test additions or modificationsperf- Performance improvementsstyle- Code style/formatting (no logic change)
Brief Description (required):
- Imperative mood: "add", not "added" or "adds"
- Lowercase start
- No period at end
- Maximum 50 characters
- Describe what the commit does
Detailed Explanation (recommended):
- Explain WHAT changed and WHY
- Don't explain HOW (code shows that)
- Use bullet points for multiple changes
- Wrap at 72 characters per line
Footer (optional):
- Issue links:
Fixes #123,Resolves #456,Closes #789 - Breaking changes:
BREAKING CHANGE: describe the change - Co-authors:
Co-Authored-By: Name - Tool attribution:
π€ Generated with [Claude Code](https://claude.com/claude-code)
Standard Workflow
- Review Changes
```bash
git status
git diff
```
- Analyze Changes
- Determine commit type
- Identify main purpose
- Note secondary effects
- Find related issues
- Compose Message
Follow the format above
- Create Commit
```bash
git commit -m "$(cat <<'EOF'
EOF
)"
```
Best Practices
Good Brief Descriptions:
feat: add user authentication with JWTfix: resolve race condition in websocket handlerchore: update dependencies to latest versionsdocs: add API endpoint documentation
Bad Brief Descriptions:
feat: added some new features(too vague)fix: Fixed a bug(not descriptive)update(missing type)FEAT: Add Feature(wrong capitalization)
Good Detailed Explanations:
```
Add JWT-based authentication to protect API endpoints
- Implement token generation and validation
- Add middleware to verify tokens on protected routes
- Store refresh tokens in database
- Add token expiration and renewal logic
This ensures only authenticated users can access sensitive data.
```
Bad Detailed Explanations:
```
Made some changes to auth
```
Commit Message Templates
#### Feature Commit
```
feat: add dark mode toggle
Implement dark mode toggle in user settings with:
- Theme preference stored in localStorage
- CSS variable switching for colors
- Smooth transitions between themes
Fixes #42
π€ Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude
```
#### Bug Fix Commit
```
fix: resolve websocket race condition
Fix race condition where messages could be sent before connection
fully established:
- Add connection ready flag
- Queue messages during connection
- Flush queue once connected
Fixes #156
π€ Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude
```
#### Chore Commit
```
chore: update Python dependencies
Update uv.lock with latest package versions:
- fastapi 0.104.0 -> 0.109.0
- uvicorn 0.24.0 -> 0.27.0
- pydantic 2.5.0 -> 2.6.0
All tests passing with updated versions.
π€ Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude
```
#### Refactor Commit
```
refactor: extract message processing into handlers
Split monolithic message processor into specialized handlers:
- SystemMessageHandler
- AssistantMessageHandler
- UserMessageHandler
- ResultMessageHandler
No behavior changes, improved maintainability.
π€ Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude
```
Multiple Commits vs Single Commit
Use Multiple Commits When:
- Changes are logically separate
- Each commit works independently
- Different types (feat + docs)
Use Single Commit When:
- Changes are tightly coupled
- Breaking them apart doesn't make sense
- Implementing single issue/feature
Amending Commits
When to Amend:
- Forgot to include a file
- Typo in commit message
- Small addition to last commit
- Commit not yet pushed
How to Amend:
```bash
git add
git commit --amend --no-edit
```
When NOT to Amend:
- Commit already pushed to remote
- Other developers have the commit
- Would rewrite shared history
Examples
Example 1: Feature implementation
```
Changes: Added user profile page with avatar upload
Action:
- Review changes: git diff
- Identify type: feat (new feature)
- Compose:
- Brief: "add user profile page with avatar upload"
- Detail: List components added, functionality
- Footer: Fixes #42
- Commit with formatted message
```
Example 2: Bug fix
```
Changes: Fixed null pointer error in login handler
Action:
- Identify type: fix (bug fix)
- Brief: "resolve null pointer in login handler"
- Detail: Explain the bug and how it was fixed
- Footer: Fixes #89
- Commit
```
Example 3: Multiple related changes
```
Changes: Updated deps + fixed compatibility issue
Decision: Single commit (changes are coupled)
Action:
- Type: chore (dependency update)
- Brief: "update dependencies and fix compatibility"
- Detail: List updates + explain compatibility fix
- Commit together
```
Example 4: Separate concerns
```
Changes: New feature + unrelated docs update
Decision: Two commits (logically separate)
Action:
- Stage feature files: git add src/
- Commit feature: feat message
- Stage docs: git add docs/
- Commit docs: docs message
```
More from this repository10
Synchronizes local main branch with remote, pulling latest changes and ensuring a clean, up-to-date base for new worktrees.
Retrieves recent issues related to login, presents most relevant issue ``` Reads and analyzes GitHub issues to provide comprehensive context and implementation details.
Manages Git branches by safely creating, switching, and cleaning up branches with intelligent handling of uncommitted changes.
Automates GitHub pull request workflows by tracking, reviewing, and managing PRs across repositories with intelligent filtering and status updates
Explores codebases systematically by identifying relevant files, tracing functionality, and understanding architectural patterns through targeted search techniques.
Generates comprehensive, step-by-step implementation plans with clear technical details, testing strategies, and risk assessment for complex software features.
process-manager skill from edanstarfire/claudecode_webui
Analyzes code changes by tracing direct and indirect dependencies, identifying potential impacts and risks before implementing modifications.
Validates git repository state by checking working directory status, branch conflicts, and repository health before critical git operations.
Authenticates and troubleshoots GitHub CLI access by verifying credentials, refreshing tokens, and resolving permission issues.