Make your Jira board match the code in GitHub

**Objective:** For Jira project `{project-key}`, compare each issue updated in the last `{lookback-days}` days (default 30) with the GitHub commits in repository `{repository}` (if blank, use the connector's default repository) and report where Jira's status disagrees with the code.

**Step 1: Read the Jira side**

Call `jira-get-issue` with `project-key` set to `{project-key}`, `updated.from` set to today minus `{lookback-days}` days, and `max-records` 200. If nothing comes back, report that no issues were updated in that window and stop.

**Step 2: Read the GitHub side once**

Call `github-get-commit` with `commit-date.from` set to the same date and `max-records` 500 (pass `company` = `{repository}` when given). Do not call it once per issue.

**Step 3: Match**

For each Jira issue, find the commits whose message contains its `issue-key` exactly (uppercase project key, hyphen, number; `ABC-12` must not match `ABC-123`).

Classify each issue:

* **Done, no commits:** status is Done (or another closed status) but no commit references it.
* **Not started, has commits:** status is To Do (or another not-started status) but commits reference it.
* **Stalled:** status is In Progress but its newest commit is more than 7 days old, or it has no commits.
* **Consistent:** everything else.

Jira status names vary by site. Classify by meaning, and list any status you could not place.

**Step 4: Report**

A table per class except Consistent: issue-key, summary, status, assignee, commit count, newest commit date. End with the Consistent count and the number of commits in the window that referenced no issue in this project.

**Rules & Guidelines:**

* `jira-get-issue` is on the jira server; `github-get-commit` is on the github server.
* This prompt is read-only. Do NOT call `jira-update-issue`, `jira-assign-issue` or `jira-add-issue-comment`. Suggest status changes in the report instead of making them.

**Validation:**

* If `github-get-commit` returns exactly `max-records` rows, say the commit list may be truncated and the Done, no commits class may contain false positives.
* If the commits carry no Jira keys at all, say the team may not reference keys in commit messages, and do not present the Done, no commits class as a defect.