Skip to content

Instantly share code, notes, and snippets.

@wezoalves
Forked from vedovelli/10-process-review.md
Created March 5, 2026 09:29
Show Gist options
  • Select an option

  • Save wezoalves/d8993aebdc560cc5e86ab20683866c6f to your computer and use it in GitHub Desktop.

Select an option

Save wezoalves/d8993aebdc560cc5e86ab20683866c6f to your computer and use it in GitHub Desktop.
nanoclaw devteam: 10-process-review

process-review

Função: processReview — agente: senior ou junior (cross-review)

Review PR #{{pr}} on repo {{DEVTEAM_UPSTREAM_REPO}}.

Steps:
1. Read the PR: gh pr view {{pr}} --repo {{DEVTEAM_UPSTREAM_REPO}}
2. Read the diff: gh pr diff {{pr}} --repo {{DEVTEAM_UPSTREAM_REPO}}
3. Read any existing review comments: gh api repos/{{DEVTEAM_UPSTREAM_REPO}}/pulls/{{pr}}/comments

Write a substantive code review. Comment on:
- Code quality and patterns
- TypeScript types usage
- Component structure
- Potential bugs or edge cases
- Performance considerations

[IF shouldApprove]
After your review, APPROVE the PR: gh pr review {{pr}} --repo {{DEVTEAM_UPSTREAM_REPO}} --approve --body "..."
[ELSE]
After your review, REQUEST CHANGES: gh pr review {{pr}} --repo {{DEVTEAM_UPSTREAM_REPO}} --request-changes --body "..."
[END IF]

Also leave 1-3 inline comments on specific lines using:
gh api repos/{{DEVTEAM_UPSTREAM_REPO}}/pulls/{{pr}}/comments -f body="..." -f commit_id="..." -f path="..." -F line=N

Finally, post a comment on Linear planning issue {{planning_issue}} with your review outcome:
- PR #{{pr}} reviewing Linear issue {{issue}}
- Whether you approved or requested changes
Use the Linear MCP create_comment tool on issue {{planning_issue}}.

Output: REVIEW_RESULT=approved   (or REVIEW_RESULT=changes_requested)

Nota: shouldApprove é determinado pelo orchestrator com base em review_round e probabilidade (round 1: 20%, round 2: 70%, round 3+: 100%).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment