address review
- Repo stars 0
- Author repo skills-registry
- Domain
- Engineering
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
Run `git branch --show-current` to get the current branch. Derive the feature folder: Strip the `feat/` prefix from the branch name. Extract the first path segment (everything before the second `/`) — this is the feature slug. Feature folder = `spec/features/[slug]/`
Use `gh api repos/{owner}/{repo}/pulls/{number}/comments` to get all review comments. Filter for unresolved/pending comments (not yet resolved by the author). Group comments by category: Code Comments General code review feedback — bugs, style, logic issues, suggestions.
For each unresolved code comment: Read the referenced file and line range. Understand the reviewer's concern. Fix the code to address the concern. If the fix requires test changes, update tests and ensure they pass.
Read `SPEC-PROPOSAL.md` from the feature folder (if it exists). For Approved Proposals Read the proposal entry (e.g. SP-001). Apply the proposed change to the actual spec file (e.g. update `REQUIREMENTS.md`, `ADR.md`, or `DESIGN.md` in the feature folder). Remove the approved entry from `SPEC-PROPOSAL.md`.
Run the full test suite (or at minimum, tests related to the changes) to ensure everything passes after the fixes.
Stage all modified files. Commit with message: `fix(NNNN-slug): address review comments for {ISSUE-ID}` Push to the current branch.
Present a summary: Number of comments addressed Code changes made Spec proposals approved/rejected and files updated Whether SPEC-PROPOSAL.md was cleaned up
# Address Review
This skill pulls unresolved review comments from the current branch's PR and addresses them. It handles code changes, spec proposal approvals, and pushes fixes.
## Process
### Step 1: Identify the PR and Feature Folder
1. Run `git branch --show-current` to get the current branch.
2. Derive the feature folder:
- Strip the `feat/` prefix from the branch name.
- Extract the first path segment (everything before the second `/`) — this is the feature slug.
- Feature folder = `spec/features/[slug]/`
- Example: `feat/0023-payment-retry/eng-123-retry-endpoint` → `spec/features/0023-payment-retry/`
- Example: `feat/0023-payment-retry` → `spec/features/0023-payment-retry/`
3. Use `gh pr view --json number,url,headRefName` to find the open PR for this branch.
4. If no PR is found, fail with a clear message.
### Step 2: Pull Unresolved Comments
1. Use `gh api repos/{owner}/{repo}/pulls/{number}/comments` to get all review comments.
2. Filter for unresolved/pending comments (not yet resolved by the author).
3. Group comments by category:
#### Code Comments
General code review feedback — bugs, style, logic issues, suggestions.
#### Spec Proposal Comments
Comments that reference SPEC-PROPOSAL.md entries. Look for patterns like:
- "SPEC-PROPOSAL: approved" or "SP-001: approved" — reviewer approves the proposal
- "SPEC-PROPOSAL: rejected" or "SP-001: rejected" — reviewer rejects the proposal
- Other comments on SPEC-PROPOSAL.md lines
### Step 3: Address Code Comments
For each unresolved code comment:
1. Read the referenced file and line range.
2. Understand the reviewer's concern.
3. Fix the code to address the concern.
4. If the fix requires test changes, update tests and ensure they pass.
5. If the fix changes behavior covered by `spec://` references, verify the references are still correct.
### Step 4: Handle Spec Proposals
Read `SPEC-PROPOSAL.md` from the feature folder (if it exists).
#### For Approved Proposals
1. Read the proposal entry (e.g. SP-001).
2. Apply the proposed change to the actual spec file (e.g. update `REQUIREMENTS.md`, `ADR.md`, or `DESIGN.md` in the feature folder).
3. Remove the approved entry from `SPEC-PROPOSAL.md`.
#### For Rejected Proposals
1. Read the rejection reason from the review comment.
2. Revert any code that was written assuming the proposed spec change.
3. Adjust the implementation to work within the existing spec.
4. Remove the rejected entry from `SPEC-PROPOSAL.md`.
5. Update tests if the behavior changed.
#### Cleanup
If all entries in `SPEC-PROPOSAL.md` are resolved (approved or rejected), delete the file entirely.
### Step 5: Run Tests
Run the full test suite (or at minimum, tests related to the changes) to ensure everything passes after the fixes.
### Step 6: Commit and Push
1. Stage all modified files.
2. Commit with message: `fix(NNNN-slug): address review comments for {ISSUE-ID}`
3. Push to the current branch.
### Step 7: Report
Present a summary:
- Number of comments addressed
- Code changes made
- Spec proposals approved/rejected and files updated
- Whether SPEC-PROPOSAL.md was cleaned up
- Test results
- Suggest running `/address-review` again after the next review cycle
- If all comments are resolved and PR is approved, remind the user to merge the PR manually
---
> Source: [aqaliarept/sdd](https://github.com/aqaliarept/sdd) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-22 -->
Listed in source order.
sections -> Process → Step 1: Identify the PR and Feature Folder → Step 2: Pull Unresolved Comments → Step 3: Address Code Comments → Step 4: Handle Spec Proposals → Step 5: Run Tests
terms -> This skill pulls unresolved review comments from the current branch's PR and addresses them. · 1. Run git branch --show-current to get the current branch. · 1. Use gh api repos/{owner}/{repo}/pulls/{number}/comments to get all review comments. · 1. Read the referenced file and line range. · Read SPEC-PROPOSAL.md from the feature folder (if it exists). · 1. Read the proposal entry (e.g. · 1. Read the rejection reason from the review comment. · If all entries in SPEC-PROPOSAL.md are resolved (approved or rejected), delete the file entirely.
files/cmd -> git branch --show-current · feat/ · spec/features/[slug]/ · feat/0023-payment-retry/eng-123-retry-endpoint · spec/features/0023-payment-retry/ · feat/0023-payment-retry · gh pr view --json number,url,headRefName · gh api repos/{owner}/{repo}/pulls/{number}/comments
body sha256 -> 4f4481b2a324
Step 1: Identify the PR and Feature Folder
Run
git branch --show-currentto get the current branch. Derive the feature folder: Strip thefeat/prefix from the branch name. Extract the first path segment (everything before the second/) — this is the feature slug. Feature folder =spec/features/[slug]/Step 2: Pull Unresolved Comments
Use
gh api repos/{owner}/{repo}/pulls/{number}/commentsto get all review comments. Filter for unresolved/pending comments (not yet resolved by the author). Group comments by category: Code Comments General code review feedback — bugs, style, logic issues, suggestions.Step 3: Address Code Comments
For each unresolved code comment: Read the referenced file and line range. Understand the reviewer's concern. Fix the code to address the concern. If the fix requires test changes, update tests and ensure they pass.
Step 4: Handle Spec Proposals
Read
SPEC-PROPOSAL.mdfrom the feature folder (if it exists). For Approved Proposals Read the proposal entry (e.g. SP-001). Apply the proposed change to the actual spec file (e.g. updateREQUIREMENTS.md,ADR.md, orDESIGN.mdin the feature folder). Remove the approved entry fromSPEC-PROPOSAL.md.Step 5: Run Tests
Run the full test suite (or at minimum, tests related to the changes) to ensure everything passes after the fixes.