pr-codeowners

Map changed files to responsible teams and Slack contacts from CODEOWNERS files.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/abretonc7s/metamask-skills --skill pr-codeowners-abretonc7s
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-codeowners
Source: https://github.com/abretonc7s/metamask-skills/tree/main/domains/pr-workflow/skills/pr-codeowners
Command: npx skills add https://github.com/abretonc7s/metamask-skills --skill pr-codeowners-abretonc7s

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of identifying responsible teams and Slack contacts based on changed files in repositories, reducing manual lookup time.

Core Features & Use Cases

  • Code Ownership Identification: Reads .github/CODEOWNERS files to determine team ownership for modified files.
  • Team-to-Slack Mapping: Maps code owner teams to corresponding Slack handles using a predefined lookup table.
  • Use Case: When reviewing a pull request with multiple changed files, quickly generate a list of relevant team Slack handles for targeted communication or notifications.

Quick Start

Provide the list of changed files to the Skill to obtain associated team and Slack handle pairs for collaboration.

Frequently Asked Questions about pr-codeowners

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

FAQPage Schema
How do I identify code owners from a GitHub pull request?

Mapping changed files to code owners involves reading `.github/CODEOWNERS` files to determine team ownership for modified files. It generates a structured list of responsible teams for targeted communication during development workflows.

How do I map GitHub CODEOWNERS teams to Slack handles?

Mapping GitHub CODEOWNERS teams to Slack handles uses a predefined lookup table to pair code owner teams with corresponding Slack contacts. This generates a structured list of team-Slack pairs for efficient notifications and reviews.

Can I automatically notify teams in Slack about modified files in multiple repositories?

Yes, you can automatically notify teams in Slack about modified files across multiple repositories. The process handles multiple changed files and maps them to responsible teams and Slack contacts for targeted communication.

Do I need external dependencies to parse CODEOWNERS files for team collaboration?

No, you do not need external dependencies to parse CODEOWNERS files for team collaboration. The process relies solely on reading predefined `.github/CODEOWNERS` files to determine team ownership and generate Slack contact pairs.

What is the best way to streamline code ownership identification for pull request reviews?

The best way to streamline code ownership identification for pull request reviews is to automatically map changed files to responsible teams using `.github/CODEOWNERS` files. This reduces manual lookup time and generates structured team-Slack pairs for targeted communication.