Conventional Git and GitFlow automation.

GitHub stars
14

Install

/plugin install git@dotfiles

Run it inside Claude Code after adding the marketplace with /plugin marketplace add dubuqingfeng/dotfiles.

Contents

Discovered from source

Commands 8

Requirements

  • Use atomic commits for logical units of work: Each commit should represent one complete, cohesive change.
  • Title: entirely lowercase, <50 chars, imperative mood (e.g., "add", "fix", "update"), conventional commits format (feat:, fix:, docs:, refactor:, test:, chore:)
  • Body: blank line after title, ≤72 chars per line, must start with uppercase letter, standard capitalization and punctuation. Describe what changed and why, not how.
  • Footer (optional): Must start with uppercase letter, standard capitalization. Reference issues/PRs (Closes #123, Fixes #456, Linked to PR #789). Use BREAKING CHANGE: prefix for breaking changes.

Examples

feat(auth): add google oauth login flow

- Introduce Google OAuth 2.0 for user sign-in
- Add backend callback endpoint `/auth/google/callback`
- Update login UI with Google button and loading state

Add a new authentication option improving cross-platform
sign-in.

Closes #42. Linked to #38 and PR #45
fix(api): handle null payload in session refresh

- Validate payload before accessing `user.id`
- Return proper 400 response instead of 500
- Add regression test for null input

Prevents session refresh crash when token expires.

Fixes #105
feat(auth): migrate to oauth 2.0

- Replace basic auth with OAuth 2.0 flow
- Update authentication middleware
- Add token refresh endpoint

BREAKING CHANGE: Authentication API now requires OAuth 2.0 tokens. Basic auth is no longer supported.

Closes #120. Linked to #115 and PR #122
  • Pushes must target the current branch on the remote; create a tracking branch when necessary using git push -u.

Your Task

IMPORTANT: You MUST use the Task tool to complete ALL tasks.

  1. Review the diff overview (e.g. git status, git diff --stat) to determine discrete logical units of work.
  2. For each unit, stage the relevant files and create a conventional commit.
  3. After committing all units, push the branch to the remote, configuring the upstream if it does not exist.

Requirements

  • Use atomic commits for logical units of work: Each commit should represent one complete, cohesive change.
  • Title: entirely lowercase, <50 chars, imperative mood (e.g., "add", "fix", "update"), conventional commits format (feat:, fix:, docs:, refactor:, test:, chore:)
  • Body: blank line after title, ≤72 chars per line, must start with uppercase letter, standard capitalization and punctuation. Describe what changed and why, not how.
  • Footer (optional): Must start with uppercase letter, standard capitalization. Reference issues/PRs (Closes #123, Fixes #456, Linked to PR #789). Use BREAKING CHANGE: prefix for breaking changes.

Examples

feat(auth): add google oauth login flow

- Introduce Google OAuth 2.0 for user sign-in
- Add backend callback endpoint `/auth/google/callback`
- Update login UI with Google button and loading state

Add a new authentication option improving cross-platform
sign-in.

Closes #42. Linked to #38 and PR #45
fix(api): handle null payload in session refresh

- Validate payload before accessing `user.id`
- Return proper 400 response instead of 500
- Add regression test for null input

Prevents session refresh crash when token expires.

Fixes #105
feat(auth): migrate to oauth 2.0

- Replace basic auth with OAuth 2.0 flow
- Update authentication middleware
- Add token refresh endpoint

BREAKING CHANGE: Authentication API now requires OAuth 2.0 tokens. Basic auth is no longer supported.

Closes #120. Linked to #115 and PR #122

Your Task

IMPORTANT: You MUST use the Task tool to complete ALL tasks.

  1. Analyze the pending changes to identify coherent logical units of work.
  2. For each logical unit, stage only the relevant files and craft a conventional commit message.
  3. Repeat the staging and committing process until every change is accounted for.

Context

  • Current branch: !git branch --show-current
  • Git status: !git status --porcelain
  • Recent commits: !git log --oneline -5
  • Test commands available: Detect available testing frameworks for this project

Requirements

  • Ensure all changes for feature $ARGUMENTS are committed before finishing.
  • Run the relevant test suite and confirm all checks pass.
  • Use atomic commits for logical units of work: Each commit should represent one complete, cohesive change.
  • Title: entirely lowercase, <50 chars, imperative mood (e.g., "add", "fix", "update"), conventional commits format (feat:, fix:, docs:, refactor:, test:, chore:)
  • Body: blank line after title, ≤72 chars per line, must start with uppercase letter, standard capitalization and punctuation. Describe what changed and why, not how.
  • Footer (optional): Must start with uppercase letter, standard capitalization. Reference issues/PRs (Closes #123, Fixes #456, Linked to PR #789). Use BREAKING CHANGE: prefix for breaking changes.

Examples

feat(auth): add google oauth login flow

- Introduce Google OAuth 2.0 for user sign-in
- Add backend callback endpoint `/auth/google/callback`
- Update login UI with Google button and loading state

Add a new authentication option improving cross-platform
sign-in.

Closes #42. Linked to #38 and PR #45
fix(api): handle null payload in session refresh

- Validate payload before accessing `user.id`
- Return proper 400 response instead of 500
- Add regression test for null input

Prevents session refresh crash when token expires.

Fixes #105
feat(auth): migrate to oauth 2.0

- Replace basic auth with OAuth 2.0 flow
- Update authentication middleware
- Add token refresh endpoint

BREAKING CHANGE: Authentication API now requires OAuth 2.0 tokens. Basic auth is no longer supported.

Closes #120. Linked to #115 and PR #122

Your Task

IMPORTANT: You MUST use the Task tool to complete ALL tasks.

  1. Confirm the branch name follows the feature/* convention and the working tree is clean.
  2. Execute the appropriate tests and resolve any failures before proceeding.
  3. Merge the feature branch into develop, delete the feature branch locally and remotely, handle merge conflicts if they arise, and push the updated develop branch.

Context

  • Current branch: !git branch --show-current
  • Git status: !git status --porcelain
  • Recent commits: !git log --oneline -5
  • Test commands available: Detect available testing frameworks for this project
  • Current version: Check version information in project configuration files

Requirements

  • Hotfix branches must follow the hotfix/* naming convention and remain narrowly scoped.
  • Update version metadata and changelog entries as part of the hotfix release.
  • Finish the Git Flow hotfix procedure (merge to main and develop, create release tag).
  • Use atomic commits for logical units of work: Each commit should represent one complete, cohesive change.
  • Title: entirely lowercase, <50 chars, imperative mood (e.g., "add", "fix", "update"), conventional commits format (feat:, fix:, docs:, refactor:, test:, chore:)
  • Body: blank line after title, ≤72 chars per line, must start with uppercase letter, standard capitalization and punctuation. Describe what changed and why, not how.
  • Footer (optional): Must start with uppercase letter, standard capitalization. Reference issues/PRs (Closes #123, Fixes #456, Linked to PR #789). Use BREAKING CHANGE: prefix for breaking changes.

Examples

feat(auth): add google oauth login flow

- Introduce Google OAuth 2.0 for user sign-in
- Add backend callback endpoint `/auth/google/callback`
- Update login UI with Google button and loading state

Add a new authentication option improving cross-platform
sign-in.

Closes #42. Linked to #38 and PR #45
fix(api): handle null payload in session refresh

- Validate payload before accessing `user.id`
- Return proper 400 response instead of 500
- Add regression test for null input

Prevents session refresh crash when token expires.

Fixes #105
feat(auth): migrate to oauth 2.0

- Replace basic auth with OAuth 2.0 flow
- Update authentication middleware
- Add token refresh endpoint

BREAKING CHANGE: Authentication API now requires OAuth 2.0 tokens. Basic auth is no longer supported.

Closes #120. Linked to #115 and PR #122

Your Task

IMPORTANT: You MUST use the Task tool to complete ALL tasks.

  1. Validate the branch name, ensure the working tree is clean, and confirm all hotfix commits are present.
  2. Execute the relevant tests, increment the patch version if required, and refresh changelog entries before finalizing.
  3. Complete the hotfix workflow—merge into main and develop, create and push tags, publish the GitHub release summary, and remove the hotfix branch locally and remotely.

Context

  • Current branch: !git branch --show-current
  • Existing release branches: !git branch --list 'release/*' | sed 's/^..//'
  • Git status: !git status --porcelain
  • Recent commits: !git log --oneline -5
  • Test commands available: Detect available testing frameworks for this project
  • Current version: Check version information in project configuration files

Requirements

  • Release branches must follow the release/<version> naming pattern and encode the target semantic version.
  • Update changelog and README documentation before completing the release.
  • Execute the full Git Flow release finish sequence (merge to main, tag, merge back to develop).
  • Use atomic commits for logical units of work: Each commit should represent one complete, cohesive change.
  • Title: entirely lowercase, <50 chars, imperative mood (e.g., "add", "fix", "update"), conventional commits format (feat:, fix:, docs:, refactor:, test:, chore:)
  • Body: blank line after title, ≤72 chars per line, must start with uppercase letter, standard capitalization and punctuation. Describe what changed and why, not how.
  • Footer (optional): Must start with uppercase letter, standard capitalization. Reference issues/PRs (Closes #123, Fixes #456, Linked to PR #789). Use BREAKING CHANGE: prefix for breaking changes.

Examples

feat(auth): add google oauth login flow

- Introduce Google OAuth 2.0 for user sign-in
- Add backend callback endpoint `/auth/google/callback`
- Update login UI with Google button and loading state

Add a new authentication option improving cross-platform
sign-in.

Closes #42. Linked to #38 and PR #45
fix(api): handle null payload in session refresh

- Validate payload before accessing `user.id`
- Return proper 400 response instead of 500
- Add regression test for null input

Prevents session refresh crash when token expires.

Fixes #105
feat(auth): migrate to oauth 2.0

- Replace basic auth with OAuth 2.0 flow
- Update authentication middleware
- Add token refresh endpoint

BREAKING CHANGE: Authentication API now requires OAuth 2.0 tokens. Basic auth is no longer supported.

Closes #120. Linked to #115 and PR #122

Your Task

IMPORTANT: You MUST use the Task tool to complete ALL tasks.

  1. Validate branch naming, ensure a clean working tree, and confirm all tests succeed.
  2. Merge the release branch into main with --no-ff, tag the merge commit using the encoded version, and merge main back into develop.
  3. Delete the release branch locally and remotely, push main, develop, and tags to origin, create the GitHub release from the new tag, and handle conflicts as needed.

Manual Recovery (if workflow fails)

  • git checkout main
  • git merge --no-ff release/x.x.x
  • git tag -a vx.x.x -m "Release x.x.x"
  • git checkout develop
  • git merge --no-ff main
  • git branch -d release/x.x.x && git push origin --delete release/x.x.x
  • git push origin main develop --tags
  • Create the GitHub release

Context

  • Current branch: !git branch --show-current
  • Existing feature branches: List all feature branches
  • Git status: !git status --porcelain

Requirements

  • Feature branches must use kebab-case names under the feature/ prefix.
  • Maintain a clean working tree before switching or publishing branches.
  • Publish new feature branches to origin for collaboration.
  • Use atomic commits for logical units of work: Each commit should represent one complete, cohesive change.
  • Title: entirely lowercase, <50 chars, imperative mood (e.g., "add", "fix", "update"), conventional commits format (feat:, fix:, docs:, refactor:, test:, chore:)
  • Body: blank line after title, ≤72 chars per line, must start with uppercase letter, standard capitalization and punctuation. Describe what changed and why, not how.
  • Footer (optional): Must start with uppercase letter, standard capitalization. Reference issues/PRs (Closes #123, Fixes #456, Linked to PR #789). Use BREAKING CHANGE: prefix for breaking changes.

Examples

feat(auth): add google oauth login flow

- Introduce Google OAuth 2.0 for user sign-in
- Add backend callback endpoint `/auth/google/callback`
- Update login UI with Google button and loading state

Add a new authentication option improving cross-platform
sign-in.

Closes #42. Linked to #38 and PR #45
fix(api): handle null payload in session refresh

- Validate payload before accessing `user.id`
- Return proper 400 response instead of 500
- Add regression test for null input

Prevents session refresh crash when token expires.

Fixes #105
feat(auth): migrate to oauth 2.0

- Replace basic auth with OAuth 2.0 flow
- Update authentication middleware
- Add token refresh endpoint

BREAKING CHANGE: Authentication API now requires OAuth 2.0 tokens. Basic auth is no longer supported.

Closes #120. Linked to #115 and PR #122

Your Task

IMPORTANT: You MUST use the Task tool to complete ALL tasks.

  1. Determine whether to create a new feature/$ARGUMENTS branch or resume an existing one.
  2. Ensure the working directory is clean, then switch to the selected branch (creating it if necessary).
  3. Push the feature branch to origin if it is newly created and confirm readiness for development.

Context

  • Current branch: !git branch --show-current
  • Existing hotfix branches: List all hotfix branches
  • Latest tag: !git tag --list --sort=-creatordate | head -1
  • Current version from main: Inspect version files on the main branch
  • Git status: !git status --porcelain

Requirements

  • Hotfix branches must use the hotfix/ prefix and represent patch-level fixes.
  • Increment the patch version automatically if none is provided and update version files.
  • Keep scope limited to critical production fixes before publishing.
  • Use atomic commits for logical units of work: Each commit should represent one complete, cohesive change.
  • Title: entirely lowercase, <50 chars, imperative mood (e.g., "add", "fix", "update"), conventional commits format (feat:, fix:, docs:, refactor:, test:, chore:)
  • Body: blank line after title, ≤72 chars per line, must start with uppercase letter, standard capitalization and punctuation. Describe what changed and why, not how.
  • Footer (optional): Must start with uppercase letter, standard capitalization. Reference issues/PRs (Closes #123, Fixes #456, Linked to PR #789). Use BREAKING CHANGE: prefix for breaking changes.

Examples

feat(auth): add google oauth login flow

- Introduce Google OAuth 2.0 for user sign-in
- Add backend callback endpoint `/auth/google/callback`
- Update login UI with Google button and loading state

Add a new authentication option improving cross-platform
sign-in.

Closes #42. Linked to #38 and PR #45
fix(api): handle null payload in session refresh

- Validate payload before accessing `user.id`
- Return proper 400 response instead of 500
- Add regression test for null input

Prevents session refresh crash when token expires.

Fixes #105
feat(auth): migrate to oauth 2.0

- Replace basic auth with OAuth 2.0 flow
- Update authentication middleware
- Add token refresh endpoint

BREAKING CHANGE: Authentication API now requires OAuth 2.0 tokens. Basic auth is no longer supported.

Closes #120. Linked to #115 and PR #122

Your Task

IMPORTANT: You MUST use the Task tool to complete ALL tasks.

  1. Decide whether to create a new hotfix/$ARGUMENTS branch from main or resume an existing hotfix branch.
  2. Update version metadata and changelog entries to reflect the new patch before development begins.
  3. Switch to the hotfix branch, ensure the workspace is ready, and push the branch for collaboration if newly created.

Context

  • Current branch: !git branch --show-current
  • Existing release branches: !git branch --list 'release/*' | sed 's/^..//'
  • Latest tag: !git tag --list --sort=-creatordate | head -1
  • Conventional commit scan: !git log $(git describe --tags --abbrev=0 2>/dev/null || echo)..develop --oneline --grep="feat\|fix\|BREAKING" 2>/dev/null || git log develop --oneline --grep="feat\|fix\|BREAKING"
  • Current version: Inspect project configuration files

Requirements

  • Release branches must use the release/ prefix and reflect the target semantic version.
  • Determine the semantic version bump using conventional commit history (breaking → major, feat → minor, fix → patch).
  • Update version metadata (package manifests, changelog) and publish the branch to origin.
  • Use atomic commits for logical units of work: Each commit should represent one complete, cohesive change.
  • Title: entirely lowercase, <50 chars, imperative mood (e.g., "add", "fix", "update"), conventional commits format (feat:, fix:, docs:, refactor:, test:, chore:)
  • Body: blank line after title, ≤72 chars per line, must start with uppercase letter, standard capitalization and punctuation. Describe what changed and why, not how.
  • Footer (optional): Must start with uppercase letter, standard capitalization. Reference issues/PRs (Closes #123, Fixes #456, Linked to PR #789). Use BREAKING CHANGE: prefix for breaking changes.

Examples

feat(auth): add google oauth login flow

- Introduce Google OAuth 2.0 for user sign-in
- Add backend callback endpoint `/auth/google/callback`
- Update login UI with Google button and loading state

Add a new authentication option improving cross-platform
sign-in.

Closes #42. Linked to #38 and PR #45
fix(api): handle null payload in session refresh

- Validate payload before accessing `user.id`
- Return proper 400 response instead of 500
- Add regression test for null input

Prevents session refresh crash when token expires.

Fixes #105
feat(auth): migrate to oauth 2.0

- Replace basic auth with OAuth 2.0 flow
- Update authentication middleware
- Add token refresh endpoint

BREAKING CHANGE: Authentication API now requires OAuth 2.0 tokens. Basic auth is no longer supported.

Closes #120. Linked to #115 and PR #122

Your Task

IMPORTANT: You MUST use the Task tool to complete ALL tasks.

  1. Decide whether to create a new release/<version> branch from develop or resume an existing release branch.
  2. Calculate the next semantic version based on commit history and update version files accordingly.
  3. Switch to the release branch, push it to origin if newly created, and prepare it for stabilization work.

Sponsors

Details

Marketplace
dubuqingfeng/dotfiles
Source
coding-agent/dist/claude/plugins/git
Category
Development

More from dubuqingfeng/dotfiles

All 4