[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-atlassian-twg-jira-resolve-merged-work":3,"mdc--exe73d-key":40,"related-org-atlassian-twg-jira-resolve-merged-work":478,"related-repo-atlassian-twg-jira-resolve-merged-work":657},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":23,"repoUrl":24,"updatedAt":25,"license":26,"forks":27,"topics":28,"repo":35,"sourceUrl":38,"mdContent":39},"twg-jira-resolve-merged-work","resolve stale Jira work items","Clean up stale or unresolved Jira workitems. Dry-run single items, lists, boards, sprints, epics, or projects by matching Jira keys\u002Ftitles to merged PRs, repos, Rovo\u002Fsearch-code hits, and assignee activity.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},"atlassian","Atlassian","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fatlassian.png",[12,16,19,20],{"name":13,"slug":14,"type":15},"Jira","jira","tag",{"name":17,"slug":18,"type":15},"Engineering","engineering",{"name":9,"slug":8,"type":15},{"name":21,"slug":22,"type":15},"Task Management","task-management",6,"https:\u002F\u002Fgithub.com\u002Fatlassian\u002Ftwg-cli","2026-07-22T05:36:11.502648",null,0,[29,8,30,31,32,33,34],"agents","claude","cli","codex","teamwork-graph","twg",{"repoUrl":24,"stars":23,"forks":27,"topics":36,"description":37},[29,8,30,31,32,33,34],"Public home for Atlassian Teamwork Graph CLI users, release notes, issue tracking, agent skills, and marketplace plugin integration notes.","https:\u002F\u002Fgithub.com\u002Fatlassian\u002Ftwg-cli\u002Ftree\u002FHEAD\u002Fskills\u002Ftwg-jira-resolve-merged-work","---\nname: twg-jira-resolve-merged-work\ndescription: >\n   Clean up stale or unresolved Jira workitems. Dry-run single items, lists, boards,\n   sprints, epics, or projects by matching Jira keys\u002Ftitles to merged PRs, repos,\n   Rovo\u002Fsearch-code hits, and assignee activity.\n---\n\n# twg-jira-resolve-merged-work\n\nResolve stale Jira workitems only when merged PR evidence is strong. Plan first;\nmutate only after approval.\n\nUse exact command grammar from live `twg help` \u002F `twg help describe`; do not\nguess board, sprint, transition, workspace, repo, PR, or field syntax.\n\n## CLI launcher fallback\n\nRun `twg \u003Ccommand>`. On shell `command not found`, use `$HOME\u002F.local\u002Fbin\u002Ftwg`\n(macOS\u002FLinux) \u002F `$env:LOCALAPPDATA\\Programs\\twg\\bin\\twg.exe` (PowerShell), then\ntell user to add that directory to PATH. Do not treat auth or command errors as\nPATH failures.\n\n## Scope\n\nAccept one Jira scope:\n\n- One Jira workitem key\u002FURL.\n- A small explicit list of Jira workitem keys\u002FURLs.\n- Board or sprint ID\u002FURL.\n- Epic key.\n- Jira space\u002Fproject key.\n\nDefault to dry run. Ask before mutating unless the user requests reviewed\nexecution. Use a bounded window; otherwise inspect recent active\u002Fcompleted\nsprint work and nearby PR merge dates.\n\n## Workflow\n\n1. Load Jira candidates.\n   - Single\u002Flist: hydrate each provided workitem directly.\n   - Sprint: `jira sprint workitems query`.\n   - Board: board\u002Fbacklog\u002Fsprint commands advertised by live help.\n   - Epic or space: JQL-backed `jira workitem query`.\n   - Hydrate key, title, status\u002Fcategory, assignee, updated time, parent,\n     subtasks\u002Fblockers, and URL.\n\n2. Split the set.\n   - Candidates are not done\u002Fresolved. Peers are done in the same board, sprint,\n     epic, or space.\n   - Exclude epics\u002Fparents. Skip unresolved blockers or incomplete subtasks\n     unless the user explicitly allows them.\n\n3. Discover shared repo context set-wise.\n   - Even for one item or a short list, infer context for the set together.\n   - Extract repos\u002Fworkspaces from linked PRs, commits, branches, project links,\n     Compass\u002Fcomponents, context queries, and resolved peers.\n   - Use completed peers to infer common repos, assignees, Jira-key title\u002Fbranch\n     conventions, PR links, and merge-to-transition lag.\n\n4. Check optional discovery signals.\n   - If `rovo list-apps` shows Bitbucket or GitHub connected, use Rovo search\n     for keys, titles, PR URLs, branches, and repos. Treat it as discovery until\n     hydrated through TWG\u002Fprovider\u002FJira evidence.\n   - If `search-code` is available, search exact keys first, then distinctive\n     title terms in discovered repos. Strong hits are branch names, commit text,\n     changed files, or symbols; broad fuzzy hits stay weak.\n\n5. Expand likely implementers.\n   - Prefer assignees from completed peer items and candidates. Treat reporters\n     and commenters as weak hints.\n   - Query merged PRs authored by these assignees in the window, scoped by\n     discovered repos first; if unknown, infer repos from author\u002Fdate results.\n\n6. Search merged PRs in batches.\n   - Prefer one merged-PR query per repo\u002Fwindow, then match locally across all\n     candidate keys. One PR may satisfy multiple exact keys.\n   - Match exact keys in PR title, description, branch, commits, and linked\n     issue metadata.\n   - Fall back to per-workitem lookup only for no evidence, priority items, or\n     ambiguity.\n\n7. Score confidence.\n   - High: exact key in merged PR or linked PR metadata, plausible timing, no\n     open same-key PR, no blockers\u002Fsubtasks, and target transition exists.\n   - Medium: same assignee\u002Frepo with strong title similarity, or exact key only\n     in commit\u002Fsearch-code evidence.\n   - Low: fuzzy similarity, same author only, unknown repo, or ambiguity.\n\n8. Produce the dry-run plan.\n   - Table columns: workitem key\u002Ftitle, current status, proposed transition,\n     confidence, brief rationale, PR title\u002FURL, merge date, last Jira update,\n     link\u002Frepo proposal, PR title-fix proposal, skipped reason, and verification.\n   - Include exact commands only after live-help verification. Never present\n     low-confidence rows as executable.\n\n## Mutations\n\nOnly mutate after explicit approval of the exact rows or plan.\n\n- Transition: list transitions first, then use only the approved done\u002Fresolved\n  target.\n- Link enrichment: if links are missing, offer `jira workitem link weblink`\n  for PR\u002Frepo URLs after querying links and verifying help. Do not claim this\n  creates native development-panel links.\n- PR title fix: for Bitbucket, update title only when `twg bitbucket` can read\n  the PR, write access is verified, the PR is confidently tied to the item, and\n  the user approved it. For GitHub, update only when an authenticated write tool\n  is available and access is verified; otherwise skip with the reason.\n- Verification: re-read each changed workitem and PR. Report changed keys,\n  statuses, URLs, and failed rows.\n\nDo not transition medium-confidence items automatically. Do not transition\ndeclined\u002Fsuperseded PRs or rows supported only by same author, same repo, or\nfuzzy similarity.\n\n## Output\n\nLead with the decision summary:\n\n- executable high-confidence rows,\n- review-needed medium-confidence rows,\n- skipped unsafe rows,\n- missing repo\u002Fauth\u002Fpermission coverage.\n\nThen provide the dry-run table and exact approval question. Include URLs or\nstable IDs for every workitem and PR used as evidence.\n",{"data":41,"body":42},{"name":4,"description":6},{"type":43,"children":44},"root",[45,52,58,80,87,124,130,135,165,170,176,384,390,395,434,439,445,450,473],{"type":46,"tag":47,"props":48,"children":49},"element","h1",{"id":4},[50],{"type":51,"value":4},"text",{"type":46,"tag":53,"props":54,"children":55},"p",{},[56],{"type":51,"value":57},"Resolve stale Jira workitems only when merged PR evidence is strong. Plan first;\nmutate only after approval.",{"type":46,"tag":53,"props":59,"children":60},{},[61,63,70,72,78],{"type":51,"value":62},"Use exact command grammar from live ",{"type":46,"tag":64,"props":65,"children":67},"code",{"className":66},[],[68],{"type":51,"value":69},"twg help",{"type":51,"value":71}," \u002F ",{"type":46,"tag":64,"props":73,"children":75},{"className":74},[],[76],{"type":51,"value":77},"twg help describe",{"type":51,"value":79},"; do not\nguess board, sprint, transition, workspace, repo, PR, or field syntax.",{"type":46,"tag":81,"props":82,"children":84},"h2",{"id":83},"cli-launcher-fallback",[85],{"type":51,"value":86},"CLI launcher fallback",{"type":46,"tag":53,"props":88,"children":89},{},[90,92,98,100,106,108,114,116,122],{"type":51,"value":91},"Run ",{"type":46,"tag":64,"props":93,"children":95},{"className":94},[],[96],{"type":51,"value":97},"twg \u003Ccommand>",{"type":51,"value":99},". On shell ",{"type":46,"tag":64,"props":101,"children":103},{"className":102},[],[104],{"type":51,"value":105},"command not found",{"type":51,"value":107},", use ",{"type":46,"tag":64,"props":109,"children":111},{"className":110},[],[112],{"type":51,"value":113},"$HOME\u002F.local\u002Fbin\u002Ftwg",{"type":51,"value":115},"\n(macOS\u002FLinux) \u002F ",{"type":46,"tag":64,"props":117,"children":119},{"className":118},[],[120],{"type":51,"value":121},"$env:LOCALAPPDATA\\Programs\\twg\\bin\\twg.exe",{"type":51,"value":123}," (PowerShell), then\ntell user to add that directory to PATH. Do not treat auth or command errors as\nPATH failures.",{"type":46,"tag":81,"props":125,"children":127},{"id":126},"scope",[128],{"type":51,"value":129},"Scope",{"type":46,"tag":53,"props":131,"children":132},{},[133],{"type":51,"value":134},"Accept one Jira scope:",{"type":46,"tag":136,"props":137,"children":138},"ul",{},[139,145,150,155,160],{"type":46,"tag":140,"props":141,"children":142},"li",{},[143],{"type":51,"value":144},"One Jira workitem key\u002FURL.",{"type":46,"tag":140,"props":146,"children":147},{},[148],{"type":51,"value":149},"A small explicit list of Jira workitem keys\u002FURLs.",{"type":46,"tag":140,"props":151,"children":152},{},[153],{"type":51,"value":154},"Board or sprint ID\u002FURL.",{"type":46,"tag":140,"props":156,"children":157},{},[158],{"type":51,"value":159},"Epic key.",{"type":46,"tag":140,"props":161,"children":162},{},[163],{"type":51,"value":164},"Jira space\u002Fproject key.",{"type":46,"tag":53,"props":166,"children":167},{},[168],{"type":51,"value":169},"Default to dry run. Ask before mutating unless the user requests reviewed\nexecution. Use a bounded window; otherwise inspect recent active\u002Fcompleted\nsprint work and nearby PR merge dates.",{"type":46,"tag":81,"props":171,"children":173},{"id":172},"workflow",[174],{"type":51,"value":175},"Workflow",{"type":46,"tag":177,"props":178,"children":179},"ol",{},[180,228,246,269,302,320,343,366],{"type":46,"tag":140,"props":181,"children":182},{},[183,185],{"type":51,"value":184},"Load Jira candidates.",{"type":46,"tag":136,"props":186,"children":187},{},[188,193,206,211,223],{"type":46,"tag":140,"props":189,"children":190},{},[191],{"type":51,"value":192},"Single\u002Flist: hydrate each provided workitem directly.",{"type":46,"tag":140,"props":194,"children":195},{},[196,198,204],{"type":51,"value":197},"Sprint: ",{"type":46,"tag":64,"props":199,"children":201},{"className":200},[],[202],{"type":51,"value":203},"jira sprint workitems query",{"type":51,"value":205},".",{"type":46,"tag":140,"props":207,"children":208},{},[209],{"type":51,"value":210},"Board: board\u002Fbacklog\u002Fsprint commands advertised by live help.",{"type":46,"tag":140,"props":212,"children":213},{},[214,216,222],{"type":51,"value":215},"Epic or space: JQL-backed ",{"type":46,"tag":64,"props":217,"children":219},{"className":218},[],[220],{"type":51,"value":221},"jira workitem query",{"type":51,"value":205},{"type":46,"tag":140,"props":224,"children":225},{},[226],{"type":51,"value":227},"Hydrate key, title, status\u002Fcategory, assignee, updated time, parent,\nsubtasks\u002Fblockers, and URL.",{"type":46,"tag":140,"props":229,"children":230},{},[231,233],{"type":51,"value":232},"Split the set.",{"type":46,"tag":136,"props":234,"children":235},{},[236,241],{"type":46,"tag":140,"props":237,"children":238},{},[239],{"type":51,"value":240},"Candidates are not done\u002Fresolved. Peers are done in the same board, sprint,\nepic, or space.",{"type":46,"tag":140,"props":242,"children":243},{},[244],{"type":51,"value":245},"Exclude epics\u002Fparents. Skip unresolved blockers or incomplete subtasks\nunless the user explicitly allows them.",{"type":46,"tag":140,"props":247,"children":248},{},[249,251],{"type":51,"value":250},"Discover shared repo context set-wise.",{"type":46,"tag":136,"props":252,"children":253},{},[254,259,264],{"type":46,"tag":140,"props":255,"children":256},{},[257],{"type":51,"value":258},"Even for one item or a short list, infer context for the set together.",{"type":46,"tag":140,"props":260,"children":261},{},[262],{"type":51,"value":263},"Extract repos\u002Fworkspaces from linked PRs, commits, branches, project links,\nCompass\u002Fcomponents, context queries, and resolved peers.",{"type":46,"tag":140,"props":265,"children":266},{},[267],{"type":51,"value":268},"Use completed peers to infer common repos, assignees, Jira-key title\u002Fbranch\nconventions, PR links, and merge-to-transition lag.",{"type":46,"tag":140,"props":270,"children":271},{},[272,274],{"type":51,"value":273},"Check optional discovery signals.",{"type":46,"tag":136,"props":275,"children":276},{},[277,290],{"type":46,"tag":140,"props":278,"children":279},{},[280,282,288],{"type":51,"value":281},"If ",{"type":46,"tag":64,"props":283,"children":285},{"className":284},[],[286],{"type":51,"value":287},"rovo list-apps",{"type":51,"value":289}," shows Bitbucket or GitHub connected, use Rovo search\nfor keys, titles, PR URLs, branches, and repos. Treat it as discovery until\nhydrated through TWG\u002Fprovider\u002FJira evidence.",{"type":46,"tag":140,"props":291,"children":292},{},[293,294,300],{"type":51,"value":281},{"type":46,"tag":64,"props":295,"children":297},{"className":296},[],[298],{"type":51,"value":299},"search-code",{"type":51,"value":301}," is available, search exact keys first, then distinctive\ntitle terms in discovered repos. Strong hits are branch names, commit text,\nchanged files, or symbols; broad fuzzy hits stay weak.",{"type":46,"tag":140,"props":303,"children":304},{},[305,307],{"type":51,"value":306},"Expand likely implementers.",{"type":46,"tag":136,"props":308,"children":309},{},[310,315],{"type":46,"tag":140,"props":311,"children":312},{},[313],{"type":51,"value":314},"Prefer assignees from completed peer items and candidates. Treat reporters\nand commenters as weak hints.",{"type":46,"tag":140,"props":316,"children":317},{},[318],{"type":51,"value":319},"Query merged PRs authored by these assignees in the window, scoped by\ndiscovered repos first; if unknown, infer repos from author\u002Fdate results.",{"type":46,"tag":140,"props":321,"children":322},{},[323,325],{"type":51,"value":324},"Search merged PRs in batches.",{"type":46,"tag":136,"props":326,"children":327},{},[328,333,338],{"type":46,"tag":140,"props":329,"children":330},{},[331],{"type":51,"value":332},"Prefer one merged-PR query per repo\u002Fwindow, then match locally across all\ncandidate keys. One PR may satisfy multiple exact keys.",{"type":46,"tag":140,"props":334,"children":335},{},[336],{"type":51,"value":337},"Match exact keys in PR title, description, branch, commits, and linked\nissue metadata.",{"type":46,"tag":140,"props":339,"children":340},{},[341],{"type":51,"value":342},"Fall back to per-workitem lookup only for no evidence, priority items, or\nambiguity.",{"type":46,"tag":140,"props":344,"children":345},{},[346,348],{"type":51,"value":347},"Score confidence.",{"type":46,"tag":136,"props":349,"children":350},{},[351,356,361],{"type":46,"tag":140,"props":352,"children":353},{},[354],{"type":51,"value":355},"High: exact key in merged PR or linked PR metadata, plausible timing, no\nopen same-key PR, no blockers\u002Fsubtasks, and target transition exists.",{"type":46,"tag":140,"props":357,"children":358},{},[359],{"type":51,"value":360},"Medium: same assignee\u002Frepo with strong title similarity, or exact key only\nin commit\u002Fsearch-code evidence.",{"type":46,"tag":140,"props":362,"children":363},{},[364],{"type":51,"value":365},"Low: fuzzy similarity, same author only, unknown repo, or ambiguity.",{"type":46,"tag":140,"props":367,"children":368},{},[369,371],{"type":51,"value":370},"Produce the dry-run plan.",{"type":46,"tag":136,"props":372,"children":373},{},[374,379],{"type":46,"tag":140,"props":375,"children":376},{},[377],{"type":51,"value":378},"Table columns: workitem key\u002Ftitle, current status, proposed transition,\nconfidence, brief rationale, PR title\u002FURL, merge date, last Jira update,\nlink\u002Frepo proposal, PR title-fix proposal, skipped reason, and verification.",{"type":46,"tag":140,"props":380,"children":381},{},[382],{"type":51,"value":383},"Include exact commands only after live-help verification. Never present\nlow-confidence rows as executable.",{"type":46,"tag":81,"props":385,"children":387},{"id":386},"mutations",[388],{"type":51,"value":389},"Mutations",{"type":46,"tag":53,"props":391,"children":392},{},[393],{"type":51,"value":394},"Only mutate after explicit approval of the exact rows or plan.",{"type":46,"tag":136,"props":396,"children":397},{},[398,403,416,429],{"type":46,"tag":140,"props":399,"children":400},{},[401],{"type":51,"value":402},"Transition: list transitions first, then use only the approved done\u002Fresolved\ntarget.",{"type":46,"tag":140,"props":404,"children":405},{},[406,408,414],{"type":51,"value":407},"Link enrichment: if links are missing, offer ",{"type":46,"tag":64,"props":409,"children":411},{"className":410},[],[412],{"type":51,"value":413},"jira workitem link weblink",{"type":51,"value":415},"\nfor PR\u002Frepo URLs after querying links and verifying help. Do not claim this\ncreates native development-panel links.",{"type":46,"tag":140,"props":417,"children":418},{},[419,421,427],{"type":51,"value":420},"PR title fix: for Bitbucket, update title only when ",{"type":46,"tag":64,"props":422,"children":424},{"className":423},[],[425],{"type":51,"value":426},"twg bitbucket",{"type":51,"value":428}," can read\nthe PR, write access is verified, the PR is confidently tied to the item, and\nthe user approved it. For GitHub, update only when an authenticated write tool\nis available and access is verified; otherwise skip with the reason.",{"type":46,"tag":140,"props":430,"children":431},{},[432],{"type":51,"value":433},"Verification: re-read each changed workitem and PR. Report changed keys,\nstatuses, URLs, and failed rows.",{"type":46,"tag":53,"props":435,"children":436},{},[437],{"type":51,"value":438},"Do not transition medium-confidence items automatically. Do not transition\ndeclined\u002Fsuperseded PRs or rows supported only by same author, same repo, or\nfuzzy similarity.",{"type":46,"tag":81,"props":440,"children":442},{"id":441},"output",[443],{"type":51,"value":444},"Output",{"type":46,"tag":53,"props":446,"children":447},{},[448],{"type":51,"value":449},"Lead with the decision summary:",{"type":46,"tag":136,"props":451,"children":452},{},[453,458,463,468],{"type":46,"tag":140,"props":454,"children":455},{},[456],{"type":51,"value":457},"executable high-confidence rows,",{"type":46,"tag":140,"props":459,"children":460},{},[461],{"type":51,"value":462},"review-needed medium-confidence rows,",{"type":46,"tag":140,"props":464,"children":465},{},[466],{"type":51,"value":467},"skipped unsafe rows,",{"type":46,"tag":140,"props":469,"children":470},{},[471],{"type":51,"value":472},"missing repo\u002Fauth\u002Fpermission coverage.",{"type":46,"tag":53,"props":474,"children":475},{},[476],{"type":51,"value":477},"Then provide the dry-run table and exact approval question. Include URLs or\nstable IDs for every workitem and PR used as evidence.",{"items":479,"total":656},[480,497,515,532,547,558,573,591,606,618,632,642],{"slug":481,"name":481,"fn":482,"description":483,"org":484,"tags":485,"stars":494,"repoUrl":495,"updatedAt":496},"capture-tasks-from-meeting-notes","create Jira tasks from meeting notes","Analyze meeting notes to find action items and create Jira tasks for assigned work. When an agent needs to: (1) Create Jira tasks or tickets from meeting notes, (2) Extract or find action items from notes or Confluence pages, (3) Parse meeting notes for assigned tasks, or (4) Analyze notes and generate tasks for team members. Identifies assignees, looks up account IDs, and creates tasks with proper context.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[486,489,490,493],{"name":487,"slug":488,"type":15},"Automation","automation",{"name":13,"slug":14,"type":15},{"name":491,"slug":492,"type":15},"Meetings","meetings",{"name":21,"slug":22,"type":15},848,"https:\u002F\u002Fgithub.com\u002Fatlassian\u002Fatlassian-mcp-server","2026-07-12T07:58:45.323861",{"slug":498,"name":498,"fn":499,"description":500,"org":501,"tags":502,"stars":494,"repoUrl":495,"updatedAt":514},"generate-status-report","generate project status reports for Confluence","Generate project status reports from Jira issues and publish to Confluence. When an agent needs to: (1) Create a status report for a project, (2) Summarize project progress or updates, (3) Generate weekly\u002Fdaily reports from Jira, (4) Publish status summaries to Confluence, or (5) Analyze project blockers and completion. Queries Jira issues, categorizes by status\u002Fpriority, and creates formatted reports for delivery managers and executives.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[503,504,507,508,511],{"name":9,"slug":8,"type":15},{"name":505,"slug":506,"type":15},"Confluence","confluence",{"name":13,"slug":14,"type":15},{"name":509,"slug":510,"type":15},"Project Management","project-management",{"name":512,"slug":513,"type":15},"Reporting","reporting","2026-07-12T07:58:38.457696",{"slug":516,"name":516,"fn":517,"description":518,"org":519,"tags":520,"stars":494,"repoUrl":495,"updatedAt":531},"jira-sprint-dashboard","create Jira sprint dashboards","Create a visual Jira sprint dashboard from Jira project, space, sprint, board, filter, JQL, work item keys, or Jira URL data. Use when the user asks for a Jira sprint dashboard, standup dashboard, sprint review, delivery review, engineering manager dashboard, WIP review, planning view, closeout view, or a visual snapshot of Jira work that is more useful than a flat report. Use the richest dashboard format supported by the current agent, such as Cursor Canvas, an interactive artifact, HTML, or Markdown.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[521,524,527,528],{"name":522,"slug":523,"type":15},"Agile","agile",{"name":525,"slug":526,"type":15},"Dashboards","dashboards",{"name":13,"slug":14,"type":15},{"name":529,"slug":530,"type":15},"Sprint Planning","sprint-planning","2026-07-12T07:58:41.031798",{"slug":533,"name":533,"fn":534,"description":535,"org":536,"tags":537,"stars":494,"repoUrl":495,"updatedAt":546},"search-company-knowledge","search internal company knowledge bases","Search across company knowledge bases (Confluence, Jira, internal docs) to find and explain internal concepts, processes, and technical details. When an agent needs to: (1) Find or search for information about systems, terminology, processes, deployment, authentication, infrastructure, architecture, or technical concepts, (2) Search internal documentation, knowledge base, company docs, or our docs, (3) Explain what something is, how it works, or look up information, or (4) Synthesize information from multiple sources. Searches in parallel and provides cited answers.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[538,539,542,543],{"name":505,"slug":506,"type":15},{"name":540,"slug":541,"type":15},"Enterprise Search","enterprise-search",{"name":13,"slug":14,"type":15},{"name":544,"slug":545,"type":15},"Knowledge Management","knowledge-management","2026-07-12T07:58:39.684132",{"slug":548,"name":548,"fn":549,"description":550,"org":551,"tags":552,"stars":494,"repoUrl":495,"updatedAt":557},"spec-to-backlog","convert Confluence specifications to Jira backlogs","Automatically convert Confluence specification documents into structured Jira backlogs with Epics and implementation tickets. When an agent needs to: (1) Create Jira tickets from a Confluence page, (2) Generate a backlog from a specification, (3) Break down a spec into implementation tasks, or (4) Convert requirements into Jira issues. Handles reading Confluence pages, analyzing specifications, creating Epics with proper structure, and generating detailed implementation tickets linked to the Epic.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[553,554,555,556],{"name":522,"slug":523,"type":15},{"name":505,"slug":506,"type":15},{"name":13,"slug":14,"type":15},{"name":509,"slug":510,"type":15},"2026-07-12T07:58:37.200385",{"slug":559,"name":559,"fn":560,"description":561,"org":562,"tags":563,"stars":494,"repoUrl":495,"updatedAt":572},"triage-issue","triage bug reports in Jira","Intelligently triage bug reports and error messages by searching for duplicates in Jira and offering to create new issues or add comments to existing ones. When an agent needs to: (1) Triage a bug report or error message, (2) Check if an issue is a duplicate, (3) Find similar past issues, (4) Create a new bug ticket with proper context, or (5) Add information to an existing ticket. Searches Jira for similar issues, identifies duplicates, checks fix history, and helps create well-structured bug reports.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[564,567,568,569],{"name":565,"slug":566,"type":15},"Debugging","debugging",{"name":13,"slug":14,"type":15},{"name":509,"slug":510,"type":15},{"name":570,"slug":571,"type":15},"Triage","triage","2026-07-12T07:58:33.007343",{"slug":574,"name":574,"fn":575,"description":576,"org":577,"tags":578,"stars":588,"repoUrl":589,"updatedAt":590},"forge-app-builder","build and deploy Atlassian Forge apps","Guides building, deploying, troubleshooting, and installing Atlassian Forge apps — custom extensions built with the Forge CLI (forge create, forge deploy, forge install). Use when the user wants to create a Forge app (issue panels, dashboard gadgets, Confluence macros, global pages), is encountering Forge CLI errors or deployment issues (e.g. forge install failures, environment errors), or needs help with Forge-specific concepts like resolvers, UI Kit, manifest scopes, or developer spaces. Do not use for general Jira configuration, automation rules, JQL queries, or Atlassian REST API usage outside of a Forge app context.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[579,580,582,585],{"name":9,"slug":8,"type":15},{"name":581,"slug":31,"type":15},"CLI",{"name":583,"slug":584,"type":15},"Deployment","deployment",{"name":586,"slug":587,"type":15},"Plugin Development","plugin-development",14,"https:\u002F\u002Fgithub.com\u002Fatlassian\u002Fforge-skills","2026-07-12T07:58:52.007851",{"slug":592,"name":592,"fn":593,"description":594,"org":595,"tags":596,"stars":588,"repoUrl":589,"updatedAt":605},"forge-app-review","review Atlassian Forge app readiness","Performs a lightweight pre-release readiness review of Atlassian Forge apps across manifest\u002Fmodule wiring, architecture, runtime compatibility, dependency posture, tests, deploy readiness, and obvious security, cost, or reliability smells. Use when the user asks \"review my Forge app\", \"pre-deploy check\", \"is this app ready to ship\", \"review manifest\", \"general app review\", \"release readiness\", or asks for a broad quality pass. Do not use for deep security audits\u002FSAST\u002Fexploitability review, cost optimization, or diagnosing a known broken app; route those to forge-security-review, forge-cost-optimizer, or forge-debugger respectively.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[597,598,601,602],{"name":9,"slug":8,"type":15},{"name":599,"slug":600,"type":15},"Code Analysis","code-analysis",{"name":583,"slug":584,"type":15},{"name":603,"slug":604,"type":15},"QA","qa","2026-07-12T07:58:50.744672",{"slug":607,"name":607,"fn":608,"description":609,"org":610,"tags":611,"stars":588,"repoUrl":589,"updatedAt":617},"forge-connector","build Atlassian Forge Teamwork Graph connectors","Guides building and deploying Atlassian Forge Teamwork Graph connector apps that ingest external data into Atlassian's Teamwork Graph, making it searchable in Rovo Search and surfaced in Rovo Chat. Use when the user wants to build a Forge connector, ingest external data into Atlassian, connect a third-party tool (e.g. Google Drive, ServiceNow, Salesforce) to Atlassian, make external content searchable in Rovo, build a graph:connector module, use the @forge\u002Fteamwork-graph SDK, or implement onConnectionChange \u002F validateConnection functions.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[612,615,616],{"name":613,"slug":614,"type":15},"API Development","api-development",{"name":17,"slug":18,"type":15},{"name":540,"slug":541,"type":15},"2026-07-12T07:58:48.520248",{"slug":619,"name":619,"fn":620,"description":621,"org":622,"tags":623,"stars":588,"repoUrl":589,"updatedAt":631},"forge-cost-optimizer","optimize Atlassian Forge platform costs","Optimizes Atlassian Forge apps to reduce platform consumption and avoid unnecessary costs using Atlassian's \"Optimise Forge platform costs\" guidance. Use when the user asks to optimize Forge app costs, reduce Forge invocations, lower GB-seconds, reduce storage or log usage, tune memory, replace polling, improve scheduled triggers, reduce KVS writes, move work to the frontend, use bridge APIs, batch API calls, add caching, or evaluate Forge Remote trade-offs. By default, perform an audit first and offer to make the recommended changes after presenting the audit. Only modify files immediately when the user explicitly asks the agent to implement or apply optimizations.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[624,625,628],{"name":9,"slug":8,"type":15},{"name":626,"slug":627,"type":15},"Cost Optimization","cost-optimization",{"name":629,"slug":630,"type":15},"Operations","operations","2026-07-12T07:58:53.557299",{"slug":633,"name":633,"fn":634,"description":635,"org":636,"tags":637,"stars":588,"repoUrl":589,"updatedAt":641},"forge-debugger","diagnose and fix Atlassian Forge apps","Diagnoses and fixes issues in Atlassian Forge apps. Use this skill whenever a Forge app has errors, crashes, shows blank UI, fails to deploy, doesn't appear after installation, has permission issues, or produces unexpected output. Trigger on any mention of forge logs, forge deploy errors, resolver errors, blank panels, missing scopes, Custom UI not rendering, production vs dev discrepancies, or any Jira\u002FConfluence app that \"stopped working\". Also trigger when the user asks to debug, troubleshoot, investigate, or fix a Forge app issue — even if they haven't used the word \"Forge\" but describe a Jira panel or Confluence macro acting up.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[638,639,640],{"name":9,"slug":8,"type":15},{"name":565,"slug":566,"type":15},{"name":583,"slug":584,"type":15},"2026-07-12T07:58:47.226713",{"slug":643,"name":643,"fn":644,"description":645,"org":646,"tags":647,"stars":588,"repoUrl":589,"updatedAt":655},"forge-security-review","perform security reviews for Forge apps","Performs a white-box security review of Atlassian Forge apps using structured, Forge-specific security rules and evidence-driven reporting. Use when the user asks for a Forge security review, security audit, vuln assessment, pentest-style code review, authz review, tenant isolation analysis, web trigger hardening, or static analysis execution for a Forge app.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[648,651,652],{"name":649,"slug":650,"type":15},"Audit","audit",{"name":599,"slug":600,"type":15},{"name":653,"slug":654,"type":15},"Security","security","2026-07-12T07:58:54.806538",24,{"items":658,"total":750},[659,668,681,696,709,722,740],{"slug":34,"name":34,"fn":660,"description":661,"org":662,"tags":663,"stars":23,"repoUrl":24,"updatedAt":667},"execute Atlassian work-data tasks","Root TWG CLI skill for Atlassian work-data tasks. Use typed commands for known anchors; use live `twg help` only when command shape or output contract is uncertain.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[664,665,666],{"name":9,"slug":8,"type":15},{"name":487,"slug":488,"type":15},{"name":581,"slug":31,"type":15},"2026-07-25T05:31:49.287124",{"slug":669,"name":669,"fn":670,"description":671,"org":672,"tags":673,"stars":23,"repoUrl":24,"updatedAt":680},"twg-agentic-search","perform iterative enterprise knowledge search","Use with root `twg` for deep iterative enterprise\u002Fcompany knowledge search and internal research with Rovo Search across connected apps\u002Fconnectors including Confluence, Jira, Drive, Slack, Bitbucket, and GitHub.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[674,675,676,677],{"name":9,"slug":8,"type":15},{"name":540,"slug":541,"type":15},{"name":544,"slug":545,"type":15},{"name":678,"slug":679,"type":15},"Research","research","2026-07-25T05:56:27.582838",{"slug":682,"name":682,"fn":683,"description":684,"org":685,"tags":686,"stars":23,"repoUrl":24,"updatedAt":695},"twg-bench-lite","run A\u002FB comparisons of Atlassian context","Run a lightweight single-prompt A\u002FB comparison of free Atlassian\u002Flocal MCP context vs TWG CLI graph context using paired read-only agent sessions.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[687,690,691,694],{"name":688,"slug":689,"type":15},"A\u002FB Testing","a-b-testing",{"name":9,"slug":8,"type":15},{"name":692,"slug":693,"type":15},"MCP","mcp",{"name":678,"slug":679,"type":15},"2026-07-22T05:36:16.491486",{"slug":697,"name":697,"fn":698,"description":699,"org":700,"tags":701,"stars":23,"repoUrl":24,"updatedAt":708},"twg-confluence","manage Confluence content and hierarchy","Use with root `twg` for Confluence content, spaces, hierarchy, authoring, editing, comments, versions, permissions, exports, and CQL. Applies Confluence semantics and safe write rules.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[702,703,704,707],{"name":9,"slug":8,"type":15},{"name":505,"slug":506,"type":15},{"name":705,"slug":706,"type":15},"Documents","documents",{"name":544,"slug":545,"type":15},"2026-07-25T05:31:47.271484",{"slug":710,"name":710,"fn":711,"description":712,"org":713,"tags":714,"stars":23,"repoUrl":24,"updatedAt":721},"twg-context-discovery","discover project context and dependencies","Use with root `twg` for deep context, dependency maps, related entities, project-to-repo discovery, OOO catch-ups, and \"catch me up\" requests around a concrete anchor.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[715,716,717,718],{"name":9,"slug":8,"type":15},{"name":544,"slug":545,"type":15},{"name":678,"slug":679,"type":15},{"name":719,"slug":720,"type":15},"Search","search","2026-07-25T05:31:51.299922",{"slug":723,"name":723,"fn":724,"description":725,"org":726,"tags":727,"stars":23,"repoUrl":24,"updatedAt":739},"twg-engineering-work","analyze engineering work and pull requests","Use with root `twg` for code search, repositories using an API\u002Fpackage, implementation and reverse-dependency discovery, PR status and reviews, repo contributors, hot areas, and issue-to-PR lookups.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[728,729,732,733,736],{"name":9,"slug":8,"type":15},{"name":730,"slug":731,"type":15},"Code Review","code-review",{"name":17,"slug":18,"type":15},{"name":734,"slug":735,"type":15},"GitHub","github",{"name":737,"slug":738,"type":15},"Pull Requests","pull-requests","2026-07-25T05:31:52.317362",{"slug":741,"name":741,"fn":742,"description":743,"org":744,"tags":745,"stars":23,"repoUrl":24,"updatedAt":749},"twg-jira","manage Jira work items and projects","Use with root `twg` for Jira workitems, projects, boards, sprints, fields, transitions, comments, links, and administration. Applies Jira semantics and safe mutation rules.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[746,747,748],{"name":9,"slug":8,"type":15},{"name":13,"slug":14,"type":15},{"name":21,"slug":22,"type":15},"2026-07-25T05:31:46.279241",11]