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.

Safety Notice

This listing is from the official public ClawHub registry. Review SKILL.md and referenced scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "task-review-workflow" with this command: npx skills add anikgnr/task-review-workflow

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 Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

Olares Market (olares-cli market)

olares-cli market command tree against the per-user Market app-store v2 API: list / get / categories for catalog browsing; install / uninstall / upgrade / cl...

Registry SourceRecently Updated
Coding

Mistral Mcp Openclaw

Configure OpenClaw to use the community mistral-mcp stdio server for Mistral OCR, Codestral FIM, Voxtral audio, durable workflows, moderation, classification...

Registry SourceRecently Updated
731swih
Coding

Web Design Lead Qualifier

Research and score prospective web design clients. Crawl their site, assess fit, and produce a qualification report. Use when asked to qualify a lead, resear...

Registry SourceRecently Updated
Coding

Olares Shared (olares-cli foundation)

Shared olares-cli foundation: profile model, first-time login (profile login with password + TOTP), bootstrapping a profile from an existing refresh token (p...

Registry SourceRecently Updated