Agent skill

Codeownership

by LedgerHQ in LedgerHQ/ledger-live

Maintain CODEOWNERS file and team directories. An agent skill from LedgerHQ/ledger-live.

MITAuto-check passed

Install Codeownership

skills CLI
$ npx skills add LedgerHQ/ledger-live --skill codeownership -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install LedgerHQ/ledger-live codeownership --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/LedgerHQ/ledger-live.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/codeownership .claude/skills/codeownership && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
codeownership
GitHub stars
621
Token cost
~687 tokens
SKILL.md length
205 words
Files
2
Skills in repo
50
Repo updated
First seen
Licence
MIT

At a glance

Maintain CODEOWNERS file and team directories. An agent skill from LedgerHQ/ledger-live.

  • Working with /team-/
  • SKILL.md covers Why, What, Resolving ownership for a list… and Checking CODEOWNERS before…, plus 1 more section
  • Runs JavaScript scripts from its folder; calls node and git
  • Splitting monolithic files

What it does

Codeownership is an agent skill from LedgerHQ/ledger-live. Maintain CODEOWNERS file and team directories. Provides resolve-codeowners.js to annotate files with their owner team — useful to split a large PR by team. Use when working with "/team-/" or splitting monolithic files.

Its SKILL.md is about 690 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `resolve-codeowners.js`).

The repository describes itself as: Mono-repository for Ledger Wallet apps and related packages. The licence is MIT.

When your agent uses it

  • Working with /team-/
  • Splitting monolithic files

Example prompts

  • “/team-/”
  • “/codeownership”

Requirements

  • Node.js

What it can do on your machine

Read from SKILL.md and the folder at commit a3861a2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships script files (JavaScript), which the agent can run.

    Shell commands in SKILL.md call:

    • node
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Codeownership loads about 687 tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 205 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~59
When it runs · the whole SKILL.md, loaded when a task matches
~687

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from LedgerHQ/ledger-live at commit a3861a2, republished under its MIT licence (© LedgerHQ). 205 words, ~687 tokens.

Download SKILL.mdSave it as .claude/skills/codeownership/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
codeownership
description
Maintain CODEOWNERS file and team directories. Provides resolve-codeowners.js to annotate files with their owner team — useful to split a large PR by team. Use when working with "**/team-*/**" or splitting monolithic files.

Codeownership

Why

  • To reduce cross-team review bottlenecks

What

  • Make ownership of team specific directories clear
  • Organise some directories into team-specific sub-directories
  • Maintain CODEOWNERS files when team specific directories are added or removed
  • Split monolithic files or folders that have been identified as being touched by too many teams

Resolving ownership for a list of files

Use resolve-codeowners.js to annotate any list of files with their CODEOWNERS team — handy when splitting a large PR by team owner. It uses the same matcher as the CI check in validate-codeowners, so it resolves exactly as GitHub does (case-sensitive, no install needed).

bash
# From a git diff
git diff --name-only HEAD~1 | node .agents/skills/codeownership/resolve-codeowners.js

# Explicit file list
node .agents/skills/codeownership/resolve-codeowners.js apps/ledger-live-desktop/src/foo.ts libs/env/src/bar.ts

# Override CODEOWNERS location
node .agents/skills/codeownership/resolve-codeowners.js --codeowners /path/to/CODEOWNERS <files...>

Output format (same columns as CODEOWNERS, but resolved to actual files):

apps/ledger-live-desktop/src/main/index.ts  @ledgerhq/platform
apps/ledger-live-desktop/src/renderer/foo.ts  @ledgerhq/wallet-xp
.github/workflows/e2e.yml  @ledgerhq/wallet-ci @ledgerhq/qaa
random/unknown/file.xyz  (no owner)

Semantics: last-rule-wins; ownerless entries appear as (no owner).

Checking CODEOWNERS before pushing

After editing CODEOWNERS, or moving or deleting files it names, run the CI check locally:

bash
node .agents/skills/codeownership/resolve-codeowners.js --check

It fails on rules that match no file, never take effect, re-own narrower rules from a later position, or use an unanchored name that matches in several places. Put defaults such as **/tsconfig* near the top; team-specific rules come after them.

Target

Splitting a monolithic file
  • Split [foo].ts into [foo]/team-[name]/*.ts
Maintaining team specific directories
Example

/shared/feature-flags/src/flags/ contains team-coin-integration, team-engagement, team-live-devices, etc.

CODEOWNERS defines the owner for each of these:

**/team-coin-integration/         @ledgerhq/coin-integration
**/team-engagement/               @ledgerhq/engagement
**/team-live-devices/             @ledgerhq/live-devices

© LedgerHQ, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .agents/skills/codeownership of LedgerHQ/ledger-live.

  • SKILL.md
  • resolve-codeowners.js

Open the folder on GitHubat commit a3861a2

Compare with similar skills

Codeownership next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Codeownership compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Codeownership this skillLedgerHQ/ledger-live621—~687Automated safety check: PassMIT
Deerflow Maintainer Orchestratorbytedance/deer-flow83k—~5.4kAutomated safety check: PassMIT
Open Source Maintainer Assistantslopus/happy24k—~1.9kAutomated safety check: PassMIT
Maintainer Reviewopenai/openai-agents-python30k—~8.9kAutomated safety check: PassMIT
Brilliant Directories AutomationComposioHQ/awesome-claude-skills77k3 repos~783Automated safety check: PassNone
Resolve Git Conflictspenpot/penpot61k—~772Automated safety check: PassMPL-2.0

