GIT Workflow

Should be used when the user asks to "create git commit", "manage branches", "follow...

Install

npx skills add Galaxy-Dawn/claude-scholar --skill git-workflow -g -a claude-code -y

Press to copy:C Claude CodeX CodexU CursorA Ask your agent

Repository: Galaxy-Dawn/claude-scholar6k
Category: Git and review
Updated: 16d ago
License: MIT
Context cost: Mediumabout 2,890 tokens
Runs scripts: Yes, review before use

What it does

This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team collaboration.

Git Workflow Standards

This document defines the project's Git usage standards, including commit message format, branch management strategy, workflows, merge strategies, and more. Following these standards improves collaboration efficiency, enables traceability, supports automation, and reduces conflicts.

Commit Message Standards

The project follows the Conventional Commits specification:

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

<body>

<footer>

Type Reference

Type	Description	Example
`feat`	New feature	`feat(user): add user export functionality`
`fix`	Bug fix	`fix(login): fix captcha not refreshing`
`docs`	Documentation update	`docs(api): update API documentation`
`refactor`	Refactoring	`refactor(utils): refactor utility functions`
`perf`	Performance improvement	`perf(list): optimize list performance`
`test`	Test related	`test(user): add unit tests`
`chore`	Other changes	`chore: update dependency versions`

Subject Rules

Start with a verb: add, fix, update, remove, optimize
No more than 50 characters
No period at the end

For more detailed conventions and examples, see references/commit-conventions.md.

Branch Management Strategy

Branch Types

Branch Type	Naming Convention	Description	Lifecycle
master	`master`	Main branch, releasable state	Permanent
develop	`develop`	Development branch, latest integrated code	Permanent
feature	`feature/feature-name`	Feature branch	Delete after completion
bugfix	`bugfix/issue-description`	Bug fix branch	Delete after fix
hotfix	`hotfix/issue-description`	Emergency fix branch	Delete after fix
release	`release/version-number`	Release branch	Delete after release

Branch Naming Examples

Read the whole SKILL.md on GitHub