Skip to content

Install the CLI and skills

Adopting needs no installation: adopt installs and pins its own CLI, as Adopt a standards source describes. Install the CLI yourself for authoring commands or the lower-level inspection and adoption run interface, and install a skill to start adoption or authoring from your coding agent.

Each version’s GitHub release carries its release notes, and its assets carry the publication identities. The CLI installation commands below require the named version to have been published to public npm; a release bundle alone is not publication. Standalone skill installation uses a public Git release tag independently of npm publication.

Use macOS or Linux with Node.js 24 or 26, npm, and Git 2.32 or newer on PATH. Install Node.js 24 or 26 from https://nodejs.org/en/download or select it with your version manager. Author operations may require additional executables and versions; inspection discloses these, and start checks them before changing the project.

The system ps utility must also be on PATH to inspect author process groups after prerequisite probes and operations, and during recovery. Minimal container images may omit it. On Debian/Ubuntu, provide it by installing procps in the image or environment, then retry. An unavailable or failing ps blocks execution with PROCESS_STATE; its diagnostic identifies the inspection failure.

Only stable 24.x and 26.x are supported, with their bundled npm. Node.js 22 is outside the support policy; odd majors, prereleases and future majors are also excluded. Windows, private sources, SSH and Git hosts other than public GitHub are unsupported. Trusted author scripts have normal host and network access; --ignore-scripts disables npm lifecycle scripts, not disclosed author operations.

For authoring commands or the lower-level inspection and adoption run interface, you can install the CLI separately:

Terminal window
npm install --global --ignore-scripts --registry=https://registry.npmjs.org \
@lutzseverino/repo-standards@11.0.1
repo-standards --version
repo-standards source validate /path/to/your/standards-repository --json
repo-standards source search --json

This installs both repo-standards and repo-standards-bootstrap. If your global prefix is not writable, use the external directory installation in inspection. Do not add the CLI to your adopting project’s dependency manifest.

Alternatively download the standalone bootstrap from the matching GitHub release:

Terminal window
mkdir -p "$HOME/.local/bin"
curl --fail --location \
https://github.com/lutzseverino/repo-standards/releases/download/v11.0.1/repo-standards-bootstrap \
--output "$HOME/.local/bin/repo-standards-bootstrap"
chmod 755 "$HOME/.local/bin/repo-standards-bootstrap"

The release also includes SHA256SUMS and release.json identifying its package and bootstrap bytes. The bootstrap requires only Node.js 24 or 26 and npm to obtain the CLI. From a committed adopting project, inspect the public learning source:

Terminal window
repo-standards-bootstrap --cli-version 11.0.1 inspect \
--source https://github.com/lutzseverino/repo-standards-example \
--standards-version v3.0.0 --profile service --json

Use the full bootstrap path if $HOME/.local/bin is not on PATH. Omit --cli-version 11.0.1 to select the greatest published stable version once; stderr discloses the exact selection. Keep that version for start. Inspection does not change project content or run author operations; the only author scripts it runs are read-only remote setup readiness probes. Discovery is optional and is not an endorsement of any source.

The standards format, including remote setup, names no hosting platform: a source’s own probes and fixes decide what a platform needs. Source acquisition is the known blocker to platform independence: it accepts only public github.com sources.

The standalone bootstrap only inspects; to drive inspection and inspect and start directly, retain an external installation of its selected exact CLI for start and recovery.

The product provides three separate skills: adopt-repository-standards starts adoption in an adopting project, author-standards helps publishers author a standards source, and the project-local repository-standards looks up installed rules and reports updates after adoption. Adoption installs only the last of these automatically. repository-standards replaces standards-updates; an update removes the old skill and its Claude link when unedited. Edited old copies stay as project-owned content under the normal retirement policy.

adopt-repository-standards is a single-sentence pointer to adopt, using the standards source you name, with Repo Canon as the fallback. The CLI owns all adopting-agent guidance. The entry command uses npx --yes and adopt --json so npm and a terminal cannot start an interactive conversation. The agent decides what Git can undo and records its decisions in the review handoff; only an unsettled profile choice or a remote setting overwrite needs your answer. See adoption with an agent.

