gh-workflow

Use after receiving PR review feedback to systematically address comments, verify fixes, and re-request review

Use after making changes to commit with context-aware classification that flags out-of-context modifications before committing

Use when needing to create a new GitHub issue to gather requirements, check for duplicates, and create solution-agnostic issues

Use after PR is approved to merge with safe defaults, verification checks, and optional branch cleanup

Use when ready to create a PR to run full code review, convention checks, and get reviewer suggestions before PR creation

Use when ready to release to create a git tag, generate changelog from merged PRs, and create GitHub release

Use when assigned as reviewer or proactively reviewing PRs to perform multi-faceted code review with prioritized findings

Use when first setting up gh-workflow in a repository to analyze tech stack, detect conventions, and generate customized workflow configuration

Use to start work on a GitHub issue - assigns issue, creates branch, guides implementation with task tracking, and prepares for PR

Use to get a quick overview of assigned issues, open PRs, and pending review requests

Use proactively after code changes to review for quality, security, edge cases, and error handling. Use when performing self-review before PR creation or during PR review.

Use when validating Git conventions including commit messages, branch naming, PR format, and issue linkage. Use during PR review or before creating a PR.

Use when starting work on a GitHub issue to parse acceptance criteria and create a task breakdown. Use to establish implementation order and track progress.

Use to discover and run project-specific lint, test, and type-check commands. Use after code changes to verify quality gates pass before PR creation or merge.

Use before workflow execution to discover available agents, skills, and quality commands in the project environment. Use when adapting gh-workflow commands to project-specific tooling.

Use when needing to get the default branch, detect repository settings, fetch available labels, get repo info for API calls, or when any gh-workflow command needs dynamic repository configuration instead of hardcoded values.

Use when creating PRs to suggest reviewers, when creating issues to suggest assignees, or when re-requesting review after addressing comments. Ranks users by CODEOWNERS match, file expertise, recent activity, and workload balancing.

2 hooks across 1 event