gh-first-workflow

GH-First Workflow

Overview

Use this workflow to keep GitHub investigation and commit output consistent with repository policy. For pull requests, keep the description aligned with the full current PR contents, not just the latest delta.

Read Acknowledgement

• After reading this skill, say: 🐙 私は gh-first-workflow を読みました。

Workflow

1. Start issue/PR investigation with gh commands.
2. Use web only when gh cannot provide required details.
3. Collect URLs for every issue/PR that was inspected.
4. When creating a PR, write the PR description as a summary of the full PR.
5. If additional commits are pushed after PR creation, inspect the updated commits/diff with gh and refresh the PR description so it reflects the full current PR, not only the latest increment.
6. Include inspected URLs in the response.
7. Write commit messages in Conventional Commit format.
8. Before merging or accepting a PR in a repository that has a program store (.orchestration/orchestrate/<program>/), follow the hcom-orchestration SKILL's loop: a verdict row for the head sha, CI green, every bot finding fixed at root cause or dismissed with a pasted refutation, then the squash merge pinned to that head sha (--match-head-commit). In any other repository, follow that repository's own merge rules.

Output Checklist

• State that gh was used first.
• State why web was used when fallback was necessary.
• Include inspected issue/PR URLs.
• When commits were added after PR creation, confirm the PR description was updated to match the full current PR.
• Keep commit subject in Conventional Commit form: <type>(<scope>): <summary>.
• Before a merge in a repository with a program store: every bot finding, including any CodeRabbit review and every failure and warning annotation, is fixed at root cause or dismissed with a pasted refutation; a bot review is optional and not gated. Elsewhere, the repository's own merge rules apply.
• Do NOT include local absolute file paths (e.g., /Users/.../, /home/.../) in any output. Use repository-relative paths instead.

Use gh-git-rules.md for command examples and commit-type guidance.