Agent skill

Codebase Context

by homarr-labs in homarr-labs/homarr

Navigate Homarr's monorepo architecture and reuse shared packages.

Apache-2.0Auto-check passedDevelopment

Install Codebase Context

skills CLI
$ npx skills add homarr-labs/homarr --skill codebase-context -a claude-code

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

GitHub CLI
$ gh skill install homarr-labs/homarr codebase-context --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/homarr-labs/homarr.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/codebase-context .claude/skills/codebase-context && 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
codebase-context
GitHub stars
5k
Token cost
~659 tokens
SKILL.md length
258 words
Files
4 (incl. references)
Skills in repo
4
Repo updated
First seen
Licence
Apache-2.0

At a glance

Navigate Homarr's monorepo architecture and reuse shared packages.

  • Works in 5 steps: Confirm the branch and inspect the… → Search @homarr/common before creating a… → Read references/architecture.md when the… → …
  • Choosing a package boundary
  • SKILL.md covers Workflow, Current toolchain and High-value seams
  • Calls pnpm

What it does

Codebase Context is an agent skill from homarr-labs/homarr. Navigate Homarr's monorepo architecture and reuse shared packages. Use when locating code, choosing a package boundary, understanding runtime services, tRPC, databases, widgets, integrations, cron jobs, Custom Widgets, Workshop, or checking @homarr/common before creating a utility.

Its SKILL.md is about 660 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `agents/openai.yaml`, `references/architecture.md` and `references/common.md`).

It sits in Development, covering Codebase knowledge for agents, gRPC and Protobuf and Monorepo tooling. It works with tRPC and Next.js. The repository describes itself as: A modern and easy to use dashboard. 80+ integrations. 20K+ icons built in. Authentication out of the box. No YAML, drag and drop configuration. The licence is Apache-2.0.

When your agent uses it

  • Choosing a package boundary
  • Understanding runtime services
  • Checking @homarr/common before creating a utility

Example prompts

  • “/codebase-context”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Confirm the branch and inspect the nearest package.json, existing sibling modules, and package exports.
  2. Search @homarr/common before creating a general-purpose helper. Read references/common.md for every public entrypoint and export.
  3. Read references/architecture.md when the task crosses packages, runtimes, routing, data, widgets, integrations, cron jobs, Custom Widgets…
  4. Keep the change in the deepest package that owns the behavior. Reuse public entrypoints rather than deep-importing implementation files.
  5. Re-run targeted searches before documenting counts, consumers, or dependency edges; these change faster than the architectural seams.

What it can do on your machine

Read from SKILL.md and the folder at commit 3f02da7. 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

    Shell commands in SKILL.md call:

    • pnpm

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

  • Network

    No URLs in SKILL.md. Its commands use pnpm, 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

Codebase Context loads about 659 tokens when it runs, and up to ~4.3k if it reads all its reference files. Until then it costs about 75 tokens; SKILL.md has 258 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~75
When it runs · the whole SKILL.md, loaded when a task matches
~659
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.3k

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 homarr-labs/homarr at commit 3f02da7, republished under its Apache-2.0 licence (© homarr-labs). 258 words, ~659 tokens.

Download SKILL.mdSave it as .claude/skills/codebase-context/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
codebase-context
description
Navigate Homarr's monorepo architecture and reuse shared packages. Use when locating code, choosing a package boundary, understanding runtime services, tRPC, databases, widgets, integrations, cron jobs, Custom Widgets, Workshop, or checking @homarr/common before creating a utility.

Homarr Codebase Context

Orient from the current checkout before editing. Treat package manifests, exports, and source as authoritative when they differ from this snapshot.

Workflow

  1. Confirm the branch and inspect the nearest package.json, existing sibling modules, and package exports.
  2. Search @homarr/common before creating a general-purpose helper. Read references/common.md for every public entrypoint and export.
  3. Read references/architecture.md when the task crosses packages, runtimes, routing, data, widgets, integrations, cron jobs, Custom Widgets, or Workshop.
  4. Keep the change in the deepest package that owns the behavior. Reuse public entrypoints rather than deep-importing implementation files.
  5. Re-run targeted searches before documenting counts, consumers, or dependency edges; these change faster than the architectural seams.

Current toolchain

  • Use Node 24.18.0 from mise.toml and pnpm 11.15.1 from package.json.
  • Use pnpm workspaces with Turborepo. Workspace packages use the @homarr/ scope and catalog-managed dependencies.
  • Use Next.js App Router, TypeScript, tRPC, Drizzle, Mantine v9, Tabler icons, Jotai, TanStack Query, next-intl, Vitest, and Playwright.
  • Use oxlint and oxfmt. Mantine is the application UI system; Tailwind is limited to the docs app.
  • pnpm dev starts only @homarr/nextjs. Start a standalone runtime explicitly when the task needs it.

High-value seams

  • Server/RSC tRPC: @homarr/api/server
  • Client tRPC hooks: @homarr/api/client
  • Main router: packages/api/src/root.ts
  • MCP eager router: packages/api/src/mcp.ts
  • Database schemas: packages/db/schema/{sqlite,postgresql}.ts
  • Widget registry: packages/widgets/src/registry.ts
  • Widget loading manifest: packages/widgets/src/manifest.ts
  • Integration definitions: packages/definitions/src/integration.ts
  • Integration factory: packages/integrations/src/base/creator.ts
  • Cron jobs: packages/cron-jobs/src/jobs/
  • App routes: apps/nextjs/src/app/[locale]/

