NGHC GitHub Workflow

Treat an NGHC change as one semantic story expressed consistently across the issue, branch, commits, and pull request. Prefer repository evidence over generic Git advice.

Establish the repository contract

1. Read repository instructions such as AGENTS.md, CONTRIBUTING.md, .github/, issue forms, PR templates, and release or commit policies.
2. Confirm that the repository actually adopts NGHC. Do not activate NGHC merely because the project uses Conventional Commits.
3. Identify the default/base branch and any repository-defined scopes. Never invent a scope just to fill the format.
4. Inspect the relevant issue, current branch, staged and unstaged changes, and recent commit/PR history before proposing metadata.
5. Let explicit user instructions and repository-local rules override this baseline when they intentionally differ from NGHC.

Read nghc-reference.md for the baseline convention and edge-cases.md when the change does not map cleanly to one type, scope, issue, or PR.

Build one semantic spine

Determine these facts once, then reuse them everywhere: