code-owners
/code-owners
Identify who owns, maintains, or has expertise in a specific code area — use when asked who to talk to about a system, who to request a code review from, or who has been actively working in a codebase area.
- Author
- gleanwork ↗
- Repository
- claude-plugins ↗
- Licence
- MIT
- Last repository change
- 29.09.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 29.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Identify who owns, maintains, or has expertise in a specific code area — use when asked who to talk to about a system, who to request a code review from, or who has been actively working in a codebase area.
Original author description
Identify who owns, maintains, or has expertise in a specific code area — use when asked who to talk to about a system, who to request a code review from, or who has been actively working in a codebase area.
How it works
- Core Principles
- Process
- If No Clear Owners Found
SKILL.md preview
--- name: code-owners description: Identify who owns, maintains, or has expertise in a specific code area — use when asked who to talk to about a system, who to request a code review from, or who has been actively working in a codebase area. --- # Code Owners Identify who owns, maintains, or has expertise in a specific code area. Determine the component or codebase area from the user's request. If not specified, ask before proceeding. ## Core Principles - **Multi-signal identification**: Code + docs + org structure = complete picture - **Recency matters**: Active maintainers are more useful than historical authors - **Be skeptical**: Just having commits doesn't mean they're the right contact - **Quality over quantity**: 2-3 right people beats 10 tangential names ## Process ### Phase 1: Find Recent Contributors Search for who's been actively working on this code: ``` code_search "[component] owner:* updated:past_month" code_search "[component] from:* updated:past_3_months" ``` ### Phase 2: Find Historical Authors Look for original authors and significant contributors: ``` code_search "[component] owner:* after:2023-01-01" ``` ### Phase 3: Find Related Documentation Authors People who wrote the docs often have deep knowledge: ``` search "[component] design doc OR architecture owner:*" search "[component] RFC owner:*" ``` ### Phase 4: Cross-Reference with Org Info Get current roles and contact info: ``` employee_search "[contributor names]" ``` ### Phase 5: Vet Each Candidate For each person found, evaluate: | Test | ✅ Active Owner | ⚠️ Consider | ❌ Reject | |------|---------------|------------|---------| | **Ownership** | Multiple commits in past 3 months, reviews PRs | Occasional activity, still relevant | Single commit, tangential involvement | | **Relevance** | Same team, same area | Changed teams but retains context | Left company, completely different area | | **Knowledge** | Wrote design docs, significant PRs, in CODEOWNERS | Regular contributor, knows the code | Minor commits, typo fixes | | **Contact** | Owns the code, expects questions | Knowledgeable but busy/senior — suggest alternatives first | Would be surprised to be contacted | ### Phase 6: Present Vetted Ownership Map ```markdown # Code Ownership: [Component] ## Vetting Summary | Candidates Found | Active Owners | Historical | Rejected | |------------------|---------------|------------|----------| | [X] | [Y] | [Z] | [W] | ## Primary Contacts (Recommended) ### 1. [Name] — [Title] **Confidence**: High - **Why**: Most active contributor, [X] commits in past month - **Good for**: Day-to-day questions, PR reviews - **Last active**: [date] - **Contact**: [email] ## Secondary Contacts | Name | Role | Why Secondary | Contact | |------|------|---------------|---------| | [Name] | [Title] | Moved to [team] but retains context | [email] | ## Historical Contributors | Name | Contribution | Current Role | Last Active | |------|--------------|--------------|-------------| | [Name] | Original author | Now on [team] | [date] | ## Team Ownership - **Team**: [team name] - **Manager**: [name] - **Slack channel**: [channel] (may be faster than individual outreach) ## Rejected Candidates | Name | Reason | |------|--------| | [Name] | Single commit — typo fix only | | [Name] | Left company | ``` ## If No Clear Owners Found ```markdown # Code Ownership: [Component] ## Ownership Unclear Could not identify clear owners for this component. **Possible explanations:** - Ownership may be implicit within a team - Code may be unmaintained/legacy **Suggested next steps:** 1. Check the repository's CODEOWNERS or MAINTAINERS file directly 2. Look at recent PR reviewers as a proxy 3. Ask in [relevant Slack channel] ```
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · gleanwork/claude-plugins | 100 | MIT |
| Amey-Thakur/AI-SKILLS | 90 | MIT |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 292626931b5d (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100ownership-map
Work out who owns what and who decides, from evidence rather than the org chart - CODEOWNERS, commit authorship over time, review patterns, ticket references, and directory-level activity - distinguishing who wrote the code from who maintains it now. Use when you need a… - 100analyze-knowledge
Use when the user asks who knows specific code, who should review a PR or files, what the lottery factor is, whether knowledge is concentrated or spread, who to talk to about a code area, or when suggesting reviewers beyond GitHub's built-in suggestions. - 100context-document
Use when the user says \"create context\", \"document this area\", or wants a structured snapshot of a codebase area for agent orientation. - 100establishing-code-ownership
Determine which PostHog team owns a file, directory, or code path, or enumerate all code a team owns (via distributed `owners.yaml`, `products/*/product.yaml`, and `.github/CODEOWNERS`). Use when assigning a reviewer, attributing a bug or slow query to a team, routing work,… - 100review
Review — judge a diff or an area of existing code without changing it, using review-diff for the evidence standard and independent reviewers when useful. Use for /haechi:review, when the user asks to review a merge request, a branch, uncommitted changes or an area of code. - 90reviews
Review a pull request or code change for code health. Use when a user asks to "code review", "review this PR", or "review this change".