pr-codeowners

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.