Git workflow automation patterns: branch naming, commit messages, PR descriptions, issue creation. Provides templates and conventions for consistent Git operations. Triggers: git, branch, commit, pull request, PR, issue, conventional commits, branch naming.
Automates Git workflows with templates for branches, commits, PRs, and issues.
/plugin marketplace add thkt/claude-config/plugin install complete-workflow-system@thkt-development-workflowsThis skill is limited to using the following tools:
references/branch-naming.mdreferences/commit-messages.mdreferences/issue-templates.mdreferences/pr-descriptions.mdGit workflow automation patterns using Conventional Commits and consistent naming.
Centralize Git workflow patterns that were embedded in individual commands. Commands become thin orchestrators that reference this skill for Git operations.
| Workflow | Reference | Command |
|---|---|---|
| Branch Naming | @./references/branch-naming.md | /branch |
| Commit Messages | @./references/commit-messages.md | /commit |
| PR Descriptions | @./references/pr-descriptions.md | /pr |
| Issue Creation | @./references/issue-templates.md | /issue |
<type>/<ticket>-<description>
Examples:
feat/AUTH-123-oauth-login
fix/BUG-456-null-pointer
refactor/TECH-789-cleanup-utils
<type>(<scope>): <description>
[optional body]
[optional footer]
| Type | Purpose |
|---|---|
feat | New feature |
fix | Bug fix |
docs | Documentation |
refactor | Code restructuring |
test | Test changes |
chore | Build/tooling |
## Summary
- [1-3 bullet points]
## Changes
- [Key changes]
## Test Plan
- [ ] Unit tests added
- [ ] Manual testing done
## Description
[Clear description]
## Steps to Reproduce (for bugs)
1. [Step 1]
2. [Step 2]
## Expected vs Actual
- Expected: [behavior]
- Actual: [behavior]
git push --force (use --force-with-lease)git reset --hard without confirmationgit status before commitOne logical change per commit:
# Bad
git commit -m "fix bug and add feature"
# Good
git commit -m "fix(auth): resolve token refresh"
git commit -m "feat(user): add profile page"
utilizing-cli-tools - CLI tool usage patterns/branch - Branch name suggestions/commit - Commit message generation/pr - PR description generation/issue - Issue creationThis 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.