commandbox-package-management

Automates management of CFML/BoxLang packages via ForgeBox, Git, and HTTP.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/ortus-boxlang/skills --skill commandbox-package-management-ortus-boxlang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commandbox-package-management
Source: https://github.com/ortus-boxlang/skills/tree/main/commandbox/commandbox-package-management
Command: npx skills add https://github.com/ortus-boxlang/skills --skill commandbox-package-management-ortus-boxlang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CommandBox package management for CFML/BoxLang projects, enabling configuration via box.json, installation from ForgeBox, Git, HTTP, or local folders, and streamlined publishing and versioning workflows.

Core Features & Use Cases

  • Configure and manage box.json metadata for projects
  • Install, update, and publish packages from ForgeBox or remote endpoints
  • Handle dependencies, devDependencies, and lock files across environments
  • Create and publish new packages to ForgeBox and manage private packages
  • Support semantic versioning and integrated scripting hooks in package workflows

Quick Start

Create a box.json at your project root and run the install flow to fetch dependencies.

Frequently Asked Questions about commandbox-package-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage CFML and BoxLang package dependencies using ForgeBox?

You can manage CFML and BoxLang package dependencies using ForgeBox by configuring a box.json file at your project root and running an automated install flow to fetch, update, and lock project dependencies across environments.

What is the best way to publish a new package to ForgeBox and handle semantic versioning?

Publishing a new package to ForgeBox with semantic versioning involves configuring your box.json metadata and executing a streamlined publishing workflow that updates version numbers and deploys the package from development to production endpoints.

Can I install CommandBox packages from Git repositories or HTTP endpoints instead of ForgeBox?

Yes, you can install CommandBox packages directly from Git repositories, HTTP endpoints, or local folders, allowing flexible dependency sourcing while maintaining consistent box.json configuration and lock file handling across your development environments.

Does box.json support devDependencies and script hooks for automated package workflows?

Yes, box.json supports devDependencies and integrated scripting hooks, enabling you to automate package workflows and separate development dependencies from production requirements throughout the CommandBox lifecycle.

How do lock files work when updating CommandBox dependencies across different environments?

Lock files handle dependency resolution by locking package versions during installation, ensuring consistent updates and preventing version drift when you move CommandBox projects across development and production environments.