cit-data-practice-cli

A friendly, cross-platform command-line tool that installs and manages the CI&T Data Practice team's private Claude Code plugins — without needing GitHub access. You sign in once in your browser and you're ready to go.

The user-facing command is cit-data-practice-cli. Works on Windows, macOS, and Linux.

Install

Requires Node.js 20 or newer (nodejs.org).

npm install -g cit-data-practice-cli

Sign in

cit-data-practice-cli auth login

Your browser opens, you sign in with your @ciandt.com account, and you're authenticated. That's it.

cit-data-practice-cli auth status         # check who you're signed in as
cit-data-practice-cli auth login --force  # re-authenticate (e.g. switch account)

There's no logout: your token is shared with the plugin's telemetry, so removing it would stop telemetry. Access is revoked server-side if ever needed.

Install, update, remove plugins

Run with no subcommand to open the interactive home (it signs you in first if needed):

cit-data-practice-cli

The home lists the available plugins with their state (installed version, and an X→Y badge when an update exists). Move with the arrow keys and press Enter to open a plugin's Actions screen — the obvious action (Install · latest / Update / Reinstall) is preselected and marked recommended, so the latest stable is an Enter, Enter install. That screen also offers Uninstall (with confirmation) and Other versions…, an opt-in picker of every release (latest/prerelease tags) and test branches. Choosing a specific version pins it (no more auto-update prompts); the Update action goes back to following the latest stable. r refreshes the home, q quits.

Installs are delegated to the Claude Code CLI (claude) via a local marketplace — so it works the same on Desktop, VS Code, and terminal, with no GitHub access. claude is a prerequisite; if it's missing, the home offers to run the official installer. After any change, run /reload-plugins in Claude Code (or restart it) for it to take effect.

Already installed via GitHub? The first run detects it and does a one-time, safe migration to the CLI-managed install (install-then-remove, so a failure leaves your existing install intact). Your sign-in and telemetry are kept.

Staying up to date

The CLI updates itself. When you open it, it checks whether a newer version was published and installs it where it can, restarting into the new version — nothing to remember, nothing to type.

Where it can't (your Node was installed system-wide and the global folder needs sudo, or volta/pnpm owns the install), it says so and prints the exact command. That's a notice, not a wall — you can keep going.

To turn the automatic part off:

export DP_CLI_NO_AUTO_UPDATE=1     # macOS / Linux
setx DP_CLI_NO_AUTO_UPDATE 1       # Windows, new terminals

It will still mention new versions; it just won't install them. One exception stays in force either way: if the backend raises the minimum supported version and yours is below it, the CLI stops and shows you how to update — a version that can no longer talk to the backend correctly fails in ways that are much harder to diagnose.

The plugin stays current too

If you follow the stable version, the CLI installs new plugin releases for you when you open it, and tells you it did. Then run /reload-plugins in Claude Code — that last step is the one the CLI cannot do for you.

If you pinned a version or chose a test branch through "Other versions…", it is left exactly as you set it. That was a decision, and the automation does not undo decisions; it just shows the badge on the home.

DP_CLI_NO_AUTO_UPDATE switches off both this and the CLI's own update — one intent, one switch.

Documentation

For everyone — the hosted docs portal:

| | English | Português | Español | |---|---|---|---| | Getting started | en | pt | es | | CLI guide | en | pt | es |

For maintainers — technical docs in the repo: architecture · development · contract.

Part of the CI&T Data Practice. Sibling repos: data-practice (the plugin) and data-practice-api (the backend).