adding-a-package

Create a new monorepo package and update ESLint, Knip, and Commitlint configs.

3|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/Avinava/agentic-guardrail-ts --skill adding-a-package-avinava
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adding-a-package
Source: https://github.com/Avinava/agentic-guardrail-ts/tree/main/skills/adding-a-package
Command: npx skills add https://github.com/Avinava/agentic-guardrail-ts --skill adding-a-package-avinava

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates a new workspace package in a monorepo and updates all required config files to preserve architecture boundaries and tooling integrations.

Core Features & Use Cases

  • Scaffold a new package directory with standard project structure (package.json, tsconfig.json, src/index.ts).
  • Automatically assign the correct architecture tier and update ESLint, Knip, and Commitlint configurations.
  • Ensure workspace references, dependencies, and boundary rules are wired correctly to prevent misconfigurations.

Quick Start

Run the monorepo scaffold workflow to add a new package and update all required config files.

Frequently Asked Questions about adding-a-package

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

FAQPage Schema
How do I scaffold a new package in a monorepo and update all the config files?

To scaffold a new monorepo package, run the scaffold workflow to generate the package directory structure and automatically update five essential config files, including ESLint, Knip, and Commitlint.

What is the best way to maintain cross-package consistency when adding a workspace package?

Maintaining cross-package consistency when adding a workspace package requires automatically assigning the correct architecture tier and wiring boundary rules into ESLint, Knip, and Commitlint configurations during the scaffolding process.

Does scaffolding a monorepo package automatically wire workspace references and dependencies?

Yes, scaffolding a monorepo package automatically wires workspace references, dependencies, and boundary rules to prevent misconfigurations and preserve architecture boundaries across the cohesive workspace.

What standard project structure is generated when creating a new monorepo package?

Creating a new monorepo package generates a standard project structure containing package.json, tsconfig.json, and src/index.ts, ensuring cohesive workspace scaffolding across the repository.

Can I use this scaffolding workflow to update Commitlint and ESLint configurations together?

Yes, you can use this scaffolding workflow to update Commitlint and ESLint configurations together, as it automatically wires dependencies and boundary rules across five config files according to project conventions.