mcpField
P
perform-preflight

perform-preflight

github.com/bitwardenTesting & quality16257 installsUpdated today
Repository

About perform-preflight

A pre-commit and pre-PR checklist skill for Bitwarden repositories. It covers tests, code quality, zero-knowledge security, and architecture, with repository-specific commands taken from CLAUDE.md.

Key features

  1. 01Checks tests for affected modules
  2. 02Verifies test coverage for new code
  3. 03Checks linting and formatting
  4. 04Reviews zero-knowledge security requirements
  5. 05Checks architecture and dependency patterns

Use cases

  1. 01Validate changes before committing
  2. 02Prepare changes before opening a PR
  3. 03Identify unresolved test, lint, security, or architecture issues

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/bitwarden/ai-plugins --skill perform-preflight

After installing, type/perform-preflightin Claude Code to confirm it loaded.

Details

From the project README

Preflight Checklist

Run this checklist before committing or creating a PR. Consult the repo's CLAUDE.md for platform-specific commands (test runner, linter, formatter).

Tests

  • Run tests for affected modules (consult CLAUDE.md for commands)
  • New code has test coverage
  • No existing tests broken

Code Quality

  • Lint and format pass (consult CLAUDE.md for commands)
  • No TODO comments without Jira ticket references
  • Public APIs documented per repo convention (KDoc, DocC, XML docs, etc.)

Bitwarden Security

  • Zero-knowledge architecture preserved — no unencrypted vault data logged, persisted, or transmitted
  • Sensitive data uses platform-appropriate secure storage (consult CLAUDE.md Security Rules)
  • No sensitive data in log statements

Architecture

  • Changes follow patterns in CLAUDE.md and architecture docs
  • Dependency injection and error handling follow repo convention
  • String resources added to the correct location (if applicable)

On Failure

If any check fails, fix the issue before proceeding. For test failures, diagnose the root cause rather than skipping. For lint/format failures, run the repo's auto-fix command if available. If a check cannot be resolved, flag it to the user with the specific failure output.

Comments

Markdown supported