use case
Catch scope drift between a PR and its ticket — on demand
Did the PR actually do what the ticket asked? Comment @syncTrace on a GitHub pull request or its Linear issue, and syncTrace compares the full diff to the ticket, then posts a scope/coverage breakdown.
What it does
- ✅ covered · ⚠️ added beyond spec · ❌ not addressed · ❓ to confirm
- Resolves the exact PR↔ticket link — never guessed from branch names
- Posts on both the Linear issue and the PR
- Re-runs edit the comment in place — no notification spam
How it works
- 01Connect GitHub and Linear.
- 02Comment @syncTrace on a PR or its linked Linear issue.
- 03syncTrace reacts 👀, compares the diff to the ticket, and posts the breakdown.
Related
AI pull request summaries
Turn every merged pull request into a plain-language summary — headline, key changes, impact areas, and risks — posted to Slack automatically or for review.
Documentation impact & drift detectionCatch documentation drift at merge time: syncTrace flags which docs a change likely made stale and suggests the update, delivered alongside the PR summary in Slack.