Claude Code Plugins

Community-maintained marketplace

Feedback

git-workflow

@wonjangcloud9/claude-tree
0
0

Git branching strategy and versioning workflow. Use when creating branches, PRs, or releasing versions.

Install Skill

1Download skill
2Enable skills in Claude

Open claude.ai/settings/capabilities and find the "Skills" section

3Upload to Claude

Click "Upload skill" and select the downloaded ZIP file

Note: Please verify skill by going through its instructions before using it.

SKILL.md

name git-workflow
description Git branching strategy and versioning workflow. Use when creating branches, PRs, or releasing versions.
allowed-tools Read, Bash, Grep, Glob

Git Workflow

Manages branching strategy and semantic versioning with Changesets.

Branch Strategy

main      ← stable releases (triggers npm publish)
  ↑
develop   ← integration branch (PRs go here)
  ↑
feature/* ← feature branches
fix/*     ← bugfix branches

Workflow Steps

1. Starting New Work

# Always start from develop
git checkout develop
git pull origin develop

# Create feature branch
git checkout -b feature/<name>
# or
git checkout -b fix/<name>

2. Recording Changes

After completing work, record the change for versioning:

pnpm changeset

Select change type:

  • patch: Bug fixes, minor changes (0.0.X)
  • minor: New features, backwards compatible (0.X.0)
  • major: Breaking changes (X.0.0)

Write a clear description of what changed.

3. Creating PR to develop

git add -A
git commit -m "<type>: <description>"
git push -u origin <branch-name>

Create PR to develop branch on GitHub.

4. Release to main

When develop is stable:

  1. Create PR from develop to main
  2. Merge triggers GitHub Action
  3. Action creates "Release PR" with:
    • Updated CHANGELOG.md
    • Bumped versions
  4. Merge Release PR to publish to npm

Commit Message Format

<type>(<scope>): <subject>

<body>

Types:

  • feat: New feature
  • fix: Bug fix
  • docs: Documentation
  • refactor: Code refactoring
  • test: Tests
  • chore: Maintenance

Commands Reference

# Check current branch
git branch --show-current

# View changeset status
pnpm changeset status

# Preview version changes
pnpm changeset version --dry-run

# Build and publish (CI does this)
pnpm release

Rules

  1. Never commit directly to main
  2. Always create changeset for user-facing changes
  3. Keep PRs focused and small
  4. Ensure tests pass before merging