Back to Details

twg-engineering-work

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

twg-engineering-work

twg-engineering-work

Use together with the root 
twg
skill. Use documented command shapes when they cover the request. Use focused live 
twg help
only when the required command, argument, or output contract is absent or uncertain.
与核心
twg
技能配合使用。当已有文档化的命令格式能满足需求时，优先使用该格式。仅当所需命令、参数或输出约定缺失或不确定时，才使用针对性的实时
twg help
。

CLI launcher fallback

CLI启动器回退方案

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.
运行
twg <command>
。若shell提示“command not found”，请使用
$HOME/.local/bin/twg
（macOS/Linux系统）或
$env:LOCALAPPDATA\Programs\twg\bin\twg.exe
（PowerShell环境），然后告知用户将该目录添加至PATH环境变量。请勿将身份验证或命令错误视为PATH配置问题。

Use When

使用场景

  • "Which PRs are waiting for my review?"
  • "Where is this API implemented or used?"
  • "Which repositories directly depend on this package?"
  • "Latest PRs for this issue"
  • "Who contributed most to this repo/topic?"
  • "Repos I created PRs in"
  • "Stale reviews"
  • "Review flow or bottlenecks"
  • "PR-only status for a user, team, or repo"
  • "PR status for Alice" or "this person's PRs"
  • "My PRs this week"
  • "Summarize my pull requests for a time window"
  • "Open bugs/tasks with PRs in flight"
  • "哪些PR正在等待我的评审？"
  • "这个API在哪里实现或被使用？"
  • "哪些仓库直接依赖这个包？"
  • "该问题对应的最新PR"
  • "谁对这个仓库/主题贡献最多？"
  • "我提交过PR的仓库"
  • "过期评审"
  • "评审流程或瓶颈"
  • "指定用户、团队或仓库的PR专属状态"
  • "Alice的PR状态"或"这个人的PR情况"
  • "我本周的PR"
  • "汇总我在某个时间段内的拉取请求"
  • "已有PR在处理中的未解决缺陷/任务"

First Move

第一步操作

Resolve the engineering anchor:
  • Repo prompt: identify workspace and repo from URL, local checkout, or repo query.
  • PR prompt: resolve exact PR URL, ID, workspace, and repo.
  • Workitem prompt: fetch/context the Jira workitem to discover linked PRs, commits, branches, and repos.
  • Topic prompt: resolve/search once, then find linked repos, PRs, and workitems.
  • Code prompt: resolve the concrete package, API, symbol, or repository anchor, then load 
    references/code-search.md
    for route selection and hydration.
Use matching typed pull-request, Bitbucket, Jira, context, and search commands. Provider-native PR commands apply only to their host; Bitbucket activity/comment/task commands never apply to GitHub PRs. Use focused help for uncertain routes/contracts.
确定工程锚点：
  • 仓库提示：从URL、本地检出目录或仓库查询中识别工作区和仓库。
  • PR提示：解析精确的PR URL、ID、工作区和仓库。
  • 工作项提示：获取/关联Jira工作项上下文，以发现关联的PR、提交记录、分支和仓库。
  • 主题提示：先解析/搜索一次，再查找关联的仓库、PR和工作项。
  • 代码提示：解析具体的包、API、符号或仓库锚点，然后加载
    references/code-search.md
    进行路由选择和内容补充。
使用匹配的类型化拉取请求、Bitbucket、Jira、上下文和搜索命令。服务商原生PR命令仅适用于对应的平台；Bitbucket的活动/评论/任务命令绝不应用于GitHub PR。若路由/约定不确定，使用针对性帮助。

Route Selection

路由选择

  • For queues, query candidate PRs first, then hydrate selected PRs needing action.
  • For stale reviews, group by repo, author, reviewer, and stage before fetching detailed comments or diffs.
  • For issue-to-PR lookup, use workitem context before broad PR text search.
  • For repo contributors and hot areas, combine PR/commit/file-area signals with ownership and review evidence.
  • For PR leadership/team/org rollups, use 
    twg-status-rollups
    ; this skill supplements PR details.
  • For person/repo status, collect merged/open PRs for relevant people, repos, and window.
  • Code: load 
    references/code-search.md
    .
  • For person-scoped summaries with Jira, docs, meetings, planning, or notifications, use 
    twg-status-rollups
    plus 
    ../twg-status-rollups/references/personal-work-summary.md
    ; this skill owns PR-only work.
  • 对于队列，先查询候选PR，再补充需要操作的选定PR的详细信息。
  • 对于过期评审，在获取详细评论或差异之前，先按仓库、作者、评审者和阶段分组。
  • 对于问题到PR的关联查询，先使用工作项上下文，再进行广泛的PR文本搜索。
  • 对于仓库贡献者和热点区域，结合PR/提交/文件区域信号与归属权及评审证据。
  • 对于PR负责人/团队/组织汇总，使用
    twg-status-rollups
    ；本技能用于补充PR细节。
  • 对于个人/仓库状态，收集相关人员、仓库和时间段内的已合并/未合并PR。
  • 代码相关：加载
    references/code-search.md
    。
  • 对于包含Jira、文档、会议、规划或通知的个人范围汇总，使用
    twg-status-rollups
    及
    ../twg-status-rollups/references/personal-work-summary.md
    ；本技能仅负责PR相关工作。

