skills.rest
MetaMask
MetaMaskOFFICIAL
Explore all skills by this author →
Website𝕏@metamaskGitHub

pr-codeowners

Identify code owners for changed files and map them to Slack group handles.

3.0k|1.6k|Updated Jul 18, 2018
Search Tags:#automation#github#slack#pr#codeowners#codereview#team-mapping
One-click install
npx skills add https://github.com/MetaMask/metamask-mobile --skill pr-codeowners
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-codeowners
Source: https://github.com/MetaMask/metamask-mobile/tree/main/.agents/skills/pr-codeowners
Command: npx skills add https://github.com/MetaMask/metamask-mobile --skill pr-codeowners

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review often stalls when ownership is unclear; this skill identifies the teams responsible for changed files and maps them to Slack group handles to facilitate targeted reviews.

Core Features & Use Cases

  • Code ownership extraction: Read the repository's CODEOWNERS file to aggregate unique owners for all changed files.
  • Slack mapping: Convert owners to corresponding Slack group handles using a provided lookup.
  • Fallback handling: If an owner has no Slack mapping, default to a general review channel and warn the user.
  • Use Case: Given a PR with multiple changed files, quickly identify all owners and ping the appropriate Slack groups for review.

Quick Start

Identify code owners for changed files by reading CODEOWNERS and output a Slack-ready mapping for each owner.

Frequently Asked Questions about pr-codeowners

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I map GitHub code owners to Slack groups for PR reviews?▼

To map GitHub code owners to Slack groups for PR reviews, this skill reads your repository's CODEOWNERS file to identify responsible teams and translates them into Slack handles using a provided lookup mapping.

What happens if a GitHub code owner has no Slack mapping?▼

If a GitHub code owner has no Slack mapping, the skill applies fallback handling by defaulting to a general review channel and warning the user that the specific owner could not be mapped.

How do I identify unique code owners for changed files in a GitHub PR?▼

You identify unique code owners for changed files by reading the CODEOWNERS file in the repository, which aggregates the responsible teams or individuals across all modified paths in the pull request.

Can I use this automation with any GitHub repository to clarify PR ownership?▼

Yes, you can use this automation with any GitHub repository because it applies to PR reviews across GitHub repositories wherever ownership needs to be clarified using the CODEOWNERS file.

Does this skill require a Slack lookup table to map code owners?▼

Yes, the skill requires a provided Slack lookup table to convert aggregated GitHub code owners into corresponding Slack group handles for targeted review notifications.

Related Skills

Explore More Software Engineering Skills→
dtsongdtsong
1

GitHub PR Request Review

Request GitHub pull request reviewers by analyzing changed files and CODEOWNERS.

Community
Intermediate
Dev10x-GuruDev10x-Guru
7

Dev10x:slack

Send notifications, upload files, and reply in threads to Slack channels.

Official
Intermediate
yanochka11yanochka11

gh-review-requests

Fetch unread GitHub review notifications and filter pending pull requests by team.

Community
Intermediate
semicolon-devteamsemicolon-devteam

assign-task

Assign GitHub issues to assignees, manage workload points, and send Slack notifications.

Official
Intermediate