Git workflow patterns for branching, commits, and pull requests following project conventions.
Provides git workflow patterns for branching, commits, and pull requests following project conventions. Claude uses this when creating branches, writing commit messages, or guiding git operations to ensure consistent workflow.
/plugin marketplace add az9713/claude-code-agentic-framework/plugin install az9713-codebase-singularity@az9713/claude-code-agentic-frameworkThis skill inherits all available tools. When active, it can use any tool Claude has access to.
This skill defines the git workflow patterns for the project, including branching strategies, commit conventions, and pull request guidelines.
| Branch | Purpose | Naming |
|---|---|---|
main | Production-ready code | Protected |
develop | Integration branch | Protected |
feature/* | New features | feature/description |
bugfix/* | Bug fixes | bugfix/issue-description |
hotfix/* | Production fixes | hotfix/critical-fix |
release/* | Release preparation | release/v1.2.0 |
type/short-description
Examples:
feature/user-authentication
bugfix/login-validation
hotfix/security-patch
release/v2.0.0
type(scope): subject
body (optional)
footer (optional)
| Type | Description |
|---|---|
feat | New feature |
fix | Bug fix |
docs | Documentation |
style | Formatting (no code change) |
refactor | Code refactoring |
test | Adding tests |
chore | Maintenance |
perf | Performance improvement |
ci | CI/CD changes |
# Feature
feat(auth): add JWT token validation
# Bug fix
fix(api): resolve null pointer in user lookup
# Documentation
docs(readme): update installation instructions
# Refactor
refactor(utils): simplify date formatting logic
Closes #123 or Fixes #456# 1. Start from develop
git checkout develop
git pull origin develop
# 2. Create feature branch
git checkout -b feature/my-feature
# 3. Make changes and commit
git add .
git commit -m "feat(scope): description"
# 4. Push branch
git push -u origin feature/my-feature
# 1. Ensure up to date with develop
git checkout develop
git pull origin develop
git checkout feature/my-feature
git rebase develop
# 2. Push final changes
git push origin feature/my-feature
# 3. Create PR via GitHub/CLI
gh pr create --base develop --title "feat: description" --body "..."
## Summary
[Brief description of changes]
## Changes Made
- [Change 1]
- [Change 2]
## Testing Done
- [Test 1]
- [Test 2]
## Checklist
- [ ] Tests pass
- [ ] Code reviewed
- [ ] Documentation updated
- [ ] No breaking changes (or documented)
## Related Issues
Closes #XXX
# Squash merge for features
git checkout develop
git merge --squash feature/my-feature
git commit -m "feat(scope): complete feature description"
git push origin develop
# Delete feature branch
git branch -d feature/my-feature
git push origin --delete feature/my-feature
git fetch origin
git checkout develop
git pull origin develop
git checkout feature/my-feature
git rebase develop
# During rebase
git status # See conflicted files
# Edit files to resolve conflicts
git add <resolved-files>
git rebase --continue
# Change message
git commit --amend -m "new message"
# Add forgotten files
git add forgotten-file.js
git commit --amend --no-edit
# Squash last 3 commits
git rebase -i HEAD~3
# In editor, change 'pick' to 'squash' for commits to combine
main Branchdevelop Branch# 1. Create release branch
git checkout develop
git checkout -b release/v1.2.0
# 2. Update version numbers, changelog
# ... make release preparations ...
# 3. Merge to main
git checkout main
git merge release/v1.2.0
git tag -a v1.2.0 -m "Release v1.2.0"
git push origin main --tags
# 4. Merge back to develop
git checkout develop
git merge release/v1.2.0
git push origin develop
# 5. Clean up
git branch -d release/v1.2.0
git reset --soft HEAD~1
git reset --hard HEAD~1
git reflog # Find commit hash
git checkout -b recovered-branch <hash>
git clean -fd # Remove untracked files and directories
This 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.