Rechercher

PythonReactSEOPDF
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 installations selon la source☆ 0 Étoiles du dépôt

Installation

Suivez les instructions du dépôt pour votre agent. Consultez les fichiers et dépendances avant l’installation.

SkillHub CLI

skillhub install anikgnr/task-review-workflow

Examinez la source et la compatibilité, puis suivez les étapes d’installation.

Donnez le lien à votre agent et demandez-lui d’examiner instructions et dépendances avant d’expliquer les étapes.

Voir la source ↗Guides

Instructions

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.

Informations sur la source

Source
github
Repository
openclaw/skills
Path
skills/anikgnr/task-review-workflow
Version
—
Commit
87091cf48705d368713d7aa426a6c0c0a0697730
Source de classification
rules
Statut
active
Visibilité
public

Ces informations proviennent de l’analyse indexée et peuvent être anciennes. Vérifiez les fichiers actuels.

Contenu extrait

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.

Skills associés

OpenClaw

1password

daggerkun007

Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.