# Paw Review Response

> Shared PR review comment response mechanics for PAW activity skills. Provides TODO workflow, commit patterns, and reply format for addressing reviewer feedback. Use when this capability is needed.

- Skill: `tomevault-io/paw-review-response` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/paw-review-response`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/paw-review-response/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/paw-review-response

---


# Review Response

## Review Comment Workflow

### 1. Read All Unresolved Comments

- Use GitHub MCP tools to fetch PR comments and conversation threads
- Identify which comments still require work:
  - Check for follow-up commits addressing the comment
  - Check for reviewer replies indicating resolution
  - Skip comments clearly already addressed
- If uncertain whether a comment needs work, include it and ask for clarification

### 2. Create TODOs for Comments

Create one TODO per comment (group small related comments together):

```
TODO: Address review comment [link/ID]
- What change is needed
- Which file(s) to modify
- Commit message reference
```

**Grouping guidelines:**
- Group comments affecting the same file or section
- Group comments addressing the same concern
- Keep complex comments as separate TODOs
- Each TODO = one focused commit

### 3. Address Comments Sequentially

Work through TODOs one at a time. For each:

1. **Make the changes** to address the comment
2. Follow `paw-git-operations` artifact staging discipline — check artifact lifecycle mode before staging `.paw/` files
3. **Stage selectively**: `git add <file1> <file2>` (never `git add .`)
4. **Verify staged changes**: `git diff --cached`
5. **Commit** with message referencing the comment
6. **Push/Reply timing**: Determined by calling activity skill—some push immediately per-comment, others batch commits and defer push to a verification step

**CRITICAL**: Complete each TODO's changes and commit before starting the next. Push and reply timing per activity skill instructions.

### 4. Verify Completion

- Ensure all review comments have been addressed
- Verify no open questions remain
- Run any applicable verification (tests, linting)

## Reply Format

Use this format when replying to review comments:

```
**🐾 [Activity] 🤖:**

[What was changed and commit hash reference]
```

**Activity names by PR type:**
- Planning PR: `Implementation Planner`
- Phase PR: `Implementation Reviewer`
- Docs PR: `Documenter`
- Final PR: `Implementation Reviewer`

**Examples:**

```
**🐾 Implementation Planner 🤖:**

Updated Phase 2 to include error handling tests as suggested. See commit abc1234.
```

```
**🐾 Implementation Reviewer 🤖:**

Added the missing null check and updated the docstring. Commit def5678.
```

## Commit Message Format

Reference the review comment in commit messages:

```
Address review comment: [brief description]

[More detail if needed]

Ref: [PR comment URL or ID]
```

## Role Separation

This utility skill handles **mechanics** (how to commit/push/reply). Activity skills handle **domain logic** (what changes to make).

| Responsibility | Handled By |
|---------------|------------|
| What to change | Activity skill |
| How to commit | This utility skill |
| How to reply | This utility skill |
| When to push | Activity skill (based on workflow) |

## Checklist Before Completion

- [ ] All unresolved review comments addressed
- [ ] Each comment addressed with focused commit
- [ ] Commits pushed to remote
- [ ] Replies posted to each addressed comment
- [ ] Verification passed (tests, lint)

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/lossyrob) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-11 -->