Evidence Policy

证据策略

  • Hydrate PR details, comments, tasks, pipeline status, and diff only for stale, blocked, central, or high-impact PRs.
  • For PR rollups, stop after the evidence set identifies the main themes, repos/services, owners, and recency. Do not keep searching for more PRs when the next batch would only add more examples of the same theme.
  • For review status, include age, requested reviewers, comments/tasks, approval state, CI/check or pipeline state, and last activity when the provider surface exposes them.
  • For repo/team reports, group by repo, service, or workstream rather than only person counts.
  • Inspect PR titles/descriptions and linked issues to infer themes; do not rank solely by PR count.
  • Keep Bitbucket, GitHub connector/tool, and Atlassian auth failures separate.
  • If PR graph or repo-wide query calls repeatedly fail, make one narrower fallback using known repos, people, workitems, or search anchors. If that also fails, answer from the successful evidence and call out the PR coverage gap.
  • 仅为过期、阻塞、核心或高影响的PR补充详细信息、评论、任务、流水线状态和差异内容。
  • 对于PR汇总，当证据集已确定主要主题、仓库/服务、所有者和时效性后，停止搜索。当下一批PR仅会增加同一主题的更多示例时，无需继续搜索。
  • 对于评审状态，若服务商平台提供相关信息，需包含时长、请求的评审者、评论/任务、审批状态、CI/检查或流水线状态，以及最后活动时间。
  • 对于仓库/团队报告，按仓库、服务或工作流分组，而非仅按人员数量统计。
  • 查看PR标题/描述及关联问题以推断主题；切勿仅按PR数量排名。
  • 区分Bitbucket、GitHub连接器/工具和Atlassian的身份验证失败情况。
  • 若PR图谱或仓库范围查询反复失败，使用已知的仓库、人员、工作项或搜索锚点进行一次更窄范围的回退查询。若仍失败，基于成功获取的证据作答，并指出PR覆盖缺口。

Recipe Cards

方案卡

Review Queue

评审队列

Query reviewer-scoped open PRs. Sort by waiting time, requested action, unresolved tasks/comments, failing CI, and project relevance. Hydrate only PRs that need action.
查询指定评审者范围内的未关闭PR。按等待时间、请求操作、未解决任务/评论、CI失败情况及项目相关性排序。仅补充需要操作的PR的详细信息。

Stale Reviews / Review Bottlenecks

过期评审 / 评审瓶颈

Find PRs open or waiting beyond the threshold. Group by repo, author, reviewer, and stage. Identify bottleneck patterns such as missing reviewer, unresolved tasks, failing CI, repeated request-changes, or owner unavailable.
找出超出阈值的未关闭或等待中的PR。按仓库、作者、评审者和阶段分组。识别瓶颈模式，如缺失评审者、未解决任务、CI失败、反复要求修改或所有者不可用等。

Issue PRs

问题关联PR

Use workitem context to find linked PRs, commits, branches, and repos. Fetch PRs only if the user asks for details, status, or next action.
使用工作项上下文查找关联的PR、提交记录、分支和仓库。仅当用户要求查看详细信息、状态或下一步操作时，才获取PR内容。

Repo Contributors / Hot Areas

仓库贡献者 / 热点区域

Query PRs/commits for the repo and time window. Group by files/areas, authors, reviewers, and themes. For hot areas, prioritize changed area plus frequency and ownership signals.
查询指定仓库和时间段内的PR/提交记录。按文件/区域、作者、评审者和主题分组。对于热点区域，优先考虑变更区域、频率和归属权信号。

PR-Based Status Rollup

基于PR的状态汇总

Resolve org/team first, then collect PRs for members or repos in the time window. Group into themes and repos/services. Call out gaps where PR-only evidence omits Jira, docs, planning, or customer context. For a single person where the prompt is broader than PRs, switch to 
twg-status-rollups
and load 
../twg-status-rollups/references/personal-work-summary.md
.
先解析组织/团队，再收集指定时间段内成员或仓库的PR。按主题和仓库/服务分组。指出仅基于PR的证据未涵盖Jira、文档、规划或客户上下文的缺口。 若用户的请求针对单个人员且范围超出PR，请切换至
twg-status-rollups
并加载
../twg-status-rollups/references/personal-work-summary.md
。

Output Shape

输出格式

For queues, include PR, repo, owner, state, reason, next action, and evidence. For engineering reports, summarize workstreams, contributors, bottlenecks, risks, and gaps. Include stable URLs or IDs for key artifacts.
对于队列，需包含PR、仓库、所有者、状态、原因、下一步操作及证据。 对于工程报告，汇总工作流、贡献者、瓶颈、风险和缺口。包含关键工件的稳定URL或ID。

Anti-Patterns

反模式

  • Do not guess Bitbucket workspace or repo.
  • Do not fetch every PR body, diff, or comment in a large queue.
  • Do not treat PR counts as impact.
  • Do not mix Bitbucket, GitHub connector/tool, and Atlassian auth failures.
  • 切勿猜测Bitbucket工作区或仓库。
  • 切勿获取大型队列中每个PR的正文、差异或评论。
  • 切勿将PR数量等同于影响力。
  • 切勿混淆Bitbucket、GitHub连接器/工具和Atlassian的身份验证失败情况。