code-review

name	code-review
description	Code review a pull request. Usage: /code-review <PR number>

Code Review — lambda-boss

Review a PR for code quality and adherence to spec/plan.

Arguments

• /code-review <PR number> — Review the specified pull request

Instructions

1. Read the PR: gh pr view <number> -R TagloGit/lambda-boss --json title,body,url
2. Find the linked issue from the PR body (look for "Closes #N")
3. Read the issue: gh issue view <number> -R TagloGit/lambda-boss --json title,body
4. If the issue references a spec or plan, read those files
5. Review the diff: gh pr diff <number> -R TagloGit/lambda-boss
6. Assess:
   • Does the code match the plan?
   • Are there tests? Are they meaningful?
   • Does it follow the repo's coding conventions?
   • Any obvious bugs or edge cases?
7. Report findings

Output Format

PR Review: #N — [title]

Plan Compliance: [Good/Partial/Poor] — [brief note] Test Coverage: [Good/Partial/None] — [brief note] Code Quality: [observations] Issues Found: [list or "None"] Recommendation: [Approve / Request Changes / Needs Discussion]

Behaviour Notes

• Do NOT write code or make changes
• Do NOT merge PRs
• Be constructive — flag issues but also note what's done well

Self-Improvement

When you notice a recurring problem or workflow gap:

1. Create a process issue on TagloGit/taglo-pm describing the observation
2. Continue your current work