perform-security-review
Parameters
--output-dir <path>: When using --output file, write the report to <path>/security-review-YYYY-MM-DD-{identifier}.md instead of the current working directory. Tip: use --output-dir ~/.claude/security-reviews/ to keep reports outside git repos.
Security Review Mode
Determine review mode from the invocation:
- PR mode (PR number or URL):
gh pr view <number>for context,gh pr diff <number>for the diff. - Commit mode (commit SHA):
git diff <sha>..HEAD— reviews all changes after that commit. - Time-based mode (duration, e.g., "last 48 hours"): find the oldest commit in range with
git log --since="<duration>" --reverse --format=%H | head -1, thengit diff <sha>^..HEADto include it. - Local changes mode (no argument, pending changes exist):
git diff HEADfor staged + unstaged changes. - Branch comparison mode (no argument, no pending changes):
git diff main...HEAD— changes since the branch diverged from main.
Security Review Process
Model selection: If --model is specified, use that model for all agents. Otherwise, default to opus.
Execute these steps in order. Do not skip, reorder, or combine steps.
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