360 Secure SkillHub
360 安全技能中心

Task Review Workflow

面向任务驱动开发的 PR 评审与合并标准流程:先读取 PR 与关联任务确认验收标准,按检查清单逐文件审查差异、在本地运行测试/静态检查/构建,输出可执行的评审意见,再决定合并或打回修改;合并后更新 Trello 卡片、删除任务分支并保留 main 分支,最后向编程智能体回传结果。

anikgnr
anikgnr
热度 79.85
最近更新 2026-05-17 12:09:32
分类:开发依赖:读写文件 / 代码执行 / 第三方 API应用场景:代码审查 / 工作流 / 任务管理 / DevOps

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add task-review-workflow
Metadata
name
task-review-workflow
description
Standard PR review and merge workflow for task-driven development. Use when reviewing a programmer agent PR linked to a task, deciding merge vs change request, handling post-merge actions (Trello + branch cleanup), and sending a clear outcome handoff.

Task Review Workflow

Follow this workflow in order for every task-linked PR.

1) Gather Context

  • Read the PR description.
  • Open and read the linked task before reviewing code.
  • Confirm expected behavior and acceptance criteria from the task context.

2) Review Against Standard

  • Use REVIEW_CHECKLIST.md as the mandatory review baseline.
  • Check correctness, edge cases, regressions, security, performance, and test adequacy.

3) Review the Diff Thoroughly

  • Review file-by-file.
  • Flag logic flaws, unsafe assumptions, missing validation, unclear naming, dead code, and side-effect risks.

4) Validate Locally When Possible

  • Check out the PR branch.
  • Run relevant test/lint/build commands.
  • Exercise changed behavior directly where practical.

5) Write Clear Review Feedback

  • Leave actionable, specific CR comments.
  • Separate must-fix issues from optional suggestions.

6) Decide Outcome

  • If issues remain: request changes with a concrete fix list.
  • If quality is acceptable: approve/merge with a short merge note.

7) Execute Post-Merge Steps

  • Move the related Trello card to Done.
  • Delete the task branch after merge.
  • Never delete the main branch.

8) Complete Handoff

  • Send the final outcome back to the programmer agent:
    • merged, or
    • CR sent, or
    • waiting for fixes.
  • Ensure the next task starts only after this outcome message.