Skip to content

0.4.0 - #259

Merged
georgewrmarshall merged 4 commits into
mainfrom
release/0.4.0
Nov 18, 2026
Merged

0.4.0#259
georgewrmarshall merged 4 commits into
mainfrom
release/0.4.0

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Release @metamask/skills 0.4.0

This is the release candidate for 0.4.0, a minor release that brings in everything merged to main since v0.3.1 (66 PRs). See CHANGELOG.md for the full list with PR links.

Highlights

New domains

  • observability: Sentry, Tempo and telemetry cost-control skills
  • performance: measurement, anti-pattern scanning and React Compiler triage
  • typescript: authoring and migration skills
  • platform: Extension runtime architecture and failure modes

New skills

  • Mobile planning (planning, planning-spec, jira-brief), now stable base skills for Mobile and Extension
  • analytics, feature-flags, navigation and selector-patterns, each with a repo-agnostic base and a Mobile overlay
  • A PR review base skill, generated Perps review checklists, notifications-category-sync, a profiling regression proposal skill and activity mapper guidance
  • Recipe planning and cooking skills, pinned to a single mm-harness version with an install-time version check

UI development and content

  • A shared, MCP-free ui-development baseline for looking up MetaMask Design System components, with thin Mobile and Extension overlays
  • Content guidelines with shared rules plus Mobile and Extension overlays, which now also apply when existing strings are edited

Testing

  • visual-testing and mobile-visual-testing updated for @metamask/client-mcp-core 0.14.0 and @metamask/device-mcp 0.8.0
  • Component-view flake rules and Appium stability patterns added to mobile-testing

Installer / CLI

  • Explicit-only skill invocation, preserved repository overlays and pruning of retired skill names during sync
  • Syncs of each shared skill source run one at a time, so concurrent syncs can't collide during a Git fetch
  • Skill descriptions over the 1024-character catalog limit are shortened

Changelog

