CtrlK
BlogDocsLog inGet started
Tessl Logo

pr-codeowners

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

Quality

93%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

PR Code Owners

Steps

  1. Get changed files:

    git diff --name-only main...HEAD
  2. Read .github/CODEOWNERS and match each changed file against the patterns to collect unique @MetaMask/<team> owners

  3. Map each owner to a Slack group handle using the lookup table below

  4. If an owner is not in the table, fall back to @metamask-mobile-platform and warn the user about the unmapped team

Code owner to Slack handle lookup

CODEOWNERS teamSlack group handle
perpsmm-perps-engineering-team
confirmationsmetamask-confirmations-team
metamask-earnearn-dev-team
mobile-core-uxmobile-core-ux
accounts-engineersaccounts-team-devs
swaps-engineersswaps-engineers
metamask-assetsassets-dev-team
cardcard-dev-team
notificationsnotifications-dev-team
mobile-platformmetamask-mobile-platform
web3authonboarding-dev
wallet-integrationswallet-integrations-team
wallet-api-platformwallet-integrations-team
rampramp-team
predictpredict-team
rewardsrewards-team
design-system-engineersmetamask-design-system-team
core-platformcore-platform-team
supply-chainmm-supply-chain-reviewers
mobile-adminsmetamask-mobile-platform
transactionsmm-transactions-stx-core-dev
delegationdelegators
qametamask-qa-team

Output

List of unique { team, slackHandle } pairs for all code owners of the changed files.

Repository
MetaMask/metamask-mobile
Last updated
Created

Is this your skill?

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.