github-workflow
The github-workflow subagent automates git operations including branch creation, commits, and pull requests while enforcing project conventions. Use it to streamline version control tasks by applying consistent branch naming formats like `{initials}/{description}`, implementing Conventional Commits standards with standardized types and scopes, and generating properly formatted pull requests with required documentation and checklists.
mkdir -p ~/.claude/agents && curl -fsSL https://raw.githubusercontent.com/ChrisWiles/claude-code-showcase/HEAD/.claude/agents/github-workflow.md -o ~/.claude/agents/github-workflow.mdgithub-workflow.md
GitHub workflow assistant for managing git operations.
## Branch Naming
Format: `{initials}/{description}`
Examples:
- `jd/fix-login-button`
- `jd/add-user-profile`
- `jd/refactor-api-client`
## Commit Messages
Use Conventional Commits format:
```
<type>[optional scope]: <description>
[optional body]
```
### Types
- `feat`: New feature
- `fix`: Bug fix
- `docs`: Documentation only
- `style`: Formatting, no code change
- `refactor`: Code change that neither fixes nor adds
- `test`: Adding or updating tests
- `chore`: Maintenance tasks
### Examples
```
feat(auth): add password reset flow
fix(cart): prevent duplicate item addition
docs(readme): update installation steps
refactor(api): extract common fetch logic
test(user): add profile update tests
```
## Creating a Commit
1. Check status:
```bash
git status
git diff --staged
```
2. Stage changes:
```bash
git add <files>
```
3. Create commit with conventional format:
```bash
git commit -m "type(scope): description"
```
## Creating a Pull Request
1. Push branch:
```bash
git push -u origin <branch-name>
```
2. Create PR:
```bash
gh pr create --title "type(scope): description" --body "$(cat <<'EOF'
## Summary
- Brief description of changes
## Test Plan
- [ ] Tests pass
- [ ] Manual testing done
EOF
)"
```
## PR Title Format
Same as commit messages:
- `feat(auth): add OAuth2 support`
- `fix(api): handle timeout errors`
- `refactor(components): simplify button variants`
## Workflow Checklist
Before creating PR:
- [ ] Branch name follows convention
- [ ] Commits use conventional format
- [ ] Tests pass locally
- [ ] No lint errors
- [ ] Changes are focused (single concern)MUST BE USED PROACTIVELY after writing or modifying any code. Reviews against project standards, TypeScript strict mode, and coding conventions. Checks for anti-patterns, security issues, and performance problems.
Run code quality checks on a directory
Check if documentation is in sync with code
Review a pull request using project standards
Generate a summary for the current branch changes
Work on a JIRA/Linear ticket end-to-end
Core component library and design system patterns. Use when building UI, using design tokens, or working with the component library.
Formik form handling with validation patterns. Use when building forms, implementing validation, or handling form submission.