soclix

Coordinate cross-app impact analysis and migration planning for Unanima shared packages.

1|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/dduquenne/unanima-platform --skill soclix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: soclix
Source: https://github.com/dduquenne/unanima-platform/tree/main/.claude/skills/soclix
Command: npx skills add https://github.com/dduquenne/unanima-platform --skill soclix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Soclix acts as the guardian of the shared monorepo core packages, ensuring consistency, stability, and retrocompatibility across multiple apps.

Core Features & Use Cases

  • Enforces cross-app compatibility for shared packages (@unanima/core, @unanima/auth, @unanima/db, @unanima/dashboard, @unanima/email, @unanima/rgpd).
  • Performs impact analysis and coordinates migrations with ADRs and changelog documentation.
  • Coordinates PR and CI gating to protect three apps during socle changes.

Quick Start

Begin by activating Soclix to oversee changes to the shared packages before implementation.

Frequently Asked Questions about soclix

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

FAQPage Schema
How do I prevent breaking changes in a shared monorepo package?

To prevent breaking changes in a shared monorepo package, you need cross-app impact analysis and retrocompatibility enforcement. This involves coordinating migrations, documenting architecture decision records, and gating pull requests to protect dependent applications before modifying shared code.

What is cross-app impact analysis for shared packages?

Cross-app impact analysis for shared packages assesses how modifying a core library affects all dependent applications within a monorepo. It ensures stability by enforcing retrocompatibility, planning migrations, and documenting architectural decisions before implementation.

How do I ensure retrocompatibility when updating a monorepo socle?

Ensuring retrocompatibility when updating a monorepo socle requires coordinating cross-app impact assessments and enforcing CI gating. You must document architecture decision records and plan migrations before applying any shared-package modifications to prevent breaking dependent apps.

Can I use ADR documentation for monorepo migration planning?

Yes, you can use architecture decision record documentation for monorepo migration planning. It records architectural decisions, coordinates cross-app impact analysis, and ensures retrocompatibility before modifying shared packages across multiple dependent applications.

Does CI gating work for protecting shared packages across multiple apps?

Yes, continuous integration gating works for protecting shared packages across multiple apps. It coordinates pull request approvals and enforces cross-app impact analysis to ensure retrocompatibility and prevent breaking changes during shared monorepo modifications.

Why do shared monorepo packages break dependent applications?

Shared monorepo packages break dependent applications when modifications lack cross-app impact analysis and retrocompatibility enforcement. Coordinating migrations, documenting architecture decision records, and implementing continuous integration gating prevents these breaking changes across the shared codebase.