Git and Commit Guidelines

SkillDev tools

Conventional Commits format, commit types, scopes, and PR best practices for Trezor Suite. Use when committing code or creating pull requests.

Available today. Use it from your connected AI after setup.

No other account needed.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Git and Commit Guidelines skill

What this skill tells your AI

The instructions your AI receives, as published by trezor/trezor-suite in skills/git-and-commit-guidelines/SKILL.md and read by ahel’s review.

IMPORTANT: This project uses Conventional Commits. All commits MUST follow this format:

<type>(<scope>): <description>

[optional body]

[optional footer]

feat: New feature (e.g., feat(suite): add transaction history export)
fix: Bug fix (e.g., fix(components): resolve modal z-index issue)
docs: Documentation changes (e.g., docs: update setup instructions)
refactor: Code refactoring without behavior change
test: Adding or updating tests
chore: Build process, dependencies, tooling (e.g., chore(deps): update eslint)

Common scopes: suite, suite-native, connect, components, analytics

Plan internally, commit only code: For complex tasks, use todo lists or internal planning, but only commit actual code changes with conventional commits
If you must commit intermediate work, use proper conventional commits (e.g., chore: work in progress on feature X) and be prepared to squash before final push
Write clear, concise commit messages describing the actual change
One logical change per commit when possible
Reference issue numbers in commit body when applicable (e.g., Closes #1234)
Avoid committing plan documents or TODO files unless they are part of the project documentation

Advanced