PROACTIVELY load this skill when creating PRs, resolving merge conflicts, or asked about version control best practices. Provides expert guidance for Git workflows, branching strategies, commit conventions, and collaboration patterns.
Provides expert Git workflow guidance for PRs, merge conflicts, and version control best practices. Triggers when creating pull requests, resolving conflicts, or discussing commit standards.
/plugin marketplace add Git-Fg/thecattoolkit/plugin install git-fg-thecattoolkit@Git-Fg/thecattoolkitThis skill inherits all available tools. When active, it can use any tool Claude has access to.
workflows/generate-commit.md<type>(<scope>): <description>
[optional body]
[optional footer(s)]
| Type | Description |
|---|---|
| feat | New feature |
| fix | Bug fix |
| docs | Documentation only |
| style | Formatting, no logic change |
| refactor | Code change that neither fixes bug nor adds feature |
| perf | Performance improvement |
| test | Adding/updating tests |
| chore | Build process, dependencies |
| ci | CI configuration |
Feature:
feat(auth): add OAuth2 login support
Implements Google and GitHub OAuth providers.
Closes #123
BREAKING CHANGE: Session tokens now expire after 24h
Bug Fix:
fix(api): handle null response from payment gateway
Previously caused 500 error when gateway returned null.
Now returns appropriate error message to user.
Documentation:
docs(api): update authentication endpoint documentation
Adds request/response examples for OAuth flow.
Format: <type>/<ticket-id>-<short-description>
Examples:
feature/AUTH-123-oauth-loginfix/BUG-456-null-pointerchore/TECH-789-upgrade-depsdocs/README-001-update-installation| Size | Lines Changed | Expected Review Time |
|---|---|---|
| XS | < 50 | < 15 minutes |
| S | 50-200 | 15-30 minutes |
| M | 200-500 | 30-60 minutes |
| L | 500+ | Should be split if possible |
Every PR must include:
PR Template:
## Summary
[Brief description of changes]
## Changes
- [Change 1]
- [Change 2]
## Testing
- [ ] Unit tests added/updated
- [ ] Manual testing performed
- [ ] E2E tests pass
## Checklist
- [ ] Code follows project conventions
- [ ] Documentation updated
- [ ] No security vulnerabilities introduced
main ──●────●────●────●────●── (always deployable)
\ /
feature └──●──●──┘
main ──●─────────────●────── (releases only)
\ /
release └────●────┘
/
develop ──●──●────●──●──●──
\ /
feature └──●┘
Before Submitting:
Reviewer Evaluation Criteria:
workflows/generate-commit.md - Analyze staged changes and generate conventional commitThis skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.