Use this skill when posting inline comments to GitHub pull requests. Apply when formatting comments following Bitwarden engineering standards with severity emojis, clear explanations, and actionable suggestions. Use after findings are classified and ready to post. DO NOT USE when posting summary comments.
How this skill is triggered — by the user, by Claude, or both
Slash command
/bitwarden-code-review:posting-bitwarden-review-commentsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. **MUST** Analyze all changes before posting anything
CRITICAL: Never use # followed by numbers - GitHub will autolink it to unrelated issues/PRs.
CORRECT FORMAT:
WRONG (DO NOT USE):
Every inline comment MUST:
<details> AND closing </details> tagsVisibility Rule: Only severity + one-line description visible; everything else inside <details> tags.
[emoji] **[SEVERITY]**: [One-line issue description]
<details>
<summary>Details and fix</summary>
[Code example or specific fix]
[Rationale explaining why]
Reference: [docs link if applicable]
</details>
Invoke Skill(posting-review-summary) for all summary formatting and posting.
npx claudepluginhub bitwarden/ai-plugins --plugin bitwarden-code-reviewPosts code review findings as line-bound PR comments via the GitHub CLI. Maps issues to specific lines and supports severity filtering.
Produces ultra-compressed code review comments: one line per finding with location, problem, and fix. Cuts noise while preserving actionable signal.
Generates well-structured code review comments in Conventional Comments format for clear, actionable PR feedback. Classifies as praise/nitpick/suggestion/issue/question/thought with blocking/non-blocking decorations.