Index of every page on this site: llms.txt
All skills
bitwarden avatar

/posting-bitwarden-review-comments

@a11c77b official
by bitwardenbitwarden/ai-plugins165 stars
27
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/bitwarden/ai-plugins/posting-bitwarden-review-comments

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈108 tokens for metadata: the name and description. ≈1.4k when used: this file.

Description uses 5.4% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈434 characters, or 5.4%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Posting Bitwarden Review Comments

Destination Detection

Check destinations in this order — use the first match:

Destination How to Detect Action
Local output in effect An 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 available Write 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 destination The review target is local changes and no caller declared a GitHub destination Write 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 request Neither of the above Post 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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

2 warnings10d4 checks · Risk SAFE
  • Gen Agent Trust Hub10d

    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.

  • Socket10d

    No alerts

  • Snyk10d

    Risk: MEDIUM · 1 issue

  • Runlayer9mo

    1/1 file flagged

Signed by skilld at a11c77b. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 weeks ago
  • github
  • code-review
  • bitwarden
  • pull-requests
  • comments
  • inline-comments
  • engineering-standards

README badge

README badge for bitwarden/ai-plugins/posting-bitwarden-review-comments

Formats inline code review comments for GitHub pull requests using Bitwarden's engineering standards, including severity emojis, finding numbering, and actionable fixes. Use this skill after classifying review findings and ready to post line-specific comments (not summary-level feedback).

Generated from the current SKILL.md.

When should I use this skill versus the summary skill?
Use this skill for inline comments on specific code lines following Bitwarden standards. Use the posting-review-summary skill for PR-level summary comments, metadata issues (title, description), and overall findings.
What format should I use for finding numbers?
Use 'Finding 1', 'Finding 2', etc. with a space and no # symbol. The # prefix causes GitHub to autolink to unrelated issues or PRs.
Can I post praise or positive observations as inline comments?
No. Praise-only inline comments and 'Strengths' or 'Highlights' sections are forbidden. Post only findings with actionable issues or risks.
How should I format inline comments longer than 5 lines?
Use a collapsed `<details>` section with the severity emoji and one-line description visible, and the full explanation, code examples, and rationale hidden inside the details tags.
What information must every inline comment include?
Each inline comment must reference specific line(s), state the problem and its risk, provide an actionable fix for severity levels that require one, and be brief yet clear.

Generated from the current SKILL.md. These answers refresh after source changes.