shared-package-validator

Name: shared-package-validator
Availability: InStock
Author: brucetyndall

Validate shared package integrity in monorepos by checking cross-app imports and configuration consistency.

Updated Aug 23, 2026

Search Tags:#code quality #validation #dependencies #configuration #monorepo #packages

Ready to run

npx skills add https://github.com/BruceTyndall/socelle-global --skill shared-package-validator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: shared-package-validator
Source: https://github.com/BruceTyndall/socelle-global/tree/main/.agents/skills/shared-package-validator
Command: npx skills add https://github.com/BruceTyndall/socelle-global --skill shared-package-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures the integrity and consistency of shared packages within a monorepo, preventing common issues like circular dependencies and enforcing shared configuration standards.

Core Features & Use Cases

Package Boundary Validation: Checks for invalid cross-app imports and enforces defined package dependencies.
Configuration Consistency: Verifies that shared configurations (like TypeScript and Tailwind CSS) are applied uniformly across packages.
Use Case: Before merging a new feature that introduces a shared utility, run this Skill to confirm it doesn't violate existing package structures or introduce configuration drift.

Quick Start

Run the shared-package-validator skill to check the integrity of monorepo packages.

Frequently Asked Questions about shared-package-validator

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

FAQPage Schema

How do I validate shared package boundaries and prevent circular dependencies in a monorepo?▼

To validate shared package boundaries in a monorepo, you can run a validation check that detects invalid cross-app imports and enforces defined package dependencies to prevent circular dependency issues. This ensures structural integrity before merging code.

What is the best way to check for configuration drift across monorepo packages?▼

Checking for configuration drift across monorepo packages involves verifying that shared configurations, such as TypeScript and Tailwind CSS, are applied uniformly across all packages to maintain consistency and architectural soundness.

Can I integrate monorepo package validation into a CI/CD pipeline?▼

Yes, you can integrate monorepo package validation into CI/CD pipelines. Running validation checks during CI/CD maintains code quality by ensuring new features do not violate established package structures or introduce configuration drift before deployment.

When do I need to run shared package integrity checks during development?▼

You need to run shared package integrity checks before merging a new feature that introduces a shared utility. This confirms the new code adheres to established package structures and does not introduce configuration inconsistencies.

Does shared package validation work without predefined package structures?▼

No, shared package validation requires adherence to established package structures and shared configuration files. The validation process relies on these predefined boundaries to accurately check cross-app imports and enforce dependency rules.