技能详情（站内镜像，无评论）
作者：Md. Mushraful Hoque Anik @anikgnr
许可证：MIT-0
MIT-0 ·免费使用、修改和重新分发。无需归因。
版本：v0.1.0
统计：⭐ 0 · 557 · 1 current installs · 1 all-time installs
⭐ 0
安装量（当前） 1
🛡 VirusTotal ：可疑 · OpenClaw ：良性
Package：anikgnr/task-review-workflow
安全扫描（ClawHub）
- VirusTotal ：可疑
- OpenClaw ：良性
OpenClaw 评估
An instruction-only PR review workflow that is internally coherent for its stated purpose, but it references external artifacts (a REVIEW_CHECKLIST and Trello actions) without declaring how those will be accessed.
目的
The name/description match the instructions: the SKILL.md describes how to review PRs, decide outcomes, perform merge-time housekeeping, and hand off results. All requested actions (review diffs, run tests, delete branches, move task cards) are consistent with a review workflow. Minor mismatch: the workflow expects a REVIEW_CHECKLIST.md and Trello post-merge steps but the skill does not include or declare those resources.
说明范围
Instructions are narrowly scoped to PR review tasks (read PR and linked task, run tests, leave comments, merge or request changes, post-merge cleanup). They reference checking out branches, running tests/lints, reading REVIEW_CHECKLIST.md, and moving a Trello card — all reasonable for this workflow but they implicitly require repository and Trello access that the skill does not describe.
安装机制
No install spec and no code files — lowest-risk instruction-only skill. Nothing will be written to disk by an installer provided by this skill.
证书
The SKILL.md calls for actions that may require credentials (git write/merge rights, and Trello API or UI access to move cards). The skill declares no required environment variables or credentials; this is not harmful but users should be aware additional credentials or separate skills will be needed for automated branch deletion and Trello updates.
持久
always:false and no install or persistent config changes. The skill does not request elevated platform privileges or permanent presence.
综合结论
This skill is an instruction-only PR review checklist and looks coherent, but before installing consider: (1) Ensure the agent/environment that will run this skill actually has repository access and the right to check out branches, run tests, and perform merges — grant the minimum necessary permissions. (2) The workflow references a REVIEW_CHECKLIST.md that isn't included; make sure that file exists in your repo or provide the checklist. (3) P…
安装（复制给龙虾 AI）
将下方整段复制到龙虾中文库对话中，由龙虾按 SKILL.md 完成安装。
请把本段交给龙虾中文库（龙虾 AI）执行：为本机安装 OpenClaw 技能「Task Review Workflow」。简介：Standard PR review and merge workflow for task-driven development. Use when rev…。
请 fetch 以下地址读取 SKILL.md 并按文档完成安装：https://raw.githubusercontent.com/openclaw/skills/refs/heads/main/skills/anikgnr/task-review-workflow/SKILL.md
（来源：yingzhi8.cn 技能库）SKILL.md
---
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.