Agent skill
git-workflow
Follow git conventions for commits, branches, and PRs. Auto-activated during git operations.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/git-workflow-junior-frontend-dev-hi-u-ng
SKILL.md
Git Workflow Skill
Purpose
Ensure consistent git practices across all phases.
Commit Message Convention
Reference: conventions/commit-messages.md
Format
<type>(<scope>): <subject>
[optional body]
[optional footer]
Types
| Type | Use For |
|---|---|
| feat | New feature |
| fix | Bug fix |
| refactor | Code restructuring |
| docs | Documentation |
| test | Test changes |
| chore | Maintenance |
| perf | Performance improvement |
| style | Formatting, no code change |
| ci | CI/CD changes |
Examples
feat(auth): implement JWT token refresh
- Add refresh token endpoint
- Update token validation logic
- Add integration tests
Closes #123
Branch Naming
Reference: conventions/branch-naming.md
Format: <type>/<ticket>-<description>
Examples:
feat/AUTH-123-jwt-refreshfix/BUG-456-login-errorrefactor/TECH-789-user-service
PR Template
Reference: conventions/pr-template.md
Workflow Best Practices
Commit Frequency
- Commit after each logical unit of work
- Each commit should be independently buildable
- Don't commit broken code
Branch Strategy
- Create feature branch from main/develop
- Keep branches short-lived
- Rebase before merge when appropriate
PR Guidelines
- Keep PRs focused and reviewable
- Include context in description
- Link to related issues
- Request appropriate reviewers
Quality Checklist
Before committing:
- Code compiles/builds
- Tests pass
- Lint passes
- Commit message follows convention
- No sensitive data included
Before creating PR:
- Branch is up to date
- All commits are meaningful
- PR description is complete
- Tests are included
- Documentation updated
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?