azure/build
Build the Cosmos Explorer project. Use this skill when asked to build, compile, or check the build status of the project.
npx skills add https://github.com/Azure/cosmos-explorer --skill build
Use the following commands to build the Cosmos Explorer project. Choose the appropriate command based on the task.
Run a complete production build (format check → lint → compile → strict compile → webpack prod → copy):
npm run build
Run a CI build that uses webpack dev mode for faster bundling:
npm run build:ci
Run a TypeScript type-check without emitting output:
npm run compile
Run a strict null-checks compile on the subset of files in tsconfig.strict.json:
npm run compile:strict
Run ESLint across all .ts and .tsx files:
npm run lint
Run Prettier to verify formatting without modifying files:
npm run format:check
Before running any build command, check whether npm install needs to be run. Do this by comparing package.json and package-lock.json against the installed node_modules:
node_modules directory exists. If it does not, run npm install.node_modules exists, check whether package.json or package-lock.json have been modified more recently than node_modules. If so, run npm install.# Check if node_modules is missing or outdated
if [ ! -d node_modules ] || [ package.json -nt node_modules ] || [ package-lock.json -nt node_modules ]; then
npm install
fi
On Windows PowerShell:
if (-not (Test-Path node_modules) -or
(Get-Item package.json).LastWriteTime -gt (Get-Item node_modules).LastWriteTime -or
(Get-Item package-lock.json).LastWriteTime -gt (Get-Item node_modules).LastWriteTime) {
npm install
}
Always run this check before proceeding with any build command.
npm run build for a full production build.npm run build:ci.npm run compile.npm run compile output.npm run compile:strict output.npm run lint output.npm run format to auto-fix formatting, then retry the build.tsconfig.strict.json so they compile under strict mode.Take azure/build from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.
The instructions reference npm.
Without those the skill loads but fails at the first command.