skills.rest
cabloy
cabloyOFFICIAL
Explore all skills by this author →
GitHub

cabloy-module-removal

Remove Cabloy modules from a monorepo with dependency cleanup and verification.

970|131|Updated Jan 14, 2018
Search Tags:#refactoring#cleanup#monorepo#cabloy#zova#vona#module removal
One-click install
npx skills add https://github.com/cabloy/cabloy --skill cabloy-module-removal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cabloy-module-removal
Source: https://github.com/cabloy/cabloy/tree/main/.claude/skills/cabloy-module-removal
Command: npx skills add https://github.com/cabloy/cabloy --skill cabloy-module-removal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers remove Cabloy modules cleanly by coordinating source deletion, dependency cleanup, generated runtime recovery, and verification instead of leaving stale references behind.

Core Features & Use Cases

  • Removal Path Classification: Determines whether a module removal is backend-only, frontend-only, or fullstack based on Cabloy repository structure.
  • Cleanup Workflow Guidance: Guides source-first deletion, workspace dependency updates, regeneration flows, and stale generated artifact recovery.
  • Use Case: When retiring a demo module from a Cabloy monorepo, use this Skill to identify affected Vona and Zova surfaces and verify the module is fully removed from the runtime graph.

Quick Start

Ask the cabloy-module-removal skill to remove the specified Cabloy module and verify that no stale references remain.

Frequently Asked Questions about cabloy-module-removal

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

FAQPage Schema
How do I safely remove a Cabloy module from a monorepo without leaving stale references?▼

Removing a Cabloy module requires classifying the removal scope as backend-only, frontend-only, or fullstack before executing source-first deletion, workspace dependency updates, and generated runtime recovery to ensure no stale references remain.

What is the correct cleanup sequence when retiring a fullstack Cabloy module?▼

The correct cleanup sequence for retiring a fullstack Cabloy module is source-first deletion, followed by workspace dependency updates, generated runtime artifact recovery, and branch-aware validation across Vona and Zova surfaces.

Does removing a Zova frontend module require different steps than removing a Vona backend module?▼

Yes, removing a Zova frontend module versus a Vona backend module requires initial removal path classification, because the backend-only, frontend-only, or fullstack scope directly dictates the distinct dependency cleanup and generated runtime recovery workflows required.

How do I recover generated runtime artifacts after deleting a module from a Cabloy monorepo?▼

Recovering generated runtime artifacts after deleting a Cabloy module involves triggering regeneration flows to restore the runtime graph, ensuring all Vona and Zova dependency surfaces are updated and verified for overall runtime consistency.

Why do stale dependencies remain after deleting a Cabloy module from the workspace?▼

Stale dependencies remain after deleting a Cabloy module when the cleanup workflow skips source-first deletion sequencing or neglects generated artifact recovery, leaving unresolved references within the monorepo runtime graph.

Related Skills

Explore More Software Engineering Skills→
cabloycabloy
970

cabloy-contract-loop

Coordinate Cabloy Vona and Zova synchronization workflows to prevent contract drift.

Official
Advanced
OpentronsOpentrons
515

protocol-verification

Simulates and analyzes Opentrons protocols to verify correctness.

Official
Advanced
eai-toolseai-tools

gofer:bootstrap-workspace

Automate Gofer workspace setup, configuration, and dependency management.

Official
Intermediate
shuremali02shuremali02

repo-navigator

Map monorepo layout to locate frontend, backend, specs, and CLAUDE.md.

Community
Intermediate