Perform Preflight

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

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

Code Quality

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

Bitwarden Security

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

Architecture

• Not done: Changes follow patterns in CLAUDE.md and architecture docs
• Not done: Dependency injection and error handling follow repo convention
• Not done: 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.