dependencies

Manages Composer and Yarn dependencies across OrangeHRM projects inside the Docker dev environment.

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/snow-gift111/orangehrm-ai-sdlc-capstone --skill dependencies-snow-gift111
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dependencies
Source: https://github.com/snow-gift111/orangehrm-ai-sdlc-capstone/tree/main/.agents/skills/dependencies
Command: npx skills add https://github.com/snow-gift111/orangehrm-ai-sdlc-capstone --skill dependencies-snow-gift111

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? OrangeHRM spans multiple Composer projects and Yarn workspaces, and running package-manager commands against the wrong project, wrong PHP version, or wrong package manager causes broken lockfiles and incompatible dependency resolution. This Skill provides the rules and workflows for making dependency changes safely. ## Core Features & Use Cases - Project mapping: Identifies which composer.json or package.json owns a dependency across the main PHP app, dev tools, Vue frontends, and Cypress test workspace. - Version-safe Composer workflow: Resolves dependencies using the lowest supported PHP version from each project's require.php and config.platform settings. - Yarn workspace discipline: Enforces the packageManager field, prevents npm lockfile drift, and keeps manifests and lockfiles committed together. - Use Case: When adding a new PHP package to the OrangeHRM app, the Skill directs you to run composer require inside the Docker container matching the lowest supported PHP version, then commit composer.json and composer.lock together. ## Quick Start Ask the agent to add or update a Composer or Yarn package and it will follow this Skill to run the correct command in the right Docker container and workspace.

Frequently Asked Questions about dependencies

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

FAQPage Schema
How do I add a Composer package to OrangeHRM?

Identify the owning Composer project (src/ for app packages, devTools/core/ for dev tools), read its composer.json for require.php and config.platform, then run composer require inside the Docker container matching the lowest supported PHP version. Commit the manifest and lockfile together.

How do I update frontend dependencies in OrangeHRM Yarn workspaces?

Locate the nearest package.json to find the owning workspace, check its packageManager and engines fields, then run yarn add or yarn install inside the Docker dev environment. Commit the workspace manifest and lockfile together and run the narrowest relevant validation.

Why must Composer run on the lowest supported PHP version?

Resolving dependencies on a newer PHP version can select package versions that do not work on the lowest supported runtime. Reading require.php and config.platform from composer.json determines which Docker PHP container to use for install, update, or require commands.

Can I use npm instead of Yarn in OrangeHRM workspaces?

No, you should use the package manager declared by the workspace package.json packageManager field. Introducing npm lockfiles into Yarn workspaces causes lockfile drift and inconsistent dependency resolution.

Should I hand-edit composer.lock or yarn.lock files?

No, let Composer and Yarn generate lockfile changes. Hand-editing is only acceptable for conflict resolution that cannot be regenerated cleanly, and manifests and lockfiles must always be committed together.