Similar skills

  • A skill your agent uses when a DeerFlow maintainer needs comment-only GitHub issue or PR handling: resolve issue/PR scopes with gh, analyze issues, post or draft issue comments, perform PR review…

    83k GitHub stars~5.4k tokensUpdated today
    DevelopmentAuto-check passed
  • Helps maintain the slopus/happy open source project by triaging issues, drafting closing comments, finding duplicates and checking fixes, with approval before anything is posted.

    24k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed
  • Maintainer Review

    openai/openai-agents-python

    Official

    Assess a GitHub issue or PR for demonstrated need, supported alternatives, correctness, and maintainer action.

    30k GitHub stars~8.9k tokensUpdated today
    DevelopmentAuto-check passed
  • Brilliant Directories Automation

    ComposioHQ/awesome-claude-skills

    Automate Brilliant Directories tasks via Rube MCP (Composio).

    77k GitHub starsUsed in 3 repos~783 tokens
    Productivity & AutomationAuto-check passed
  • Conflict resolution flow — understand the local git conflicts, present a resolution plan, and resolve them after the user approves it.

    61k GitHub stars~772 tokensUpdated today
    DevelopmentAuto-check passed
  • Triages and works through GitHub issues and pull requests in the Q00/ouroboros repo as a maintainer, within a stated review boundary and clear limits on what it may change.

    6.2k GitHub stars~1.7k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from LedgerHQ/ledger-live

All 50 skills in this repo
  • Impacting PRs

    LedgerHQ/ledger-live

    Find which open PRs are impacted by a migration/sunset/refactor and notify their authors — blocking review when the old path is already gone from develop, heads-up comment when it is only deprecated…

    621 GitHub stars~3.3k tokensUpdated today
    Auto-check passed
  • Cloud Sync Module

    LedgerHQ/ledger-live

    Write, review or debug a cloudSyncModule.ts — a CloudSyncDataManager that syncs one slice of user data through Ledger Sync (Cloud Sync).

    621 GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • Coin Families Contract

    LedgerHQ/ledger-live

    Coin-specific families logic must live in families/. An agent skill from LedgerHQ/ledger-live.

    621 GitHub stars~1k tokensUpdated today
    Auto-check passed
  • Data Layer Advanced

    LedgerHQ/ledger-live

    Structure a Ledger Wallet data layer where one API response serves several entities.

    621 GitHub stars~509 tokensUpdated today
    Auto-check passed
  • Debug Rn Native Crash

    LedgerHQ/ledger-live

    Investigate native React Native crashes (Fabric/Hermes/iOS) in ledger-live-mobile when JS error logs are missing or unhelpful.

    621 GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Detect Data Leaks

    LedgerHQ/ledger-live

    Detect new PII leaks introduced by the current branch. An agent skill from LedgerHQ/ledger-live.

    621 GitHub stars~1.3k tokensUpdated today
    Auto-check passed

Questions about Codeownership

What does Codeownership do?

Maintain CODEOWNERS file and team directories. An agent skill from LedgerHQ/ledger-live. Codeownership is an agent skill from LedgerHQ/ledger-live. Maintain CODEOWNERS file and team directories.

When should I use Codeownership?

Codeownership fits situations like: working with /team-/; splitting monolithic files.

How do I install Codeownership in Claude Code?

Run `npx skills add LedgerHQ/ledger-live --skill codeownership -a claude-code`. Or copy the skill folder (.agents/skills/codeownership in LedgerHQ/ledger-live) into .claude/skills/codeownership in your project. Claude Code loads it when a task matches its description.

How do I install Codeownership in Codex?

Run `npx skills add LedgerHQ/ledger-live --skill codeownership -a codex`. Or copy the skill folder (.agents/skills/codeownership in LedgerHQ/ledger-live) into .agents/skills/codeownership in your project. Codex loads it when a task matches its description.

Can I use Codeownership in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LedgerHQ/ledger-live --skill codeownership -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/codeownership, .gemini/skills/codeownership, .github/skills/codeownership and .opencode/skills/codeownership in your project.

What does Codeownership need to run?

Going by SKILL.md and its folder, Codeownership needs JavaScript for the scripts in its folder and the command-line tools its instructions call (node and git). Our summary lists: Node.js.

Does Codeownership access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Codeownership safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Codeownership use?

Codeownership is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Codeownership use?

About 687 tokens (SKILL.md is roughly 2.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Codeownership?

Skills that share tags, products or a category with Codeownership: Deerflow Maintainer Orchestrator (bytedance/deer-flow, 83k stars), Open Source Maintainer Assistant (slopus/happy, 24k stars), Maintainer Review (openai/openai-agents-python, 30k stars) and Brilliant Directories Automation (ComposioHQ/awesome-claude-skills, 77k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Codeownership?

LedgerHQ (a GitHub organization) maintains it in LedgerHQ/ledger-live, which has 621 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 7, 2026.

Source: LedgerHQ/ledger-live on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.