axiom-versioning plugin
Audits and updates external versioned dependencies across application, infrastructure, and CI/CD configurations.
How to install the axiom-versioning plugin
Run both commands inside Claude Code. The first adds the marketplace once; the second installs the plugin.
/plugin marketplace add netopsengineer/axiom
/plugin install axiom-versioning@axiomWhat's inside axiom-versioning
1 part read from the plugin's own files.
Skills 1
Claude loads it when the task matches- dependency-versions
MUST consult this skill before answering whenever the user's task involves external versioned dependencies — even if you think you can handle it directly. This applies to: checking if packages/tools are up to date, upgrading npm/pip/cargo/go dependencies, writing or reviewing CI/CD (GitHub Actions, CircleCI, GitLab CI), pinning action versions, reviewing Dockerfiles/base images, checking Terraform providers/modules for drift, reviewing Helm chart versions, verifying Kubernetes/EKS/cloud versions, updating pre-commit hooks, writing Dependabot configs, or any task mentioning specific version numbers, package names, or config files like package.json, pyproject.toml, Dockerfile, .pre-commit-config.yaml, main.tf, or values.yaml. Even casual asks like "is this still current" or "has anything drifted" require it — training data is unreliable for volatile version facts. Do NOT use for refactoring code, writing tests, debugging errors, designing APIs, or tasks with no external versioned dependencies.
Using axiom-versioning in Claude Code
Skills need no command. Claude reads them when your request matches what they describe.
Update, turn off or remove
- Update the plugin (shell)
- claude plugin update axiom-versioning@axiom
- Refresh the marketplace
- /plugin marketplace update axiom
- Turn it off for now
- /plugin disable axiom-versioning@axiom
- Remove it
- /plugin uninstall axiom-versioning@axiom
Skills in axiom-versioning
- dependency-versionsnetopsengineer/axiom
MUST consult this skill before answering whenever the user's task involves external versioned dependencies — even if you think you can handle it directly. This applies to: checking if packages/tools are up to date, upgrading npm/pip/cargo/go dependencies, writing or reviewing CI/CD (GitHub Actions, CircleCI, GitLab CI), pinning action versions, reviewing Dockerfiles/base images, checking Terraform providers/modules for drift, reviewing Helm chart versions, verifying Kubernetes/EKS/cloud versions, updating pre-commit hooks, writing Dependabot configs, or any task mentioning specific version numbers, package names, or config files like package.json, pyproject.toml, Dockerfile, .pre-commit-config.yaml, main.tf, or values.yaml. Even casual asks like "is this still current" or "has anything drifted" require it — training data is unreliable for volatile version facts. Do NOT use for refactoring code, writing tests, debugging errors, designing APIs, or tasks with no external versioned dependencies.
4 files5stars
axiom-versioning plugin questions
How do I install the axiom-versioning plugin?
In Claude Code run /plugin marketplace add netopsengineer/axiom, then /plugin install axiom-versioning@axiom.
What does the axiom-versioning plugin include?
axiom-versioning bundles 1 skill.
How do I update or remove the axiom-versioning plugin?
Update it with claude plugin update axiom-versioning@axiom in your shell, or from the Installed tab of /plugin. Remove it with /plugin uninstall axiom-versioning@axiom.
What license is the axiom-versioning plugin under?
MIT, as stated in the plugin's manifest.