Tools

Supported does not
mean replaced.

xops supports tools by detecting them, reporting their state, routing commands to the right native owner, bootstrapping seamless user-space CLIs when safe, and creating approved setup plans for everything else. Each tool remains the owner of its own domain.

Seamless tools

One command surface.
Every native tool, still in charge.

You should not have to remember which CLI owns the next step. Say what you want, and xops figures out who owns the job — npm, git, GitButler, a test runner, a release flow — bootstraps catalog-marked seamless tools when safe, and hands risky setup to you with a clear plan instead of guessing.

You say"show parallel branches"
→
xops
→
Already installed → routes straight to GitButler
Safe to add → bootstraps the CLI, no setup step for you
Risky setup → hands you a plan instead of a guess
The edge is not tool replacement. The edge is reliable tool ownership through one repo-aware command surface.
Package managers
npmpnpmyarn

xops does

  • detect lockfiles and packageManager field
  • route scripts through the detected package manager
  • use npm for npm-registry operations where appropriate
  • report conflicts between lockfiles

xops does not

  • replace package resolution
  • silently install another package manager
Source control and repo hosting
gitGitButlerGitHub remotesGitLab remotesBitbucket remotes

xops does

  • detect status, branch, remotes, ahead/behind
  • detect GitButler CLI availability
  • recommend GitButler for agent-heavy or multi-package Git workflows
  • expose branch workflow actions as xops repo and agent commands, bootstrapping the user-space CLI when safe
  • route branch workflow diff/show, pull checks, lane apply/unapply, absorb, reword, move, squash, and review operations
  • commit/push only when requested
  • show remote divergence and recovery plans

xops does not

  • replace GitButler branch orchestration
  • run GitButler repo or account setup silently
  • rewrite history silently
  • force push silently
  • create remotes silently
Monorepo / workspace
npm workspacespnpm workspacesyarn workspacesTurborepoNxRushWireitmoon

xops does

  • detect workspace layout
  • build package graph
  • compute affected packages
  • run package operations in dependency order
  • respect existing monorepo runners

xops does not

  • replace Turbo/Nx/Rush
  • force a monorepo structure
Testing
VitestJestPlaywrightCypressSupertest

xops does

  • detect configs, dependencies, scripts
  • prefer existing package scripts
  • run unit/integration/API/e2e/affected tests
  • recommend missing test setup only when evidence supports it

xops does not

  • invent test commands when scripts/configs are ambiguous
  • recommend Playwright for backend-only packages
  • recommend Supertest for frontend-only packages
Quality
TypeScriptESLintPrettierBiomeOxlinttsxHuskylint-stagedLefthook

xops does

  • detect quality tools
  • run lint/format/typecheck/precommit flows
  • prefer existing scripts
  • recommend missing scripts/config only when useful

xops does not

  • add competing linters by default
  • rewrite configs silently
Repo hygiene
Knipdependency-cruiserSherifSyncpackast-grep

xops does

  • detect configs and installed versions for each tool
  • run existing repo-hygiene scripts
  • normalize unused-code, unused-dependency, dependency-graph-rule, monorepo-config-drift, and version-misalignment findings into xops issues
  • recommend a missing tool only when evidence supports it

xops does not

  • delete unused code or dependencies without approval
  • rewrite dependency versions silently
  • add a repo-hygiene tool that is not already configured
Release
xops release stacksChangesetssemantic-releaserelease-pleaserelease-itnpm-check-updates

xops does

  • detect release ownership
  • integrate release status
  • detect conflicts
  • run xops-managed release stacks when configured

xops does not

  • duplicate version bumps
  • guess between release owners
Package publishing safety
PublintAre The Types Wrongpkgrollnpm pack --dry-runlicense-checker-rseidelsohn

xops does

  • run npm pack --dry-run --json as a built-in publish-safety check
  • detect Publint and Are The Types Wrong and run them when configured
  • report ESM/CJS, exports-map, and package-correctness issues
  • report license state via license-checker-rseidelsohn when present

xops does not

  • skip the built-in pack check when these tools are missing
  • replace pkgroll as the bundler
  • claim package correctness without running the check