Invoke documentation-sync only when users need new or corrected information to set up, use, or troubleshoot Homarr; follow the Documentation Sync criteria in AGENTS.md. When exposing tRPC through MCP, invoke mcp-integration.

© homarr-labs, Apache-2.0. 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 3 other files (references) in .agents/skills/codebase-context of homarr-labs/homarr.

  • SKILL.md
  • agents/openai.yaml
  • references/architecture.md
  • references/common.md

Open the folder on GitHubat commit 3f02da7

Compare with similar skills

Codebase Context 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.

Codebase Context compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Codebase Context this skillhomarr-labs/homarr5k—~659Automated safety check: PassApache-2.0
Workspacealinaqi/maggy707—~7.3kAutomated safety check: PassMIT
LobeHub Project Maplobehub/lobehub83k—~1.8kAutomated safety check: PassCustom licence
Trpcmajiayu000/claude-skill-registry6661 repos~595Automated safety check: NotesMIT
Yjs Nextjspproenca/dot-skills214—~2.6kAutomated safety check: PassMIT
Backend Dev Guidelineslitefuse/litefuse1001 repos~5.8kAutomated safety check: PassCustom licence

Similar skills

  • Workspace

    alinaqi/maggy

    Dynamic multi-repo and monorepo awareness for Claude Code. An agent skill from alinaqi/maggy.

    707 GitHub stars~7.3k tokensUpdated 13 days ago
    DevelopmentAuto-check passed
  • LobeHub Project Map

    lobehub/lobehub

    A map of the LobeHub open-source repository: tech stack, monorepo layout, where each code layer lives and who owns apps, packages and src.

    83k GitHub stars~1.8k tokensUpdated today
    DevelopmentAuto-check passed
  • Trpc

    majiayu000/claude-skill-registry

    tRPC end-to-end type safety, procedures, routers, middleware, and React integration.

    666 GitHub starsUsed in 1 repo~595 tokens
    Backend & APIsAuto-check: notes
  • Yjs Nextjs

    pproenca/dot-skills

    Corrects the wrong defaults a capable model has when building Yjs collaborative editing into a Next.js 16 App Router app with tRPC v11 and shadcn/ui — pinned to Yjs 13.6.31.

    214 GitHub stars~2.6k tokensUpdated 1 mo ago
    Backend & APIsAuto-check passed
  • Backend Dev Guidelines

    litefuse/litefuse

    Comprehensive backend development guide for Litefuse's Next.js 14/tRPC/Express/TypeScript monorepo.

    100 GitHub starsUsed in 1 repo~5.8k tokens
    Backend & APIsAuto-check passed
  • Tnr Dev Server

    studie-tech/TheNinjaRPG

    Run a TheNinjaRPG dev server locally from any git worktree, provision disposable test users, and call tRPC endpoints as those users.

    104 GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check: notes

More from homarr-labs/homarr

  • Documentation Sync

    homarr-labs/homarr

    Write Homarr docs only when users need information to set up, use, or troubleshoot the app.

    5k GitHub stars~1k tokensUpdated today
    Auto-check passed
  • MCP Integration

    homarr-labs/homarr

    Expose Homarr tRPC procedures safely through MCP. An agent skill from homarr-labs/homarr.

    5k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Homarr Custom Widget

    homarr-labs/homarr

    Author, validate, preview, test, install, or configure API-backed Homarr Custom JSX v2 widgets.

    5k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

Works with

Questions about Codebase Context

What does Codebase Context do?

Navigate Homarr's monorepo architecture and reuse shared packages. Codebase Context is an agent skill from homarr-labs/homarr. Navigate Homarr's monorepo architecture and reuse shared packages.

When should I use Codebase Context?

Codebase Context fits situations like: choosing a package boundary; understanding runtime services; checking @homarr/common before creating a utility.

How do I install Codebase Context in Claude Code?

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

How do I install Codebase Context in Codex?

Run `npx skills add homarr-labs/homarr --skill codebase-context -a codex`. Or copy the skill folder (.agents/skills/codebase-context in homarr-labs/homarr) into .agents/skills/codebase-context in your project. Codex loads it when a task matches its description.

Can I use Codebase Context 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 homarr-labs/homarr --skill codebase-context -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/codebase-context, .gemini/skills/codebase-context, .github/skills/codebase-context and .opencode/skills/codebase-context in your project.

What does Codebase Context need to run?

Going by SKILL.md and its folder, Codebase Context needs the command-line tools its instructions call (pnpm).

Does Codebase Context access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Codebase Context 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 Codebase Context use?

Codebase Context is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Codebase Context use?

About 659 tokens (SKILL.md is roughly 2.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.7k tokens, read only when the agent opens those files.

What are the alternatives to Codebase Context?

Skills that share tags, products or a category with Codebase Context: Workspace (alinaqi/maggy, 707 stars), LobeHub Project Map (lobehub/lobehub, 83k stars), Trpc (majiayu000/claude-skill-registry, 666 stars) and Yjs Nextjs (pproenca/dot-skills, 214 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Codebase Context?

homarr-labs (a GitHub organization) maintains it in homarr-labs/homarr, which has 5,018 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 7, 2026.

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