What problem does it solve? Ticket statuses change in the tracker and pull requests get opened long after a session's notes were written, so the frontmatter in a session's notes.md drifts out of date and the dashboard shows stale information. This Skill realigns those two facts unattended, without touching anything else. ## Core Features & Use Cases - Ticket status refresh: Queries the tracker once with a single JQL call (e.g. Atlassian MCP searchJiraIssuesUsingJql) for all tickets and rewrites the ticket_states frontmatter key using the tracker's own status wording. - Pull request discovery: Runs one gh pr list per known repository filtered locally by jq on branch names containing ticket ids, falling back to gh search prs when no repository is known, and appends new PR links without ever removing existing ones. - Use Case: The dashboard's Sync button invokes this Skill with a notes path; it reads the frontmatter, fetches current Jira statuses and GitHub PRs, rewrites only those keys, and prints a one-line English confirmation of what changed. ## Quick Start Run /sync-refs with the path to a session's notes.md file to refresh its ticket statuses and attach any missing pull request links.
