Update Codeowners
Developmentupdate-codeownersUpdate Codeowners is an Agent Skill for development published in the UbiquitousLearning/mllm repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Updates CODEOWNERS entries safely with consistent path and owner formatting. Use when the user asks to add, remove, or modify CODEOWNERS rules, ownership mappings, reviewers, or module maintainers.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/UbiquitousLearning/mllm/blob/HEAD/.claude/skills/update-codeowners/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/update-codeowners, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Update CODEOWNERS
Goal
Maintain CODEOWNERS accurately while preserving the repository's existing section/comment style.
Workflow
- Read the current
CODEOWNERSfile before editing. - Identify requested changes as one of:
- Add new path rule
- Modify owners for existing path rule
- Remove obsolete path rule
- Reorganize section comments (only if requested)
- Update rules in place instead of creating duplicates for the same path.
- Keep existing section headers and comment style unless the user asks to refactor structure.
- Return a concise changelog describing which paths were added, changed, or removed.
Rule Format
- Use one rule per line:
<path-pattern> <owner1> <owner2> ... - Owners must be GitHub handles prefixed with
@. - Keep path style consistent with the file (in this repo, path patterns typically start with
/). - Do not leave rules with empty owner lists.
Editing Guidelines
- Prefer minimal edits near related sections.
- If a path already exists, update that line instead of adding a second conflicting line.
- If a new rule logically belongs to an existing section, place it in that section.
- Preserve human-readable grouping and blank lines.
- Keep comments intact unless they are clearly outdated and the user asked for cleanup.
Validation Checklist
- Every non-comment, non-empty line has at least one owner.
- Every owner token starts with
@. - No accidental duplicate rule for the exact same path pattern.
- Existing comments/sections were preserved unless explicitly changed.
Example Requests
- "Add
/mllm/models/new_model/ @alice @bobunder models." - "Change
/core/Storageowner to@team-core." - "Remove ownership rule for deprecated path
/legacy/."