squad-conventions

Standardize Squad CLI code changes with Node.js built-ins and node:test.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/sachinnair90/gitgloss --skill squad-conventions-sachinnair90
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: squad-conventions
Source: https://github.com/sachinnair90/gitgloss/tree/main/.copilot/skills/squad-conventions
Command: npx skills add https://github.com/sachinnair90/gitgloss --skill squad-conventions-sachinnair90

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintain consistent, safe, and cross-platform development practices for the Squad CLI codebase, reducing regressions and inconsistent implementation choices.

Core Features & Use Cases

  • Codebase Conventions: Reinforces the rules for zero dependencies, file structure, and Windows-safe path handling.
  • Testing and Error Handling: Guides contributors to use the built-in Node.js test runner and the standard fatal error pattern.
  • Use Case: When updating Squad source files, follow this Skill to keep behavior aligned with existing init, upgrade, and copy workflows.

Quick Start

Use this Skill to review my Squad code changes and tell me whether they follow the repository’s conventions.

Frequently Asked Questions about squad-conventions

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

FAQPage Schema
How do I enforce Node.js CLI development conventions for consistent code changes?

You can enforce Node.js CLI development conventions by applying rules for zero-dependency built-ins, node:test testing, fatal error handling, and path.join-based portability to ensure consistent code changes.

Does the Squad CLI require any external testing dependencies?

No, the Squad CLI requires zero external dependencies. It mandates using Node.js built-ins and the built-in node:test runner for testing to maintain a lightweight, cross-platform codebase.

How do I handle file paths in a cross-platform Node.js CLI?

Handle file paths in a cross-platform Node.js CLI by using path.join for path construction. This ensures Windows-safe file operations and consistent behavior across different operating systems.

What is the standard error handling pattern for Squad CLI source edits?

The standard error handling pattern for Squad CLI source edits is a fatal error approach. This ensures that critical failures halt execution safely and predictably across the codebase.

How do I manage idempotent initialization and overwrite rules in a Node.js CLI?

Manage idempotent initialization by applying consistent overwrite rules during the CLI init process. This ensures file operations remain safe and predictable across multiple upgrade or copy workflows.