// Generate a CHANGELOG entry line for a pull request from code changes. Use when the user asks to write a changelog entry, fill the changelog section of a PR, or determine if changes are user-facing.
| name | pr-changelog |
| description | Generate a CHANGELOG entry line for a pull request from code changes. Use when the user asks to write a changelog entry, fill the changelog section of a PR, or determine if changes are user-facing. |
CHANGELOG entry: <past-tense summary>
or
CHANGELOG entry: null
User-facing change? (new feature, bug fix, UI change, behavior change visible to end users)
Added..., Fixed..., Updated..., Removed...null (refactors, tests, CI, internal tooling, dev-only changes).github/scripts/check-template-and-add-labels.ts)CHANGELOG entry: followed by a non-empty value (leading whitespace is tolerated by CI)no-changelog label skips the check entirelygit diff main...HEADnullUser-facing:
CHANGELOG entry: Added dark mode toggle to settings screen
CHANGELOG entry: Fixed token balance not updating after swap
CHANGELOG entry: Updated network selector to show custom networks first
CHANGELOG entry: Removed deprecated fiat on-ramp provider
Not user-facing:
CHANGELOG entry: null
Create and update repo-local skills that follow the MetaMask Mobile standard. Use for new repo-local skills, skill entrypoints, or harness shims in this repository.
Add and fix Detox E2E tests (smoke and regression) for MetaMask Mobile using withFixtures, Page Objects, and tests/framework. Use when creating a new spec, fixing a failing E2E test, adding page objects and selectors, or adding MetaMetrics analytics expectations (analyticsExpectations).
Write, fix, and update component view tests (*.view.test.tsx) for MetaMask Mobile using the tests/component-view/ framework. Use when creating a new view test file, fixing a failing view test, updating tests after a component change, or creating a new renderer or preset for a view.
Create and review E2E performance tests that measure real user flows on real devices with TimerHelper and PerformanceTracker. Use when creating, editing, or reviewing performance tests, when the user mentions perf tests, timing measurements, performance thresholds, or files in tests/performance/.
Creates or removes a git worktree using the project scripts and shared config. Use when the user asks to create a worktree, add a worktree, remove a worktree, delete a worktree, or work on a parallel branch in a separate directory.
Identify code owners for changed files and map them to Slack group handles. Use when the user asks who owns changed files, which teams to tag for review, or to find code owners for a PR.