Pr Issue Search

• chore/update-linting-config --> no issue or ticket, continue to Step 2

Step 2: Extract from commit messages

git log main..HEAD --oneline

Look for #NUMBER references (GitHub issues) and [A-Z]+-\d+ patterns (Jira tickets) in commit subjects. Collect all unique references.

Step 3: Search by keywords

Only if Steps 1-2 found no issue numbers.

Build keywords from the branch name segments and commit subjects (strip type prefix, split on hyphens/underscores).

Prefer gh CLI (no permission prompt required):

gh search issues --repo MetaMask/metamask-mobile "<keywords>" --limit 5

Fallback to GitHub MCP if gh is unavailable:

Use the search_issues tool from the user-github MCP server:

{
  "server": "user-github",
  "toolName": "search_issues",
  "arguments": {
    "query": "<keywords>",
    "owner": "MetaMask",
    "repo": "metamask-mobile",
    "perPage": 5
  }
}

Review results and pick the most relevant issue(s).

Output Format

• Fixes: #NUMBER -- use when the PR fully resolves the issue (closes on merge)
• Refs: #NUMBER -- use when the PR partially addresses or is related to the issue

If multiple issues are found:

Fixes: #1234
Refs: #5678

If no issues are found, leave the section as:

Fixes:

Examples

Branch with GitHub issue number: Branch fix/9012_token-balance-stale --> Fixes: #9012

Branch with Jira ticket ID: Branch feat/MCWP-392_pr_desc_skills --> Refs: MCWP-392 (Jira tickets go in Refs:, not Fixes:, since GitHub cannot auto-close Jira tickets)

Commit with reference: Commit message implement caching for token prices (#3456) --> Refs: #3456

Keyword search: Branch feat/bridge-fee-estimation --> search "bridge fee estimation" --> find issue #7890 "Bridge: show estimated fees before confirmation" --> Fixes: #7890