| name | commiter |
| description | Enforce wizteros commit and pull-request formatting. Use whenever preparing, writing, validating, or creating a git commit or pull request, including requests such as "commit this", "write a commit message", "open a PR", "prepare the PR", or "check this commit/PR title". Only applies to the wizteros repo. |
Enforce commit and pull-request formatting
Read the Workflow, Commits, and Pull Requests sections of the repository-root
CLAUDE.md before preparing any commit or pull request. Treat that file as the source
of truth if its rules change.
Authorization
Do not interpret this skill's activation as permission to commit, push, create a branch,
open a pull request, or merge. Perform only the git or GitHub action the user explicitly
authorized.
Commits
- Inspect the staged diff and repository status before writing the message.
- Keep each commit to one logical change; combine related files and separate unrelated
work.
- Start the subject with
WZ: followed by a short, specific title.
- Use a concise bullet-list body when context beyond the subject is useful. Omit the
body when it adds no value.
- Reject or rewrite a message whose subject does not match
WZ: <short title>.
- Before committing, verify that only the intended files are staged.
Example:
WZ: Add subscription renewal handling
- process successful renewal webhooks
- cover renewal state changes with tests
Pull requests
- Review the complete branch diff and commit history before drafting the pull request.
- Start the title with
WZ: followed by a short, specific title.
- Keep the body minimal and favor concise bullet points.
- Reject or rewrite a title that does not match
WZ: <short title>.
- Confirm the title and body comply with the current
CLAUDE.md rules before creating
or updating the pull request.
Example:
WZ: Add subscription renewal handling
- process successful renewal webhooks
- add regression coverage
