← Back to list

git-workflow
by jgeldart
⭐ 0🍴 0📅 Jan 19, 2026
SKILL.md
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
-
Subject Line
- Use imperative mood ("add" not "added")
- Don't capitalize first letter
- No period at the end
- Limit to 50 characters
-
Body (optional)
- Explain what and why, not how
- Wrap at 72 characters
- Separate from subject with a blank line
-
Footer (optional)
- Reference issues:
Fixes #123 - Breaking changes:
BREAKING CHANGE: description
- Reference issues:
Commit Message Generation Workflow
- Run
git diff --stagedorgit statusto see changes - Analyze the changes to understand what was modified
- Generate and validate an appropriate commit message using
get_skill_script("git-workflow", "commit_message.py"). - Optionally run
git commit -m "message"if user confirms
Format
<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
feat(auth): add OAuth2 login support
Implemented OAuth2 authentication flow with Google and GitHub providers.
Added token refresh mechanism and session management.
Closes #123
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
<type>/<ticket-id>-<short-description>
Examples
feature/AUTH-123-oauth-loginfix/BUG-456-null-pointerchore/TECH-789-update-deps
Pull Request Guidelines
Title
Follow commit message format for the title.
Description Template
## 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
git checkout main
git pull origin main
git checkout -b feature/TICKET-123-description
Committing
git add -p # Interactive staging
git commit -m "type(scope): description"
Updating Branch
git fetch origin
git rebase origin/main
Creating PR
git push -u origin feature/TICKET-123-description
# Then create PR on GitHub/GitLab
Score
Total Score
45/100
Based on repository quality metrics
✓SKILL.md
SKILL.mdファイルが含まれている
+20
○LICENSE
ライセンスが設定されている
0/10
○説明文
100文字以上の説明がある
0/10
○人気
GitHub Stars 100以上
0/15
○最近の活動
3ヶ月以内に更新がある
0/10
○フォーク
10回以上フォークされている
0/5
✓Issue管理
オープンIssueが50未満
+5
○言語
プログラミング言語が設定されている
0/5
○タグ
1つ以上のタグが設定されている
0/5
Reviews
💬
Reviews coming soon