The auto-generated [0.4.0] section has been rewritten into Added, Changed and Fixed entries, written for consumers. It replaces the Uncategorized commit titles, removes duplicates and adds the PRs that were missing (#159, #183, #212 and #213).

Release steps

  1. Approve the pending workflow run so CI runs on this PR, including yarn lint:changelog --rc, the tests and yarn pack:dry-run.
  2. Get a review from @MetaMask/extension-platform or @MetaMask/mobile-platform.
  3. Squash-merge, keeping github-actions as the commit author. That's what lets Publish Release run.
  4. @metamask-npm-publishers approve the npm-publish environment. Then @metamask/skills@0.4.0 is published to npm, and the v0.4.0 GitHub release and tag are created.

@georgewrmarshall
georgewrmarshall marked this pull request as ready for review November 17, 2026 21:24
@georgewrmarshall
georgewrmarshall enabled auto-merge (squash) November 17, 2026 21:37
Comment thread CHANGELOG.md

## [Unreleased]

## [0.4.0]

@georgewrmarshall georgewrmarshall Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

main had 25 author-written entries but only 8 of them linked a PR. The release workflow relies on PR links to know what is already covered, so it appended about 60 raw commit-title lines for the same PRs. This section merges the two into one entry per topic, with every PR link kept, so the lint can match each PR and readers see each change once.

Comment thread CHANGELOG.md Outdated
- Add `navigation` skill with a repo-agnostic base and a MetaMask Mobile overlay for `Routes` and `NavigationService`. Marked `base: true` so it installs even when its domain is filtered out.
- Add `feature-flags` skill with a repo-agnostic base and a MetaMask Mobile overlay for version-gated remote flags. Marked `base: true` so it installs even when its domain is filtered out. ([#147](https://github.com/MetaMask/skills/pull/147))
- Add `analytics` skill (`platform/analytics`, moved from `coding`) with a repo-agnostic base and a MetaMask Mobile overlay for the canonical tracking API. Marked `base: true` so it installs even when its domain is filtered out. ([#140](https://github.com/MetaMask/skills/pull/140))
- Add recipe planning and cooking skills (`recipe-plan-and-dispatch`, `recipe-library-audit`, `recipe-performance`, `recipe-cook`, and setup), pinned to a single mm-harness version with an install-time version check, titled checklist steps, proof artifacts on proof steps, and a recommended mm-harness 0.96.31. ([#256](https://github.com/MetaMask/skills/pull/256), [#251](https://github.com/MetaMask/skills/pull/251), [#244](https://github.com/MetaMask/skills/pull/244), [#233](https://github.com/MetaMask/skills/pull/233), [#228](https://github.com/MetaMask/skills/pull/228), [#227](https://github.com/MetaMask/skills/pull/227), [#225](https://github.com/MetaMask/skills/pull/225), [#215](https://github.com/MetaMask/skills/pull/215), [#214](https://github.com/MetaMask/skills/pull/214), [#206](https://github.com/MetaMask/skills/pull/206))

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The 10 recipe PRs are one entry because they all iterate on a skill set that is new in this release. Consumers upgrading from 0.3.1 only see the final skills, so fixes made to them before release are folded in rather than listed separately.

Comment thread CHANGELOG.md
- Skip a brief for an unkept spike or POC and for routine CI-only work, including a workflow edit that changes how jobs or E2E launch. A CI change that is large or a contract or API change still stops for a brief, and gets a spec recommendation only when it is large. For a revert of a merged pull request or commit, name the target and files, then ask one yes/no, and name the risk when security or privacy is involved. A fully specified ask that is not large, is not a contract or API change, and does not touch auth, secrets, logs or exports of state, permissions, keyring or vault, migrations, or persisted state gets one line of scope and one yes/no instead of a brief. Always read the installed skill catalog, including for reverts and fully specified asks.
- Add component-view rules to `testing/mobile-testing` from the Predict flake investigation: clear call history before call-count assertions, re-query after a remount instead of holding a `findBy*` result, keep time-dependent behaviour in unit tests or target-state fixtures, require a named async boundary for any explicit `{ timeout }`, and a Fixing a Flake section (name the cause, reproduce it, prove the fix; a longer timeout alone is not a fix).
- Document confirmed Appium interaction-stability patterns in `testing/mobile-testing` (`references/appium-e2e.md`): child readiness, fresh interactive queries, shared open retries, virtualized-list proof, native control state, action postconditions, and single assertions for short-lived alerts.
- **BREAKING:** Install `planning`, `planning-spec`, and `jira-brief` by default as stable `base` skills for MetaMask Mobile and Extension (Core stays out of scope). They run when scope is ambiguous, the change is large, or the work is security-sensitive, performance-sensitive, or a contract or API change; `planning` calls `jira-brief` only when a Jira ticket is already identified; revert yes/no prompts and brief gates are tighter. Opt out with `yarn skills --exclude planning/planning,planning/planning-spec,planning/jira-brief --save`. An installed copy keeps its previous trigger until the next sync. ([#254](https://github.com/MetaMask/skills/pull/254), [#219](https://github.com/MetaMask/skills/pull/219), [#204](https://github.com/MetaMask/skills/pull/204))

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This describes where planning ended up, not each step along the way. #219 briefly made these skills experimental and dropped base: true, and #254 made them stable base skills again, so listing both would contradict itself. It is marked breaking because a default sync now installs three skills that were not installed before, and the opt-out command and the note about installed copies are kept so teams can act on it.

Comment thread CHANGELOG.md Outdated
- Add component-view rules to `testing/mobile-testing` from the Predict flake investigation: clear call history before call-count assertions, re-query after a remount instead of holding a `findBy*` result, keep time-dependent behaviour in unit tests or target-state fixtures, require a named async boundary for any explicit `{ timeout }`, and a Fixing a Flake section (name the cause, reproduce it, prove the fix; a longer timeout alone is not a fix).
- Document confirmed Appium interaction-stability patterns in `testing/mobile-testing` (`references/appium-e2e.md`): child readiness, fresh interactive queries, shared open retries, virtualized-list proof, native control state, action postconditions, and single assertions for short-lived alerts.
- **BREAKING:** Install `planning`, `planning-spec`, and `jira-brief` by default as stable `base` skills for MetaMask Mobile and Extension (Core stays out of scope). They run when scope is ambiguous, the change is large, or the work is security-sensitive, performance-sensitive, or a contract or API change; `planning` calls `jira-brief` only when a Jira ticket is already identified; revert yes/no prompts and brief gates are tighter. Opt out with `yarn skills --exclude planning/planning,planning/planning-spec,planning/jira-brief --save`. An installed copy keeps its previous trigger until the next sync. ([#254](https://github.com/MetaMask/skills/pull/254), [#219](https://github.com/MetaMask/skills/pull/219), [#204](https://github.com/MetaMask/skills/pull/204))
- **BREAKING:** Move the `analytics` skill from `coding` to `platform` (`platform/analytics`). Update any saved `--exclude` or `--include` paths that use `coding/analytics`. ([#140](https://github.com/MetaMask/skills/pull/140))

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The analytics skill's new path is a breaking change for anyone with coding/analytics in a saved --exclude or --include list, so it gets its own breaking entry. The matching entry under Added covers the skill content itself.

Comment thread CHANGELOG.md
- Document confirmed Appium interaction-stability patterns in `testing/mobile-testing` (`references/appium-e2e.md`): child readiness, fresh interactive queries, shared open retries, virtualized-list proof, native control state, action postconditions, and single assertions for short-lived alerts.
- **BREAKING:** Install `planning`, `planning-spec`, and `jira-brief` by default as stable `base` skills for MetaMask Mobile and Extension (Core stays out of scope). They run when scope is ambiguous, the change is large, or the work is security-sensitive, performance-sensitive, or a contract or API change; `planning` calls `jira-brief` only when a Jira ticket is already identified; revert yes/no prompts and brief gates are tighter. Opt out with `yarn skills --exclude planning/planning,planning/planning-spec,planning/jira-brief --save`. An installed copy keeps its previous trigger until the next sync. ([#254](https://github.com/MetaMask/skills/pull/254), [#219](https://github.com/MetaMask/skills/pull/219), [#204](https://github.com/MetaMask/skills/pull/204))
- **BREAKING:** Move the `analytics` skill from `coding` to `platform` (`platform/analytics`). Update any saved `--exclude` or `--include` paths that use `coding/analytics`. ([#140](https://github.com/MetaMask/skills/pull/140))
- **BREAKING:** Update `testing/mobile-visual-testing` for `@metamask/client-mcp-core` 0.13.x and 0.14.0 and `@metamask/device-mcp` 0.7.0 and 0.8.0. The knowledge store commands, the knowledge-reuse step, and the `--goal` and `--flow-tags` launch flags are removed. Failures are now one-line JSON on stdout with `error.code`, `hint`, `retryable`, and per-class exit codes, and the Android guidance is corrected from a live emulator run. ([#249](https://github.com/MetaMask/skills/pull/249), [#211](https://github.com/MetaMask/skills/pull/211), [#164](https://github.com/MetaMask/skills/pull/164))

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Marked breaking because the knowledge store commands and the --goal and --flow-tags launch flags are gone, so existing prompts or scripts that use them will fail. Three PRs across client-mcp-core 0.13.x and 0.14.0 are combined because 0.13.x was never released on its own in this package. The full command reference lives in the skill itself, so the entry lists only what a consumer has to change.

Comment thread CHANGELOG.md
- **BREAKING:** Install `planning`, `planning-spec`, and `jira-brief` by default as stable `base` skills for MetaMask Mobile and Extension (Core stays out of scope). They run when scope is ambiguous, the change is large, or the work is security-sensitive, performance-sensitive, or a contract or API change; `planning` calls `jira-brief` only when a Jira ticket is already identified; revert yes/no prompts and brief gates are tighter. Opt out with `yarn skills --exclude planning/planning,planning/planning-spec,planning/jira-brief --save`. An installed copy keeps its previous trigger until the next sync. ([#254](https://github.com/MetaMask/skills/pull/254), [#219](https://github.com/MetaMask/skills/pull/219), [#204](https://github.com/MetaMask/skills/pull/204))
- **BREAKING:** Move the `analytics` skill from `coding` to `platform` (`platform/analytics`). Update any saved `--exclude` or `--include` paths that use `coding/analytics`. ([#140](https://github.com/MetaMask/skills/pull/140))
- **BREAKING:** Update `testing/mobile-visual-testing` for `@metamask/client-mcp-core` 0.13.x and 0.14.0 and `@metamask/device-mcp` 0.7.0 and 0.8.0. The knowledge store commands, the knowledge-reuse step, and the `--goal` and `--flow-tags` launch flags are removed. Failures are now one-line JSON on stdout with `error.code`, `hint`, `retryable`, and per-class exit codes, and the Android guidance is corrected from a live emulator run. ([#249](https://github.com/MetaMask/skills/pull/249), [#211](https://github.com/MetaMask/skills/pull/211), [#164](https://github.com/MetaMask/skills/pull/164))
- **BREAKING:** Update `testing/visual-testing` for `@metamask/client-mcp-core` 0.13.1 and 0.14.0. The knowledge store commands, the mandatory knowledge-reuse step, and the `--preset` launch example are removed, and `yarn build:test` replaces the removed `yarn build:test:webpack` script. Failures are now one-line JSON on stdout with structured error codes, and the 0.14.0 commands (`mm inspect`, `mm hover`, `mm set-viewport`, `mm reload`, `mm stop`, and browser `mm scroll-to-element`) are documented. ([#248](https://github.com/MetaMask/skills/pull/248), [#210](https://github.com/MetaMask/skills/pull/210))

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Breaking for the same reason as the mobile entry above: removed knowledge store commands and the --preset example, plus the yarn build:test:webpack script being replaced by yarn build:test. The new 0.14.0 commands are named so readers know what to look up in the skill.

Comment thread CHANGELOG.md
- Add a `feature-flags` skill with a repo-agnostic base and a MetaMask Mobile overlay for version-gated remote flags, marked `base: true` so it installs even when its domain is filtered out. ([#147](https://github.com/MetaMask/skills/pull/147))
- Add an `analytics` skill (`platform/analytics`) with a repo-agnostic base and a MetaMask Mobile overlay for the canonical tracking API, marked `base: true` so it installs even when its domain is filtered out. ([#140](https://github.com/MetaMask/skills/pull/140))
- Add an `observability` domain with Sentry, Tempo, and telemetry cost-control skills. ([#76](https://github.com/MetaMask/skills/pull/76))
- Add skill rules that previously existed only in Farmslot fixtures. ([#238](https://github.com/MetaMask/skills/pull/238))

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Listed under Added because these rules are new to this package, even though they already existed as Farmslot fixtures.

Comment thread CHANGELOG.md Outdated
- Fix the `testing/visual-testing` CLI reference for screenshots, tabs, and duplicate matches, and fix the Redux state-manipulation guidance for React 18 and LavaMoat builds. ([#237](https://github.com/MetaMask/skills/pull/237), [#230](https://github.com/MetaMask/skills/pull/230))
- Finish `recipe-cook` tasks when criteria are still awaiting review. ([#208](https://github.com/MetaMask/skills/pull/208))
- Serialize updates of each shared skill source so concurrent syncs cannot race on Git's fetch state. ([#207](https://github.com/MetaMask/skills/pull/207))
- Shorten skill descriptions that exceeded the 1024-character catalog limit, including `typescript/tsc-blindspots`. ([#158](https://github.com/MetaMask/skills/pull/158))

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Combines #158 with the later tsc-blindspots fix, since both address descriptions going over the 1024-character catalog limit.

@andrepimenta

Copy link
Copy Markdown
Member

Thanks for the rewrite. All 66 PRs since v0.3.1 are linked and lint:changelog --rc passes. A few things before merging:

  1. The branch is behind main. chore(recipe-cook): recommend mm-harness 0.96.32 and require a recorded baseline before the fix #258, docs(perps-review-pr): accept a branch or commit range as the review request #260 and chore(perps-review-pr): regenerate from the Perps rules at f8b9642 #261 merged after the branch was cut. A squash-merge would ship them in 0.4.0 with no changelog entry. Because v0.4.0 will be tagged after them, the next release PR won't pick them up either. Please update from main and add entries for them:
  2. Drop the "BREAKING: Move analytics from coding" entry. feat: add analytics skill with MetaMask Mobile overlay #140 added the skill directly at platform/analytics. coding/analytics doesn't exist in v0.3.1 or anywhere in main's history, so no one can have it in a saved --exclude or --include. The Added entry covers it.
  3. Nit: the tsc-blindspots description fix landed in fix(sync): serialize shared source updates #207, so that line should link fix(sync): serialize shared source updates #207 as well as fix: shorten skill descriptions over the 1024-character operator limit #158.

Separately, docs/processes/releasing.md is out of date. It names yarn create-release-branch and yarn changelog:validate, which don't exist, and lists the publish steps in the wrong order. Worth a follow-up PR.

Folds the post-branch merges into the curated 0.4.0 changelog per review:
#258/#262 (mm-harness 0.96.33) into the recipe entry, #260/#261 into the
perps-review-pr entry, #264 rule pack and #231 CV lint checklist as new
entries, drops the inaccurate analytics-move BREAKING entry, and links

Co-authored-by: George Marshall <georgewrmarshall@users.noreply.github.com>
#207 on the tsc-blindspots entry.
@cursor

cursor Bot commented Nov 18, 2026

Copy link
Copy Markdown

Thanks for the review — all four points are addressed on release/0.4.0 (merge commit d590f53):

  1. Updated from main. Since your comment, chore(recipe): recommend mm-harness 0.96.33 #262 and feat(perps-review-pr): generate a machine-readable rule pack #264 also merged, so the changelog now covers everything that landed after the branch was cut:
  2. Dropped the "BREAKING: Move analytics from coding" entry — coding/analytics never existed in v0.3.1 or main's history, and the Added entry covers the skill.
  3. The tsc-blindspots entry now links fix: shorten skill descriptions over the 1024-character operator limit #158 and fix(sync): serialize shared source updates #207.
  4. docs/processes/releasing.md is fixed in docs(processes): correct the releasing guide #265.

yarn lint:changelog --rc, yarn build, yarn test, and yarn pack:dry-run all pass locally; CI is running on the branch.

@MetaMask MetaMask deleted a comment from cursor Bot Nov 18, 2026
@georgewrmarshall
georgewrmarshall merged commit 12753ca into main Nov 18, 2026
28 checks passed
@georgewrmarshall
georgewrmarshall deleted the release/0.4.0 branch November 18, 2026 18:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants