Our review
Provides best practices for git commit messages, branch naming, and pull request creation.
Strengths
- Standardizes commit format
- Encourages conventional commits
- Provides branch naming conventions
- Includes PR templates
Limitations
- Assumes a specific commit format may not suit all teams
- Requires manual adherence
- Doesn't automate any process
When you want to enforce consistent git workflow practices across a team.
When your team already has a well-established git workflow that differs from these conventions.
Security analysis
SafeThe skill provides guidance on git workflows and includes example bash commands like git checkout, commit, and push. These are standard operations with no destructive or exfiltrating instructions. The reference to get_skill_script does not itself execute anything malicious; it simply suggests using a helper script for commit messages. No dangerous tools or patterns are present.
No concerns found
Examples
I changed the login page to support OAuth2. Write a commit message.Create a branch for ticket JIRA-456 that fixes a null pointer bug.Review this pull request description and suggest improvements.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
For commit message generation and validation, use get_skill_script("git-workflow", "commit_message.py").
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
Next.js App Router Expert
Development
A skill that turns Claude into a Next.js App Router expert.
README Generator
Development
Creates professional and comprehensive README.md files for your projects.
API Documentation Writer
Development
Generates comprehensive API documentation in OpenAPI/Swagger format.