code-owners
/code-owners
Ustala, kto jest właścicielem, opiekunem lub ekspertem danego obszaru kodu, do kogo zwrócić się o code review i kto aktywnie w nim pracuje.
- Autor
- gleanwork ↗
- Repozytorium
- claude-plugins ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 29.09.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 29.09.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Ustala, kto jest właścicielem, opiekunem lub ekspertem danego obszaru kodu, do kogo zwrócić się o code review i kto aktywnie w nim pracuje.
Oryginalny opis (EN)
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.
Jak działa
- Core Principles
- Process
- If No Clear Owners Found
Podgląd SKILL.md
--- 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] ```
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · gleanwork/claude-plugins | 100 | MIT |
| Amey-Thakur/AI-SKILLS | 90 | MIT |
Identyczna treść występuje jeszcze w 1 innych folderach na GitHubie. Tu pokazujemy jedną, najlepiej ocenioną kopię.
Migawka bazy z 13.11.2026 · wersja paczki 292626931b5d (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100ownership-map
Ustala, kto jest właścicielem kodu i kto podejmuje decyzje, na podstawie historii commitów, przeglądów i CODEOWNERS. - 100analyze-knowledge
Wskazuje, kto zna dany fragment kodu, kogo prosić o przegląd PR i czy wiedza jest skoncentrowana czy rozproszona w zespole. - 100context-document
Tworzy uporządkowaną migawkę wybranego obszaru bazy kodu, która pomaga agentowi w orientacji w projekcie. - 100establishing-code-ownership
Ustala, który zespół PostHog odpowiada za plik, katalog lub ścieżkę kodu, albo wylicza cały kod zespołu na podstawie owners.yaml, product.yaml i CODEOWNERS. - 100review
Ocenia diff albo fragment istniejącego kodu bez zmieniania go, z dowodami i niezależnymi recenzentami, gdy to potrzebne. - 90reviews
Przegląda zmianę w kodzie lub pull request pod kątem kondycji kodu, np. na prośbę o code review.