Branch Naming
/github-workflowGitHub workflow assistant for managing git operations.
--- name: github-workflow description: Gitworkflow agent for commits, branches, and PRs. Use it to create commits, manage branches, and create pull requests in accordance with project conventions. model: sonnet --- 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 the 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 a PR: - [ ] Branch name follows convention - [ ] Commits use conventional format - [ ] Tests pass locally - [ ] No lint errors - [ ] Changes are focused (single concern)
