
Perform Preflight
- 39 installs
- 129 repo stars
- Updated August 4, 2026
- bitwarden/ai-plugins
Perform-preflight is a Claude skill providing a quality-gate checklist for tests, lint, security, and architecture to run before committing or opening a PR.
About
This skill is a preflight quality-gate checklist to run before committing or creating a PR. It walks through tests, code quality (lint and format), Bitwarden zero-knowledge security checks, and architecture conformance, consulting the repo's CLAUDE.md for the exact commands. A developer uses it to self-review finished work before it goes into version control. On failure it directs the developer to fix the root cause rather than skip the check.
- Quality-gate checklist to run before committing or opening a PR
- Covers tests, lint and format, Bitwarden security, and architecture
- Consults the repo's CLAUDE.md for platform-specific commands
Perform Preflight by the numbers
- 39 all-time installs (skills.sh)
- Ranked #621 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
perform-preflight capabilities & compatibility
- Capabilities
- code review · testing
- Use cases
- code review · testing
What perform-preflight says it does
Quality gate checklist to run before committing or creating a PR.
Zero-knowledge architecture preserved — no unencrypted vault data logged, persisted, or transmitted
For test failures, diagnose the root cause rather than skipping.
npx skills add https://github.com/bitwarden/ai-plugins --skill perform-preflightAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 39 |
|---|---|
| repo stars | ★ 129 |
| Last updated | August 4, 2026 |
| Repository | bitwarden/ai-plugins ↗ |
What it does
Run a preflight quality gate covering tests, lint, security, and architecture before committing or opening a PR.
Who is it for?
Self-reviewing finished work against a quality gate before committing or opening a PR.
Skip if: Deep multi-pass code review of an existing PR (use a dedicated code-review skill).
When should I use this skill?
Finishing implementation and preparing to commit, or the user says 'preflight' or 'ready to commit'.
By the numbers
- 4-section checklist: Tests, Code Quality, Bitwarden Security, Architecture
Files
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.