addressing-code-review-comments
Addressing Code Review Comments
You are working alongside the user to address review comments on their pull request. Reviewer feedback flows to you; you present analysis, fixes, and draft replies back to the user. The user decides what gets implemented and what gets posted.
Core principle: Verify before implementing. Surface ambiguity before assuming. Technical correctness over social comfort.
Workflow
For each review:
- Read the full set of comments before reacting to any single one.
- Restate each comment's technical requirement in your own words.
- Verify the claim against the actual codebase.
- Evaluate whether it's sound for this codebase, given context the reviewer may lack.
- Present your read to the user — fix, pushback, or clarification needed — and ask about anything ambiguous before touching code.
- Implement confirmed items one at a time, test each, and report what changed.
If a comment is unclear, stop and ask the user before touching anything. Comments often relate to each other, and partial understanding leads to half-fixes.
More from bitwarden/ai-plugins
avoiding-false-positives
Use this skill to validate findings during a code review. For each finding, run the rejection criteria and verification checks. If a finding fails any check, drop it.
50retrospecting
Performs comprehensive analysis of Claude Code sessions, examining git history, conversation logs, code changes, and gathering user feedback to generate actionable retrospective reports with insights for continuous improvement.
49implementing-dapper-queries
Implementing Dapper repository methods and stored procedures for MSSQL at Bitwarden. Use when creating or modifying Dapper repositories, writing stored procedures, or working with MSSQL-specific data access in the server repo.
47classifying-review-findings
Use this skill when categorizing code review findings into severity levels. Apply when determining which emoji and label to use for PR comments, deciding if an issue should be flagged at all, or classifying findings as CRITICAL, IMPORTANT, DEBT, SUGGESTED, or QUESTION.
46posting-review-summary
Use this skill when posting the final summary comment after all inline comments are posted. Apply as the LAST step of code review after all findings are classified and inline comments are complete. Detects context (agent mode sticky comment, GitHub Actions MCP tool, or local file) and routes output accordingly.
44reviewing-claude-config
Reviews Claude configuration files for security, structure, and prompt engineering quality. Use when reviewing changes to CLAUDE.md files (project-level or .claude/), skills (SKILL.md), agents, prompts, commands, or settings. Validates YAML frontmatter, progressive disclosure patterns, token efficiency, and security best practices. Detects critical issues like committed settings.local.json, hardcoded secrets, malformed YAML, broken file references, oversized skill files, and insecure agent tool access.
44