From python
Generates conventional commit messages from git diffs by analyzing changes for type, scope, and subject. Validates messages against spec and executes git commits after confirmation.
npx claudepluginhub martinffx/atelier --plugin pythonThis skill uses the workspace's default tool permissions.
Generate and validate commit messages following the [Conventional Commits](https://www.conventionalcommits.org/) specification.
evals/evals.jsonworkspace/iteration-1/eval-0/with_skill/outputs/commit-message.txtworkspace/iteration-1/eval-0/with_skill/outputs/eval_metadata.jsonworkspace/iteration-1/eval-1/with_skill/outputs/eval_metadata.jsonworkspace/iteration-1/eval-1/with_skill/outputs/validation-result.txtworkspace/iteration-1/eval-2/with_skill/outputs/commit-message.txtworkspace/iteration-1/eval-2/with_skill/outputs/eval_metadata.jsonworkspace/iteration-1/report.htmlGenerates Git commit messages following Conventional Commits spec with types like feat/fix/refactor, scopes, subject/body/footer guidelines, and issue references. Activates on commit requests or git mentions.
Manages git commit workflows: checks status and diffs, stages changes selectively, generates and validates conventional commit messages, then executes commits.
Generates one-shot Conventional Commits messages for staged git changes. Imperative subject ≤50 chars with types like feat/fix/refactor, optional scope and why body. Use for standard git commits.
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>| 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.