commit-workflow
This skill automates Git commit creation by analyzing staged changes and generating structured commit messages. It enforces conventional commit format, checks README updates, and provides clear examples. The workflow focuses only on staged files to prevent accidental commits of unrelated changes.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install fcakyon-claude-codex-settings-commit-workflow
Repository
Skill path: plugins/github-dev/skills/commit-workflow
This skill automates Git commit creation by analyzing staged changes and generating structured commit messages. It enforces conventional commit format, checks README updates, and provides clear examples. The workflow focuses only on staged files to prevent accidental commits of unrelated changes.
Open repositoryBest for
Primary workflow: Ship Full Stack.
Technical facets: Full Stack.
Target audience: Developers working with Git who want consistent commit messages and documentation updates, particularly in team environments where commit standards matter..
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: fcakyon.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install commit-workflow into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/fcakyon/claude-codex-settings before adding commit-workflow to shared team environments
- Use commit-workflow for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
---
name: commit-workflow
description: This skill should be used when user asks to "commit these changes", "write commit message", "stage and commit", "create a commit", "commit staged files", or runs /commit-staged or /commit-creator commands.
---
# Commit Workflow
Complete workflow for creating commits following project standards.
## Process
1. **Use commit-creator agent**
- Run `/commit-staged [context]` for automated commit handling
- Or follow manual steps below
2. **Analyze staged files only**
- Check all staged files: `git diff --cached --name-only`
- Read diffs: `git diff --cached`
- Completely ignore unstaged changes
3. **Commit message format**
- First line: `{task-type}: brief description of the big picture change`
- Task types: `feat`, `fix`, `refactor`, `docs`, `style`, `test`, `build`
- Focus on 'why' and 'what', not implementation details
- For complex changes, add bullet points after blank line
4. **Message examples**
- `feat: implement user authentication system`
- `fix: resolve memory leak in data processing pipeline`
- `refactor: restructure API handlers to align with project architecture`
5. **Documentation update**
- Check README.md for:
- New features that should be documented
- Outdated descriptions no longer matching implementation
- Missing setup instructions for new dependencies
- Update as needed based on staged changes
6. **Execution**
- Commit uses HEREDOC syntax for proper formatting
- Verify commit message has correct format
- Don't add test plans to commit messages
## Best Practices
- Analyze staged files before writing message
- Keep first line concise (50 chars recommended)
- Use active voice in message
- Reference related code if helpful
- One logical change per commit
- Ensure README reflects implementation