The first public release containing this skill is v8.0.0; that tag contains skills/adopt-repository-standards. The command below selects this release’s matching skill. A tag that predates v8.0.0 cannot install it. Use the same skills CLI route as for authoring:

Terminal window
npx skills@1.5.25 add https://github.com/lutzseverino/repo-standards/tree/v11.0.1/skills/adopt-repository-standards \
--skill adopt-repository-standards --global --agent codex --copy

Global installation makes the skill available before and across adopting projects. Select your supported agent with --agent; codex is the acceptance route. Invoke adopt-repository-standards by name or ask naturally, for example, “Set up shared repository conventions in this repository.” The installation contains only SKILL.md and agents/openai.yaml, with implicit invocation enabled in both settings. The macOS or Linux, Node.js 24, npm, and Git prerequisites above still apply. Installing this skill does not install the CLI or alter a project’s runtime pin; adopt manages its own runtime when invoked.

For unreleased development only, replace the public URL with a local directory containing this skill. That establishes candidate installation, not installation from a published release.

Direct installation is independent of the adoption skill directory page. As with the authoring listing below, the directory FAQ describes discovery through skills CLI installation telemetry. The page appeared after a telemetry-enabled installation from a release tag, as the listing record describes. Record direct release-tag installation separately from a directory observation; listing, indexing time, and ranking are not release guarantees.

The adoption listing’s Socket detail reports a medium supply-chain and instruction-delegation alert: the entry runs an unpinned external CLI, follows its printed instructions, and accepts user-selected remote standards sources. The Snyk detail reports medium W012 for external dependency provenance and runtime instructions it cannot verify. See the recorded audit evidence for the dated observations and comparison with the authoring skill.

These warnings are expected consequences of the adoption design. The entry stays unversioned so the CLI owns the current adoption procedure; --yes avoids npm’s confirmation prompt and --json selects the agent route. Neither report establishes that --yes alone causes the warning, or that removing it would clear one. The skill uses your named source or Repo Canon as the fallback.

You trust the downloaded CLI package, the instructions it prints, and the selected standards source. Adoption pins the exact CLI it runs for subsequent project work; that pin does not verify the package before its first execution or remove supply-chain risk. npm’s --ignore-scripts controls npm lifecycle scripts, not the trusted author operations adoption may run with normal host and network access. See the script trust model for those operations.

Neither WARN proves malicious code. Inferring malware from these intended capabilities would be a false positive; the reported trust risk remains real. This explanation and another skill’s PASS do not guarantee safety. These docs do not change the directory’s badges or appear on the individual skill page, which renders the skill body.

author-standards guides creation, revision, and resumption from confirmed preferences. It finishes with reviewed, validated local material and authoring notes; repository provisioning and standards publication are separate work.

Use the conventional skills CLI to install the skill from the product’s public release tag:

Terminal window
npx skills@1.5.25 add https://github.com/lutzseverino/repo-standards/tree/v11.0.1/skills/author-standards \
--skill author-standards --global --agent codex --copy

The named release must exist before running this command. Global installation is recommended for authors working before or across repositories. Select your supported agent with --agent; codex is the acceptance route. The installation contains SKILL.md and references/cli.md, profiles.md, operations.md, and revision.md. It works independently of a product checkout, adopting project, or surrounding npm package. Invoke author-standards in your agent and describe how you work. Optional references supply candidates for discussion, not policy.

The bundled references/cli.md explains installing the exact compatible npm CLI @lutzseverino/repo-standards@11.0.1 in an external directory, then reading that installation’s matching author format and script protocol documents. Node.js 24 or 26, npm, and registry access are required. Installing the skill does not install its CLI, change an adopting project’s runtime pin, or install authoring into adopting projects. Adoption continues to manage its matching local repository-standards skill independently.

Direct installation is independent of the skills.sh directory. The directory FAQ describes its discovery process; the listing record covers how this page appeared. Listing, indexing time, and ranking are third-party observations, not release guarantees. Record directory observations separately from installation results.

For unreleased development only, replace the public URL with a local directory containing the skill. That is candidate installation, even if its CLI comes from public npm. The acceptance procedure provides isolated installation without changing your real global skills.