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.
95
93%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Get changed files:
git diff --name-only main...HEADRead .github/CODEOWNERS and match each changed file against the patterns to collect unique @MetaMask/<team> owners
Map each owner to a Slack group handle using the lookup table below
If an owner is not in the table, fall back to @metamask-mobile-platform and warn the user about the unmapped team
| CODEOWNERS team | Slack group handle |
|---|---|
| perps | mm-perps-engineering-team |
| confirmations | metamask-confirmations-team |
| metamask-earn | earn-dev-team |
| mobile-core-ux | mobile-core-ux |
| accounts-engineers | accounts-team-devs |
| swaps-engineers | swaps-engineers |
| metamask-assets | assets-dev-team |
| card | card-dev-team |
| notifications | notifications-dev-team |
| mobile-platform | metamask-mobile-platform |
| web3auth | onboarding-dev |
| wallet-integrations | wallet-integrations-team |
| wallet-api-platform | wallet-integrations-team |
| ramp | ramp-team |
| predict | predict-team |
| rewards | rewards-team |
| design-system-engineers | metamask-design-system-team |
| core-platform | core-platform-team |
| supply-chain | mm-supply-chain-reviewers |
| mobile-admins | metamask-mobile-platform |
| transactions | mm-transactions-stx-core-dev |
| delegation | delegators |
| qa | metamask-qa-team |
List of unique { team, slackHandle } pairs for all code owners of the changed files.
bee9b14
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.