Menu
Use when working on Gentoo ebuilds, overlays, eclasses, Manifest files, metadata.xml, pkgdev, pkgcheck, ebuild QA, version bumps, new packages, package reviews, or Gentoo package pull requests.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Unavailable archived skill. Do not use to initialize, continue, repair, or manage long-running projects across sessions; retained only for historical reference and postmortem analysis.
Evidence-backed visual repository analysis for understanding codebases, creating concise Mermaid architecture/flow diagrams, mapping components and runtime/data paths, identifying hotspots, and producing repository-informed improvement opportunities. Use when the user asks to analyze a repository, understand a codebase, generate architecture diagrams, create a visual repo report, find high-value improvement directions, or prepare context for later design/planning work.
Use across bugs, code changes, reviews, architecture, product decisions, writing, research, and general problem solving when the user presents a visible issue, example, proposal, or decision. MUST apply Locez Lens as a lightweight scope and judgment calibration before answering or changing anything.
Use when creating or refactoring a skill for a complex multi-step task, especially when an existing skill has an overloaded main prompt, unclear sub-agent responsibilities, repeated human confirmations, missing intermediate artifacts, weak validation, or a need to turn domain-specific work such as data cleaning into a structured workflow skill.
Use when bumping, removing, or reconciling nvchecker-tracked packages in locez-overlay, especially when deciding whether a package is release-managed, live-only, or no longer maintained
Use when handling Portage conflicts, @world upgrades, /etc/portage cleanup, binpkg tradeoffs, or deciding where Gentoo maintenance rules and local host preferences should live
| name | gentoo-ebuild |
| description | Use when working on Gentoo ebuilds, overlays, eclasses, Manifest files, metadata.xml, pkgdev, pkgcheck, ebuild QA, version bumps, new packages, package reviews, or Gentoo package pull requests. |
Use this as the entry point for Gentoo package maintenance. Classify the task, load only the needed reference files, work from repository/local/official evidence, and validate with native Gentoo tools. This skill is not a replacement for target repository policy.
AGENTS.md, README*, CONTRIBUTING*, PR templates, and CI config.references/workflow.md before task-specific references.references/semantic-generation.md, references/domain-routing.md, and references/shell-idioms.md, then load only the matching domain references.LICENSE/COPYING files as a content decision, not automatic
install inputs: set LICENSE= from the licenses that apply to installed or
used content, but ship the upstream text with dodoc/DOCS only when it
explains component-to-license mapping, third-party attribution/notices,
special terms, or other user-relevant information that metadata alone does
not provide.inherit collects eclass assignments in E_DEPEND, E_RDEPEND,
E_BDEPEND, and related channels before appending them to the final metadata.
Do not duplicate eclass-owned dependencies or use BDEPEND="${BDEPEND}" as
a preservation mechanism.pkgdev, pkgcheck, ebuild, emerge, git, gh, nvchecker when relevant.references/workflow.md first.references/semantic-generation.md, references/domain-routing.md, and references/shell-idioms.md.references/new-package.md.references/version-bump.md.references/eclass-discovery.md.references/qa.md.references/commit-pr.md./var/db/repos/gentoo./var/db/repos/gentoo/eclass/*.eclass.If evidence conflicts, state the conflict and prefer the current, local, package-specific source unless official Gentoo guidance clearly overrides it.
Common-frequency patterns are discovery signals, not universal rules. A common eclass is a default only when the package's source and runtime profile matches the behavior that eclass owns.
Use these directly unless repository policy says otherwise. Resolve the bundled helper path from this skill directory; do not assume the target repository contains a copy of the script.
python3 <gentoo-ebuild-skill>/scripts/ensure_copyright_year.py --fix path/to/package-version.ebuild
pkgdev manifest category/package
pkgcheck scan category/package
ebuild category/package/package-version.ebuild clean compile install
pkgcheck scan --commits --net
pkgdev commit
Adjust commands to repository policy and local permissions.