Terminal
Terminal/Skill
Searches code, repos, PRs and reviews across Bitbucket, GitHub and Jira via the Teamwork Graph CLI, including PR status and stale reviews.
By Atlassian
Works with
npx skills add atlassian/twg-cli --skill twg-engineering-workUse with root twg. Follow documented command shapes; use focused live twg help
only for missing or uncertain commands, arguments, or output contracts.
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.
Resolve the engineering anchor:
references/code-search.md.Provider-native PR commands apply only to their host; Bitbucket activity/comment/task commands never apply to GitHub PRs.
../twg-code-review/SKILL.md only when named or code review requests additional context.
Exclude ordinary reviews during testing.twg-status-rollups; this skill adds
PR detail.references/code-search.md.twg-status-rollups plus
../twg-status-rollups/references/personal-work-summary.md.Hydrate a PR set in one call, never one call per PR.
pull-requests get <pr-url…>
covers the whole set. Use PR URLs (url in query results); ARIs give
approved: null.bitbucket pull-requests query (author, reviewer, state, window)
or pull-requests query (user/org).pr-tree reviewer counts mean "listed as reviewer", not approved.bitbucket pipeline query lists recent runs only (--limit
default 15); raise it and check returned timestamps before claiming window
coverage. pipeline get only for failures whose logs matter.
commits/deployments batch by ARI.bitbucket pull-requests activity; past ~10 PRs, sample and state it. With no
--type it returns approval, update, and comment events together, so never
call it again per event type.Query reviewer-scoped open PRs; sort by waiting time, requested action, unresolved tasks/comments, failing CI, and relevance. Hydrate only PRs needing action.
Find PRs open or waiting beyond the threshold; group by repo, author, reviewer, and stage. Bottleneck patterns: missing reviewer, unresolved tasks, failing CI, repeated request-changes, owner unavailable.
Use workitem context for linked PRs, commits, branches, and repos. Fetch PRs only when the user asks for details, status, or next action.
Query PRs/commits for the repo and window; group by files/areas, authors, reviewers, and themes. Hot areas rank changed area, frequency, and ownership.
Resolve org/team first, then collect PRs for members or repos in the window.
Group into themes and repos/services, and call out gaps where PR-only evidence
omits Jira, docs, planning, or customer context. For one person with a broader
prompt, use twg-status-rollups.
Queues: PR, repo, owner, state, reason, next action, evidence. Reports: workstreams, contributors, bottlenecks, risks, gaps, and stable artifact URLs/IDs.