Automatic Previous Review Comment Analysis - Major enhancement to track and verify reviewer feedback across patchsets.
- New section in SKILL.md to fetch previous review comments from Gerrit API
- Fetches all review messages, inline comments, and vote history
- Analyzes comments from all previous patchsets
New Python script that:
- Parses Gerrit review JSON data
- Extracts actionable issues from review messages
- Identifies patterns like "-1:", "please", "should", "needs", "missing"
- Categorizes comments by patchset
- Shows which reviewers commented and when
- Displays current review scores
- Highlights potential unaddressed issues from old patchsets
Added critical step in review workflow:
- Step 4: Verify Previous Feedback Has Been Addressed
- Check each comment from previous patchsets
- Verify fixes in current patchset
- Common unaddressed issues checklist
- Guidance on handling unresolved feedback
Updated report template to include:
- Patchset History: Current vs previous patchsets, review scores
- Previous Review Feedback: Summary of other reviewers' comments
- Issues Addressed: Which feedback has been handled
- Issues Unresolved: What still needs attention
- Response to Previous Feedback: Overall assessment
Added to reference.md:
- Checking Previous Review Comments section
- Why this matters
- How to check previous comments
- Common scenarios (tests requested, docs requested, security issues, refactoring)
- Red flags for unaddressed comments
- Example review comments for unaddressed feedback
This feature helps with:
- Avoiding duplicate reviews: See what others already found
- Tracking progress: Verify author addressed feedback
- Collaborative reviewing: Build on other reviewers' work
- Quality assurance: Ensure nothing slips through
- Reviewer accountability: Author must respond to all feedback
/openstack-review 970404
# Skill now:
# 1. Fetches review 970404
# 2. Downloads all review history
# 3. Shows previous comments: "Alice asked for tests in PS3"
# 4. Checks current code: "Tests are now present in PS9"
# 5. Verifies: ✓ Alice's feedback addressed
# 6. Continues with normal review
# 7. Reports: "All previous feedback addressed, code looks good +1"analyze_comments.py: Comment analysis script
SKILL.md: Added step 2 (Fetch Previous Review Comments) and step 4 (Verify Previous Feedback)reference.md: Added comprehensive section on checking previous commentsREADME.md: Updated features list and example workflowCHANGELOG.md: This file
Made the skill generic to work with all OpenStack projects, not just Octavia.
- Reads project name from
.gitreviewfile - Extracts Gerrit host from
.gitreview - Works with any OpenStack project (Nova, Neutron, Cinder, Keystone, etc.)
Before:
# Hardcoded to openstack/octavia
git fetch https://review.opendev.org/openstack/octavia refs/changes/...After:
# Reads from .gitreview
PROJECT=$(grep "^project=" .gitreview | cut -d= -f2 | sed 's/\.git$//')
GERRIT_HOST=$(grep "^host=" .gitreview | cut -d= -f2)
git fetch https://${GERRIT_HOST}/${PROJECT} refs/changes/...All references to specific Octavia paths changed to generic placeholders:
octavia/api/v2/→<project>/api/v2/or "check project's API structure"octavia/tests/unit/→<project>/tests/unit/octavia/db/models.py→<project>/db/models.pyor "check project structure"
Added notes about project variations:
- Coverage requirements (Octavia ≥92%, may vary)
- API validation methods (WSME, JSON Schema, etc.)
- Database patterns (repository pattern vs direct ORM)
- TaskFlow usage (not all projects use it)
✅ Fully backward compatible with Octavia
✅ Works with existing workflows
✅ Same skill invocation: /openstack-review <review-number>
Tested with:
- ✅ Octavia project (.gitreview:
openstack/octavia.git) - ✅ Script extracts project correctly
- ✅ Script extracts Gerrit host correctly
- ✅ Documentation is project-agnostic
No action needed - skill already works in .claude/skills/openstack-review/
To use across all OpenStack projects:
cp -r .claude/skills/openstack-review ~/.claude/skills/Then use from any OpenStack project directory:
cd ~/devel/nova
/openstack-review 123456
cd ~/devel/neutron
/openstack-review 789012Any OpenStack project with:
.gitreviewfile in repository root- Gerrit-based workflow
- Standard tox environments (py3, pep8, cover)
Examples:
- Nova (compute)
- Neutron (networking)
- Octavia (load balancer)
- Cinder (block storage)
- Keystone (identity)
- Glance (image)
- Heat (orchestration)
- And all other OpenStack projects!
- Octavia-specific code review skill
- Automated fetching from Gerrit
- Code quality checks
- Security analysis
- Test validation
- Comprehensive reporting