skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
bitwarden/ai-plugins94 installs

posting-bitwarden-review-comments

Use this skill when emitting inline review comments, whether posted to a GitHub pull request or written to a local file under caller-declared local-file output. Apply when formatting comments following Bitwarden engineering standards with severity emojis, clear explanations, and actionable suggestions. Use after findings are classified and ready to emit. DO NOT USE when posting summary comments.

How do I install this agent skill?

npx skills add https://github.com/bitwarden/ai-plugins --skill posting-bitwarden-review-comments
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill provides instructions for formatting and posting code review findings following Bitwarden's engineering standards. It manages output destinations between GitHub and local files and includes rules to prevent accidental platform-specific behaviors like GitHub autolinking.

  • Socketpass

    No alerts

  • Snykwarn

    Risk: MEDIUM · 1 issue

  • Runlayerwarn

    1/1 file flagged

What does this agent skill do?

Posting Bitwarden Review Comments

Destination Detection

Check destinations in this order — use the first match:

DestinationHow to DetectAction
Local output in effectAn OUTPUT: local files line in the prompt's leading directive block, or a caller that passes local files as the destination in effect. Check this first, and never key it on which tools happen to be availableWrite to the inline-comments path the caller passed. With no path, pick none: return the formatted findings in your reply and say no destination was given. bitwarden-code-reviewer resolves the directory and file name in its Step 1 and passes it on every invocation; this skill never picks either
Local target, no GitHub destinationThe review target is local changes and no caller declared a GitHub destinationWrite to the inline-comments path the caller passed. With no path, pick none: return the formatted findings in your reply and say no destination was given
GitHub pull requestNeither of the abovePost via mcp__github_inline_comment__create_inline_comment

Under either local destination, format every finding exactly as below, without the source line, and write them all to the one file, or return them in your reply when no path was passed — do not post, whatever comment tools happen to be available.

On a GitHub pull request, a finding raised again in an existing thread goes as a reply in that thread, so its history stays in one place. Call mcp__github_replies__add_reply_to_pull_request_comment with the database_id of the thread's first comment as commentId, the owner and repository from the threads data's top-level repository, and the pull request number as pullNumber, which the tool requires whenever a reply has a body. The reply uses the same finding format as an inline comment. When that tool is unavailable, the thread's first comment has no database_id, or the reply call fails, post a new inline comment instead.

Comment Posting Protocol

  1. MUST Analyze all changes before emitting anything
  2. MUST Use inline comments for code-specific findings
  3. MUST Use the Bitwarden finding format
  4. FORBIDDEN: Do NOT add "Strengths", "Highlights", or positive observations sections.
  5. FORBIDDEN Do NOT post praise-only inline comments
  6. FORBIDDEN: Do NOT post PR metadata issues (title, description, test plan) as inline comments. These go in the summary only.

Finding Format

CRITICAL: Never use # followed by numbers - GitHub will autolink it to unrelated issues/PRs.

  1. Writing "#1" creates a clickable link to issue/PR #1 (not your finding)
  2. "Issue" is also wrong terminology (use "Finding")
  3. Use "Finding" + space + number (no # symbol); aim for under 30 words in sentence

CORRECT FORMAT:

  • Finding 1: Memory leak detected
  • Finding 2: Missing error handling

WRONG (DO NOT USE):

  • ❌ Issue #1 (wrong term + autolink)
  • ❌ #1 (autolink only)
  • ❌ Issue 1 (wrong term only)

Inline Comments

Every inline comment MUST:

  1. Reference specific line(s)
  2. State the problem - what breaks or what's the risk?
  3. Provide actionable fix (for ❌ and ⚠️)
  4. Be brief yet clear
  5. Use collapsed sections for comments over 5 lines
  6. Include both opening <details> AND closing </details> tags
  7. On a GitHub pull request, end with the source line <sub>code-review</sub>, short comments and thread replies included

Visibility Rule: Only severity + one-line description and, on a GitHub pull request, the source line visible; everything else inside <details> tags.

Template for long comments

[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>

<sub>code-review</sub>

Summary Output

Invoke Skill(posting-review-summary) for all summary formatting and posting.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/bitwarden/ai-plugins/posting-bitwarden-review-comments">View posting-bitwarden-review-comments on skillZs</a>