菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| 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. |
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.
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"
Look for original authors and significant contributors:
code_search "[component] owner:* after:2023-01-01"
People who wrote the docs often have deep knowledge:
search "[component] design doc OR architecture owner:*"
search "[component] RFC owner:*"
Get current roles and contact info:
employee_search "[contributor names]"
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 |
# 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 |
# 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]
Search the public Glean developer documentation for API, SDK, MCP, authentication, indexing, and integration details. Use when the user is building with Glean rather than searching internal company knowledge — trigger phrases include Glean API, Glean SDK, integrate with Glean, indexing API, Glean Python or JavaScript SDK, and how to authenticate with Glean. Don't use it for internal company knowledge, which the using-glean skill covers.
Catch up on what you missed while away — meetings, decisions, action items, mentions, and important threads from a defined time window. Trigger phrases include "what did I miss", "catch me up", "I was out", "I'm back from PTO", "summarize while I was away", "what happened last week while I was off", "I just got back", "fill me in on what I missed".
Gather architectural context about an internal system from code and documentation across the organization — use when asked to understand a system's architecture, find its repos, or get an overview before working on it.
Help the user connect a Glean MCP server so the Glean skills have tools to call — use when setting up Glean for the first time, adding another Glean server, checking whether Glean is connected, or troubleshooting missing Glean tools. Trigger phrases include "set up Glean", "connect Glean", "configure Glean MCP", "add a Glean server", "is Glean connected", "check Glean status", "Glean isn't working", "no Glean tools", "the Glean tools aren't showing up", "I installed the Glean plugin but nothing happens". Don't use it for actual enterprise queries once connected (use the using-glean skill); this skill only sets up and verifies the connection.
Find usage examples of an API, library, or code pattern across internal repositories — use when looking for how other teams use an internal API, library, or pattern before implementing something new.
Find subject matter experts on a topic, technology, or internal system by combining real expertise signals (code contributions, document authorship, and meeting or discussion activity) rather than relying on job titles. Use this whenever the user wants to know who to ask about something — phrasings such as who knows about, who is the expert on, the go-to person for, who has worked on, who can I ask about, or subject matter expert for. Use it even when the user does not say the word expert but clearly needs a person with deep, demonstrated knowledge of an area. Do not use it for plain directory lookups (an email address, manager, or org placement with no expertise angle), which is a simple employee lookup.