squad-conventions Skill

Source

• Creator: microsoft
• Repository: microsoft/frontier-agentic-devops-rvas
• Skill file: .copilot/skills/squad-conventions/SKILL.md

What it does

Core conventions and patterns used in the Squad codebase

Skill instructions

Context These conventions apply to all work on the Squad CLI tool (create-squad). Squad is a zero-dependency Node.js package that adds AI agent teams to any project. Understanding these patterns is essential before modifying any Squad source code. Patterns Zero Dependencies Squad has zero runtime dependencies. Everything uses Node.js built-ins (fs, path, os, childprocess). Do not add packages to dependencies in package.json. This is a hard constraint, not a preference. Node.js Built-in Test Runner Tests use node:test and node:assert/strict — no test frameworks. Run with npm test. Test files live in test/. The test command is node --test test/. Error Handling — fatal() Pattern All user-facing errors use the fatal(msg) function which prints a red ✗ prefix and exits with code 1. Never throw unhandled exceptions or print raw stack traces. The global uncaughtException handler calls fatal() as a safety net. ANSI Color Constants Colors are defined as constants at the top of index.js: GREEN, R