Stats
Actions
Tags
From wf
Follow git commit conventions and branching strategies. Use when committing changes, creating branches, or writing commit messages.
How this skill is triggered — by the user, by Claude, or both
Slash command
/wf:git-workflowThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run all checks from the **conventions** skill's Code Review Checklist before every commit:
Run all checks from the conventions skill's Code Review Checklist before every commit:
uv run ruff check . && uv run ruff format . && uv run pyright && uv run pytest
All checks must pass. If any fail, fix before committing.
<type>: <subject>
<body>
<footer>
feat: add data validation module
Add input validation for user-submitted data with support for
common patterns (email, phone, URL). Includes custom validators
and comprehensive error messages.
Closes #123
feature/description - New featuresfix/description - Bug fixesrefactor/description - Code refactoringdocs/description - Documentation updatesIf GitHub MCP tools are available, use them for PR creation and issue management. Use git CLI for local operations (commit, branch, push). Fall back to gh CLI if no MCP is configured.
Before every commit, verify:
.env files stagednpx claudepluginhub mesca/claude-plugins --plugin wfOrchestrates multi-agent git workflow from code review and quality checks through testing, Conventional Commits, PR creation, and deployment readiness. Supports trunk-based and feature-branch strategies.
Provides Git workflow standards including branch naming, conventional commits, and PR guidelines. Use when creating branches, writing commits, or preparing PRs.
Guides conventional commit messages, explicit git staging workflows, logical change grouping, and best practices with issue linking. Useful for git add, commit, or staging tasks.