Link — Every PR Traces to an Issue

No work should merge untracked. This enforces the convention — a PR links to a tracker issue via a closing keyword — and closes the gap when one's missing by creating the issue and wiring the reference.

North star: every PR body carries a valid Closes|Refs <ISSUE-KEY> for the project's actual tracker, and the issue exists — done with one command, not a manual hunt.

Step 0 — Detect the tracker (never assume)

Resolve which tracker this repo uses, in order:

• The repo's PR template or contributing doc, if it states a convention.
• Config or references in the repo pointing at a Linear team, a Jira project key, or GitHub Issues.
• If genuinely ambiguous, ask once rather than guessing — creating a ticket in the wrong system is worse than asking.

Key formats: Linear uses a team prefix (TEAM-123), Jira uses a project key (PROJ-123), GitHub Issues uses #123 in the same repo or owner/repo#123 cross-repo.