Help us improve
Share bugs, ideas, or general feedback.
From python
Generates and validates conventional commit messages following the conventionalcommits.org spec. Useful when committing code, reviewing commit format, or creating pull requests.
npx claudepluginhub martinffx/atelier --plugin codeHow this skill is triggered — by the user, by Claude, or both
Slash command
/python:code-commitThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generate and validate commit messages following the [Conventional Commits](https://www.conventionalcommits.org/) specification.
Executes git commits with conventional commit message analysis, intelligent staging, and message generation. Use when asked to commit changes or when /commit is invoked.
Manages git commit workflows: checks status and diffs, stages changes selectively, generates and validates conventional commit messages, then executes commits.
Manages Git commit workflow using Conventional Commits format with safety protocols. Creates, validates, executes commits; handles hooks, PRs, and safety checks before operations.
Share bugs, ideas, or general feedback.
Generate and validate commit messages following the Conventional Commits specification.
<type>(<scope>): <subject>
[optional body]
[optional footer(s)]
| Type | Description |
|---|---|
feat | New feature |
fix | Bug fix |
docs | Documentation only |
style | Code style (formatting, semicolons, etc.) |
refactor | Code change that neither fixes nor adds |
test | Adding or updating tests |
chore | Build, tooling, dependencies |
perf | Performance improvement |
ci | CI configuration changes |
build | Build system or dependencies |
revert | Reverting a previous commit |
auth, api, ui)! after type/scope: feat(auth)!: change APIBREAKING CHANGE:) or issue references (Closes #123)When user wants to commit changes:
git status to see changed filesgit diff --staged for staged changesgit commit -m "<message>"Example:
feat(auth): add JWT token refresh
Implements token refresh endpoint to extend sessions
without requiring re-authentication.
Closes #142
When user asks to validate or check a commit message:
<type>(<scope>): <subject>When user wants to open a PR or after finishing commits on a feature branch:
git branch --show-currentls .github/PULL_REQUEST_TEMPLATE.mdgit push -u origin <branch>gh pr create:
--fill if commits are clean (auto-populates title/body)--draft for work-in-progressSee references/pr-workflow.md for full workflow details.
| Input | Action |
|---|---|
| User says "commit" or "git commit" | Generate from git diff, then commit |
| User says "validate commit" | Check the commit message format |
| User pastes commit message | Validate the provided message |
When generating a commit:
git commit -m "<message>" after confirmationgit status shows nothing → warn user nothing to commitInput: "I fixed the login bug" Output:
fix(auth): resolve login timeout issue
Users were logged out after 5 minutes due to
incorrect token expiry calculation.
Input: "I added a new API endpoint for users" Output:
feat(api): add user profile endpoint
GET /users/:id returns user profile data including
name, email, and avatar URL.
Closes #89
Input: "I changed the auth API, this breaks old clients" Output:
feat(auth)!: change token validation endpoint
The /auth/verify endpoint now requires Bearer token
instead of query parameter.
BREAKING CHANGE: Clients must update to send
Authorization header with Bearer token.