chore(ci): enable sticky comments and progress tracking in Claude Code review action

[fshowalter]

No description provided.

[claude]

Claude finished @fshowalter's task in 2m 10s —— View job

---

Code Review Complete ✓

Summary

This PR enhances the Claude Code review workflow by enabling two important features:

• Sticky comments (use_sticky_comment: true) - Makes Claude reuse the same comment across multiple pushes to a PR
• Progress tracking (track_progress: true) - Provides better visibility into Claude's review progress

---

Review Findings

✅ Code Quality & Best Practices

Excellent. The changes follow GitHub Actions YAML best practices:

• Clear, descriptive inline comments explain each configuration option
• Consistent formatting and indentation
• Well-organized with logical grouping of related options
• Comprehensive commented examples for future customization

✅ Potential Bugs or Issues

None identified. The configuration changes are:

• Syntactically correct YAML
• Using valid boolean values (true)
• Properly indented within the with: block
• Both options are documented features of the anthropics/claude-code-action@v1 action

✅ Performance Considerations

Positive impact. These changes improve efficiency:

• use_sticky_comment: true reduces comment clutter by reusing the same comment instead of creating new ones on each push
• track_progress: true provides real-time feedback, improving user experience without adding overhead
• No negative performance implications

✅ Security Concerns

None. The changes:

• Don't introduce new secret handling
• Don't modify permissions
• Don't change authentication mechanisms
• Both features are safe, UI-focused enhancements

⚠️ Test Coverage

Not applicable. This is a CI/CD workflow configuration file. While it cannot be unit tested directly, I recommend:

1. Monitor the first few PR reviews to ensure sticky comments work as expected
2. Verify that progress tracking displays correctly during reviews
3. Consider documenting the expected behavior in your team's workflow documentation

---

Additional Observations

Well-documented for future maintainers:
The workflow file includes excellent commented examples (.github/workflows/claude-code-review.yml:57-79) showing:

• Custom model selection
• Tool permissions via claude_args
• File-type-specific review prompts
• Conditional reviews based on PR metadata

Recommendation: Consider uncommenting and customizing the claude_args section (lines 58-61) to leverage the project-specific tools defined in CLAUDE.md:

claude_args: |
  --allowedTools Edit,Read,Write,Bash(uv run pytest),Bash(uv run ruff check .),Bash(uv run mypy .)

This would enable Claude to run your linters and tests during reviews, providing more comprehensive feedback.

---

Conclusion

Status: ✅ Approved

This is a clean, focused enhancement that improves the user experience of the Claude Code review workflow. The changes are well-implemented with no identified issues. The PR accomplishes exactly what the title promises: enabling sticky comments and progress tracking.

---