Dependency monitoring
RenovateDependabot

xops does

  • detect config
  • report schedules/groups/ecosystems
  • evaluate dependency update PR risk
  • recommend one provider only when both are missing

xops does not

  • install or configure bots silently
  • recommend a second bot when one is already active
Security
xops built-in checksnpm auditpnpm auditSnykTrivyGitHub Advanced Security / CodeQLlicense scanningSBOM

xops does

  • run built-in tarball and publish safety checks
  • detect scanners
  • normalize security findings
  • include required scanners in release gates when configured

xops does not

  • require paid/external scanners by default
  • claim GitHub-side security settings are enabled unless verifiable
Secrets and config
.env.env.example.npmrcDopplerVaultAWS Secrets Manager1Passwordutilitix secret aliasesCI secretsSecretlintGitleaksdotenvx

xops does

  • detect providers
  • detect Secretlint and Gitleaks and run them when configured
  • validate required env names
  • redact secret values
  • check that sensitive files are not published

xops does not

  • print secrets
  • store raw secrets
  • copy secrets between providers
  • unlock vaults during status
AI context
xops ai-packRepomix

xops does

  • generate AI-safe context bundles via the built-in ai-pack command
  • detect Repomix as a complementary context generator
  • include the package graph and latest xops issues in generated context
  • exclude ignored and secret-bearing files from the bundle

xops does not

  • dump the whole monorepo into context by default
  • include .env or other secret-bearing files in generated context
CI
GitHub ActionsGitLab CICircleCIJenkins

xops does

  • detect CI files
  • report xops usage in CI
  • recommend xops validation/dependency/API jobs when relevant
  • create workflows only after approval

xops does not

  • create CI workflows silently
  • claim remote CI settings are configured from local files alone
API operations
PostmanNewmanOpenAPI / SwaggerSwagger UIRedocBrunoInsomnia

xops does

  • detect API collections/specs
  • detect Newman runner
  • run existing API test scripts
  • recommend Newman when Postman collections exist but no runner exists
  • validate OpenAPI when supported
  • report Bruno/Insomnia collections

xops does not

  • require Postman SaaS for local collection workflows
  • create SaaS accounts
  • recommend unsupported runners
Documentation
DocusaurusStorybookTypeDoc

xops does

  • detect docs tools
  • run existing docs build scripts
  • recommend docs CI only when docs tooling exists

xops does not

  • recommend documentation frameworks generically
Containerization
DockerDocker Compose

xops does

  • detect Dockerfile and compose files
  • report container build scripts
  • recommend .dockerignore when Dockerfile exists and .dockerignore is missing
  • connect Docker presence to security scan recommendations

xops does not

  • recommend Docker for every app
Deployment
VercelNetlifyRenderRailwayFly.ioAWSGCPAzureKubernetesHelm

xops does

  • detect deployment config files and env var names
  • report deploy status
  • validate required env names when configured

xops does not

  • create cloud accounts
  • deploy silently
  • recommend cloud providers generically
Observability
SentryOpenTelemetryDatadogPrometheusGrafana

xops does

  • detect SDKs/config/env names
  • report observability status
  • recommend release/env validation when evidence exists

xops does not

  • recommend observability vendors generically
Performance and debugging
Clinic.js0xwhy-is-node-runningautocannonhyperfine

xops does

  • detect these tools when installed
  • run existing profiling/benchmark/load-test scripts
  • report status via the built-in performance, benchmark, and load-test commands

xops does not

  • install profilers or load-testers automatically
  • run load tests against a remote or production target without explicit confirmation
Metadata and Mongo operations
MaGitutilitixMongo usage classifier

xops does

  • classify Mongo usage
  • recommend MaGit only for Mongo-backed metadata/config/deploy state
  • recommend utilitix only for Mongo backup/restore/replication/compare workflows
  • route MaGit operations to MaGit
  • route Mongo utility operations to utilitix

xops does not

  • use utilitix as a MaGit replacement
  • recommend MaGit for generic runtime Mongo usage
  • recommend utilitix just because Mongo exists