Operations

Your repo has tools.
xops gives them a contract.

xops detects the supported tools in your Node.js repo — package managers, git, workspaces, tests, quality checks, release tools, dependency monitoring, security scanners, secrets, CI, API assets, MaGit, utilitix, Docker, deployment, and observability — then turns that state into safe next commands for humans and code agents.

The operating layer

The repository
became the workflow.

A modern Node.js repo is not operated by one tool. It is operated through package managers, git, workspaces, tests, quality checks, release tools, dependency bots, security scanners, secret providers, CI workflows, API collections, metadata stores, Docker files, deployment configs, observability hooks, and code agents trying to run all of it without getting stuck.

xops turns that scattered toolchain into one operating surface. It does not replace the tools — it detects them, understands what they own, runs them in the right context, explains what is safe, refuses what needs approval, and records what happened.

Release is the proof: xops already made multi-package publish work deterministic. Operations applies that same contract to the rest of the repo.

Start read-only

The current state,
not a guess.

xops ops status is the map of the repo. It does not install anything, write configs, initialize tools, or connect services. It reads the repository and reports what exists, what is missing, and which next commands are safe.

Detected areas

Package manager
Source control
Repo hosting
Workspace / monorepo
Tests
Quality
Release
Dependency monitoring
Security
Secrets/config
CI
API operations
MaGit
utilitix
Mongo usage
Docker
Deployment
Observability
Agent readiness
xops ops status
$ xops ops status $ xops ops status --json --agent ✓ npm workspaces detected ✓ git remote: github.com/acme/api ✓ Vitest configured ✓ ESLint + Prettier active ! No dependency monitoring detected ! Postman collection found, no runner → see: xops recommendations

Native ownership

Every tool
keeps its job.

xops does not make the toolchain disappear. npm still installs. git still stores history. GitButler still owns branch workflow operations. Renovate and Dependabot still manage dependency updates. Vitest and Playwright still run tests. MaGit still owns Mongo metadata versioning. utilitix still owns Mongo utility operations. xops connects them into one operating contract.

One operation, two audiences

A human needs an explanation.
An agent needs a contract.

xops returns both.

human mode
$ xops ops status Explains what exists, what is safe, and what to do next.
agent mode
$ xops ops status --json --agent Returns structured data, findings, risks, approval requirements, and exact next commands.