code-owners

Identify code area owners and maintainers from commits, documentation, and org structure.

25|8|Updated Dec 8, 2025
One-click install
npx skills add https://github.com/gleanwork/claude-plugins --skill code-owners
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-owners
Source: https://github.com/gleanwork/claude-plugins/tree/main/plugins/glean/skills/code-owners
Command: npx skills add https://github.com/gleanwork/claude-plugins --skill code-owners

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies identifying the correct code area experts and maintainers, streamlining the process of finding the right person to talk to about a system or request a code review.

Core Features & Use Cases

  • Identify Code Area Experts: Quickly locate individuals who own, maintain, or have expertise in a specific code area.
  • Automated Search: Uses multiple signals including code commits, documentation, and org structure to determine ownership.
  • Vetting Process: Evaluates contributors based on activity, relevance, knowledge, and contact information.
  • Ownership Map: Provides a comprehensive map of active owners, historical contributors, and secondary contacts.
  • Unclear Ownership: Offers guidance on next steps if no clear owners are found.

Quick Start

Use the code-owners skill to find the owner of the 'system-api' code area.

Frequently Asked Questions about code-owners

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

FAQPage Schema
How do I find the right code area experts and maintainers for a specific module?

To find code area experts, the Skill analyzes code commits, documentation, and org structure to identify active owners, historical contributors, and secondary contacts. It evaluates contributors based on activity, relevance, and knowledge to map the right maintainers for your module.

How does code ownership analysis determine who should review my code?

Code ownership analysis determines reviewers by using automated search across multiple signals including commit history and documentation. It vets contributors based on activity, relevance, knowledge, and contact information to provide a comprehensive map of qualified code reviewers.

What should I do if there is no clear code owner for a codebase area?

If no clear code owners are found during the codebase navigation analysis, the Skill offers guidance on next steps. It evaluates historical contributors and secondary contacts to help you find an appropriate expert for consultation or code review.

Can I identify code area experts using commit history and org structure?

Yes, you can identify code area experts by analyzing commit history and org structure. The Skill cross-references these signals with documentation to accurately locate individuals who own, maintain, or have specific expertise in a code area.

What is the best way to map active owners and historical contributors for code maintenance?

The best way to map active owners and historical contributors is by analyzing code commits and documentation. This Skill vets contributors based on activity and relevance, providing a comprehensive ownership map to streamline code maintenance and expert consultation.