AGENT SKILL

tb-requesting-code-review

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

License 许可
Apache-2.0
最近更新
2026-10-06
Stars
★ 0
Forks
0

01 前言 Front Matter

name
tb-requesting-code-review
description
Use when completing tasks, implementing major features, or before merging to verify work meets requirements

02 资源文件 2

03 SKILL.md 正文

Requesting Code Review

Dispatch a code reviewer subagent to catch issues before they cascade. The reviewer gets precisely crafted context for evaluation — never your session's history. This keeps the reviewer focused on the work product, not your thought process, and preserves your own context for continued work.

Core principle: Review early, review often.

When to Request Review

Mandatory:

  • After each task in subagent-driven development
  • After completing major feature
  • Before merge to main

Optional but valuable:

  • When stuck (fresh perspective)
  • Before refactoring (baseline check)
  • After fixing complex bug

How to Request

1. Get git SHAs:

BASE_SHA=$(git rev-parse HEAD~1)  # or origin/main
HEAD_SHA=$(git rev-parse HEAD)

2. Dispatch code reviewer subagent:

Dispatch a general-purpose subagent, filling the template at code-reviewer.md

Placeholders:

  • {DESCRIPTION} - Brief summary of what you built
  • {PLAN_OR_REQUIREMENTS} - What it should do
  • {BASE_SHA} - Starting commit
  • {HEAD_SHA} - Ending commit

3. Act on feedback:

  • Fix Critical issues immediately
  • Fix Important issues before proceeding
  • Note Minor issues for later
  • Push back if reviewer is wrong (with reasoning)

Example

[Just completed Task 2: Add verification function]

You: Let me request code review before proceeding.

BASE_SHA=$(git log --oneline | grep "Task 1" | head -1 | awk '{print $1}')
HEAD_SHA=$(git rev-parse HEAD)

[Dispatch code reviewer subagent]
  DESCRIPTION: Added verifyIndex() and repairIndex() with 4 issue types
  PLAN_OR_REQUIREMENTS: Task 2 from docs/plan/<date>-deployment-plan.html
  BASE_SHA: a7981ec
  HEAD_SHA: 3df7661

[Subagent returns]:
  Strengths: Clean architecture, real tests
  Issues:
    Important: Missing progress indicators
    Minor: Magic number (100) for reporting interval
  Assessment: Ready to proceed

You: [Fix progress indicators]
[Continue to Task 3]

Integration with Workflows

Subagent-Driven Development:

  • Review after EACH task
  • Catch issues before they compound
  • Fix before moving to next task

Executing Plans:

  • Review after each task or at natural checkpoints
  • Get feedback, apply, continue

Ad-Hoc Development:

  • Review before merge
  • Review when stuck

Red Flags

Never:

  • Skip review because "it's simple"
  • Ignore Critical issues
  • Proceed with unfixed Important issues
  • Argue with valid technical feedback

If reviewer wrong:

  • Push back with technical reasoning
  • Show code/tests that prove it works
  • Request clarification

See template at: code-reviewer.md

04 同仓库更多 Skills

kongnakornna
kongnakornna/golangapi

tb-writing-plans

Use when you have a spec or requirements for a multi-step task, before touching code

★ 0
kongnakornna
kongnakornna/golangapi

tb-using-git-worktrees

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

★ 0
kongnakornna
kongnakornna/golangapi

tb-test-driven-development

Use when implementing any feature or bugfix, before writing implementation code

★ 0
kongnakornna
kongnakornna/golangapi

tb-subagent-driven-development

Use when executing implementation plans with independent tasks in the current session

★ 0
kongnakornna
kongnakornna/golangapi

tb-scrutinize

Outsider-perspective end-to-end review of a plan, PR, or code change. First questions intent and whether a simpler/more elegant approach would achieve the same goal, then traces the actual code path (not just the diff) to verify the change does what it claims. Output is concise, actionable, and every call carries its rationale. Trigger on /tb-scrutinize and proactively whenever the user asks to review, audit, sanity-check, or get a second opinion on a plan, PR, diff, design doc, or proposed code change.

★ 0
kongnakornna
kongnakornna/golangapi

tb-read-jira

Use this whenever a message contains an "RTRED-" key (e.g. RTRED-2612), a digital-and-technology.atlassian.net link, or a bare issue number, AND the user wants to know what it says — reading, opening, summarizing, checking the assignee/status, or pulling the background story or acceptance criteria. This is the default skill for any "what is this card/link about", "read/อ่าน/เปิด/ดึงข้อมูล/สรุป RTRED-xxxx", "ลิงก์นี้เกี่ยวกับอะไร", or "assign ให้ใคร" request, even when the words "Jira" or "ticket" never appear. The user's intent is simply to understand the contents of one of these issues; that is enough to trigger. Skip only when the user wants to create, edit, update, or change the status of an issue, when the link points to a different Atlassian site, or for Trello boards and local files.

★ 0