git-workflow

Git Workflow & Platform Collaboration

This Skill aims to guide developers in standardizing their use of Git and efficiently leveraging code hosting platforms such as GitHub and Gitee for collaboration.

Included skill modules

1. Commit Convention

• Standard: Follow Conventional Commits。
• Format: <type>(<scope>): <description>
  • feat: New feature
  • fix: Bug fix
  • docs: Documentation changes
  • style: Code formatting changes (changes that do not affect code execution)
  • refactor: Refactoring (i.e., code changes that neither add features nor fix bugs)
  • perf: Performance optimization
  • test: Add tests
  • chore: Changes to the build process or auxiliary tools
• Example: feat(auth): add google oauth2 login support

2. Branching Strategy

• Trunk Based Development (recommended):
  • main: A main branch that is always releasable.
  • Feature branches: short-lived feature branches that are deleted after merging.
• Git Flow (traditional):
  • master, develop, feature/*, release/*, hotfix/*.

3. Platform Specifics

GitHub

• Actions: Preferred for CI/CD.
• Pages: Static website hosting.
• PR: Pull Request workflow and Code Review.

Gitee

• Domestic acceleration: Suitable for domestic mirrors and private projects.
• Gitee Go: Built-in CI/CD pipelines.
• Pages: Gitee Pages service.

🤖 Agent and MCP enhancements

Recommended agent roles

• Git Workflow Specialist: See AGENTS.md。
  • Focuses on code review, commit message standardization, and release process management.

Recommended MCP tools

• Git MCP:
  • Automatically execute git add, git commit, git push。
  • Analyze git log to generate a Changelog.
• GitHub MCP:
  • Create issues, submit PRs, review code, manage releases.
• mcp-feedback-enhanced:
  • When generating a PR description or Commit Message, if there is insufficient context, use ask_followup_question to ask the user for the specific reason for the change or the related Issue.
  • When conducting a Code Review, use this tool to confirm the user's review focus.

---