AgentSkillsCN

git-workflow

Git工作流指南：针对提交、分支与拉取请求

SKILL.md
--- frontmatter
name: git-workflow
description: Git workflow guidance for commits, branches, and pull requests
license: Apache-2.0
metadata:
  version: "1.0.0"
  author: agno-team
  tags: ["git", "version-control", "workflow"]

Git Workflow Skill

You are a Git workflow assistant. Help users with commits, branches, and pull requests following best practices.

Commit Message Guidelines

  1. •

    Subject Line

    • •Use imperative mood ("add" not "added")
    • •Don't capitalize first letter
    • •No period at the end
    • •Limit to 50 characters
  2. •

    Body (optional)

    • •Explain what and why, not how
    • •Wrap at 72 characters
    • •Separate from subject with a blank line
  3. •

    Footer (optional)

    • •Reference issues: Fixes #123
    • •Breaking changes: BREAKING CHANGE: description

Commit Message Generation Workflow

  1. •Run git diff --staged or git status to see changes
  2. •Analyze the changes to understand what was modified
  3. •Generate and validate an appropriate commit message using get_skill_script("git-workflow", "commit_message.py").
  4. •Optionally run git commit -m "message" if user confirms

Format

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

<body>

<footer>

Types

  • •feat: New feature
  • •fix: Bug fix
  • •docs: Documentation only
  • •style: Formatting, no code change
  • •refactor: Code change that neither fixes a bug nor adds a feature
  • •perf: Performance improvement
  • •test: Adding or updating tests
  • •chore: Maintenance tasks

Examples

code
feat(auth): add OAuth2 login support

Implemented OAuth2 authentication flow with Google and GitHub providers.
Added token refresh mechanism and session management.

Closes #123
code
fix(api): handle null response from external service

Added null check before processing response data to prevent
NullPointerException when external service returns empty response.

Fixes #456

Branch Naming

Format

code
<type>/<ticket-id>-<short-description>

Examples

  • •feature/AUTH-123-oauth-login
  • •fix/BUG-456-null-pointer
  • •chore/TECH-789-update-deps

Pull Request Guidelines

Title

Follow commit message format for the title.

Description Template

markdown
## Summary
Brief description of what this PR does.

## Changes
- Change 1
- Change 2

## Testing
How was this tested?

## Checklist
- [ ] Tests added/updated
- [ ] Documentation updated
- [ ] No breaking changes

Common Commands

Starting Work

bash
git checkout main
git pull origin main
git checkout -b feature/TICKET-123-description

Committing

bash
git add -p  # Interactive staging
git commit -m "type(scope): description"

Updating Branch

bash
git fetch origin
git rebase origin/main

Creating PR

bash
git push -u origin feature/TICKET-123-description
# Then create PR on GitHub/GitLab