skills.rest
tylerbutler
tylerbutlerCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

find-owners

Identify package and code owners from Git repository history and CODEOWNERS files.

Updated Jan 7, 2026
Search Tags:#git#repository analysis#contributors#sme#code owners#package ownership
One-click install
npx skills add https://github.com/tylerbutler/repo-overlays --skill find-owners
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: find-owners
Source: https://github.com/tylerbutler/repo-overlays/tree/main/tylerbutler/FluidFramework/jikim-superskills/.claude/skills/find-owners
Command: npx skills add https://github.com/tylerbutler/repo-overlays --skill find-owners

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you quickly identify the owners of specific packages, code sections, or subject matter experts within the FluidFramework repository, streamlining communication and issue resolution.

Core Features & Use Cases

  • CODEOWNERS Lookup: Directly finds owners listed in the CODEOWNERS file for a given path.
  • Package Identification: Locates relevant package.json files based on search terms.
  • Contributor Analysis: Analyzes Git history to identify recent and historical contributors, and filters out noise like bot commits.
  • Use Case: When you encounter a bug in the 'SharedTree' package, you can use this Skill to find out who is primarily responsible for it and who has recently made significant contributions.

Quick Start

Find the owners for the 'container-runtime' package.

Frequently Asked Questions about find-owners

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

FAQPage Schema
How do I find package owners and code owners in a Git repository?▼

To find package owners in a Git repository, you can scan CODEOWNERS files and search for package.json based on specific terms. This process identifies the individuals responsible for particular code sections.

Can I identify subject matter experts by analyzing Git history?▼

Yes, analyzing Git history identifies subject matter experts by surfacing recent and historical contributors. It filters out automated commits and bot accounts to provide actionable contact information.

How do I locate the correct package.json file using search terms?▼

You can locate package.json files by providing relevant search terms to the identification tool. It matches these terms against the repository structure to pinpoint the exact package configuration file.

Does repository analysis filter out automated bot commits when finding contributors?▼

Yes, contributor analysis filters out automated commits and bot accounts from the Git history. This ensures you only receive actionable contact information for actual human developers.

What is the best way to find recent contributors to a specific code package?▼

The best way to find recent contributors is to analyze Git history for the specific package. This approach identifies both recent and historical contributors while filtering out automated noise.

How do CODEOWNERS files help identify who is responsible for code sections?▼

CODEOWNERS files directly list the owners for a given path within a repository. Looking up these files allows you to quickly identify exactly who is responsible for specific code sections.

Related Skills

Explore More Software Engineering Skills→
opendatahub-ioopendatahub-io
36

shallow-clone

Creates a depth-1 clone of a Git repository in a temporary location.

Official
Intermediate
djinilabsdjinilabs
8

Intercom Customer Conversations

Search Intercom contacts and conversations, then send replies.

Official
Intermediate
gleanworkgleanwork
25

find-expert

Identify subject matter experts from code contributions, document authorship, and meeting activity.

Official
Advanced
drhazemibclcdrhazemibclc

git-history-analyzer

Trace git commit history to reveal refactors and contributors.

Community
Advanced