| name | git-workflow |
| description | Git workflow and commit conventions for Ledger Wallet |
Branches must use a clear prefix based on their purpose:
feat/add-ethereum-stakingbugfix/fix-transaction-signingsupport/update-dependenciesFollow the Conventional Commits standard.
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
desktop, mobile, coin, common, etc.)BREAKING CHANGE: ...LL-1234)feat(desktop): add dark mode toggle
fix(mobile): resolve transaction signing issue
docs(common): update API documentation
refactor(account): simplify account syncing logic
test(coin): add bitcoin integration tests
support/cleanup)
Create a pull request with proper description, changeset, and all required elements
Guided feature development with codebase understanding and architecture focus
Write unit and integration tests for Ledger Wallet apps. Use for Jest tests (Desktop/Mobile), MSW handlers and testing best practices. Applies to "*.test.*", "*.spec.*", "**/tests/**", "**/__tests__/**", "**/__integrations__/**", "**/jest-setup*"
Coin-specific families logic must live in families/. Generic UI uses the families contract only (no if (family === "evm") in shared code). Use this guidance for work in "**/families/**", "**/mvvm/**", "**/renderer/**" and "**/screens/**".
Prefer Set.has() over Array.includes() for constant allowlists/blocklists. Read this when reviewing or writing membership checks in TypeScript files.
Maintain CODEOWNERS file and team specific directories. Use when working with "**/team-*/**" file structure or to split an old file into team-specific parts