Terminal
Terminal/Skill
Finds stale Jira work items that have matching merged pull requests, and previews which ones to resolve before any change is made.
By Atlassian
Works with
npx skills add atlassian/twg-cli --skill twg-jira-resolve-merged-workResolve stale Jira workitems only when merged PR evidence is strong. Plan first; mutate only after approval.
Use exact command grammar from live twg help / twg help describe <path>; do not
guess board, sprint, transition, workspace, repo, PR, or field syntax.
Run twg <command>. On shell command not found, use $HOME/.local/bin/twg
(macOS/Linux) / $env:LOCALAPPDATA\Programs\twg\bin\twg.exe (PowerShell), then
tell user to add that directory to PATH. Do not treat auth or command errors as
PATH failures.
Accept one Jira scope:
Default to dry run. Ask before mutating unless the user requests reviewed execution. Use a bounded window; otherwise inspect recent active/completed sprint work and nearby PR merge dates.
Load Jira candidates.
jira sprint workitems query.jira workitem query.Split the set.
Discover shared repo context set-wise.
Check optional discovery signals.
rovo list-apps shows Bitbucket or GitHub connected, use Rovo search
for keys, titles, PR URLs, branches, and repos. Treat it as discovery until
hydrated through TWG/provider/Jira evidence.search-code is available, search exact keys first, then distinctive
title terms in discovered repos. Strong hits are branch names, commit text,
changed files, or symbols; broad fuzzy hits stay weak.Expand likely implementers.
Search merged PRs in batches.
Score confidence.
Produce the dry-run plan.
Only mutate after explicit approval of the exact rows or plan.
jira workitem link weblink
for PR/repo URLs after querying links and verifying help. Do not claim this
creates native development-panel links.bitbucket pull-requests get leaf can read
the PR, write access is verified, the PR is confidently tied to the item, and
the user approved it. For GitHub, update only when an authenticated write tool
is available and access is verified; otherwise skip with the reason.Do not transition medium-confidence items automatically. Do not transition declined/superseded PRs or rows supported only by same author, same repo, or fuzzy similarity.
Lead with the decision summary:
Then provide the dry-run table and exact approval question. Include URLs or stable IDs for every workitem and PR used as evidence.