github-codeowners-management
Github Codeowners Management
Overview
Use this skill to keep CODEOWNERS enforceable, low-noise, and aligned with actual maintainer responsibility.
Scope Boundaries
- Use this skill when the task matches the trigger condition described in
description. - Do not use this skill when the primary task falls outside this skill's domain.
Shared References
- CODEOWNERS pattern guidance:
references/codeowners-patterns.md
Templates And Assets
- CODEOWNERS change plan:
assets/codeowners-change-plan-template.md
Inputs To Gather
- Repository ownership map by criticality and change frequency.
- Team boundaries, backup owners, and staffing constraints.
- Required reviewer policy for sensitive paths.
- Recent PR routing pain points (over-review, no-owner paths, stale owners).
Deliverables
- CODEOWNERS update plan with rationale.
- Ownership gap/overlap report.
- Verification results for routing behavior.
- Maintenance plan for owner lifecycle changes.
Workflow
- Capture proposed changes in
assets/codeowners-change-plan-template.md. - Map high-risk paths to explicit primary and backup owners.
- Resolve overlap and wildcard precedence issues.
- Validate with lint scripts and sample PR routing.
- Publish changes with ownership maintenance rules.
Scripts
- Lint CODEOWNERS:
python3 scripts/lint_codeowners.py --path .github/CODEOWNERS --policy team
- Enforce required patterns:
python3 scripts/lint_codeowners.py --path .github/CODEOWNERS --policy team --require-pattern '/.github/workflows/*'
- GitHub semantics mode (without strict team catch-all ordering):
python3 scripts/lint_codeowners.py --path .github/CODEOWNERS --policy github
Quality Standard
- Critical paths always have active owners and backup coverage.
- Wildcards do not mask sensitive-path ownership.
- Rules are maintainable and avoid unnecessary reviewer fan-out.
- Routing behavior matches expected maintainers on real PR samples.
Failure Conditions
- Stop when critical paths are left without accountable owners.
- Stop when CODEOWNERS rules cannot be validated by lint and sample checks.
- Escalate when staffing gaps prevent enforceable ownership policy.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9redis-caching-patterns
Redis caching workflow for latency improvement with explicit key strategy, TTL/invalidation policy, and correctness bounds. Use when Redis-backed caching decisions are required for application performance; do not use for repository-wide architecture governance or release management policy.
9