OpenClaw

task-review-workflow

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.

anikgnr0 来源安装数☆ 0 仓库 Stars

查看来源 ↗安装与使用 SKILL.md ↗

安装与使用

请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求，再添加到工作流。

SkillHub CLI

skillhub install anikgnr/task-review-workflow

打开来源仓库，查看说明和兼容环境后，按来源提供的命令或步骤安装。

将来源链接提供给你的 Agent，让它先读取说明、核对依赖，并向你说明将执行的安装步骤。

查看来源 ↗使用指南

技能说明

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.

来源信息

Source: github
Repository: openclaw/skills
Path: skills/anikgnr/task-review-workflow
Version: —
Commit: 87091cf48705d368713d7aa426a6c0c0a0697730
分类来源: rules
状态: active
可见性: public

这些信息来自收录时的来源分析，可能滞后；使用前请核对最新来源文件。

来源内容

SKILL.md

# 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.

搜索