basercms-core-plugin-convert

Convert standalone baserCMS plugins into monorepo core plugins.

194|141|Updated Feb 12, 2012
One-click install
npx skills add https://github.com/baserproject/basercms --skill basercms-core-plugin-convert
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: basercms-core-plugin-convert
Source: https://github.com/baserproject/basercms/tree/main/.agents/skills/basercms-core-plugin-convert
Command: npx skills add https://github.com/baserproject/basercms --skill basercms-core-plugin-convert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a standalone baserCMS plugin into a monorepo-ready core plugin, removing the friction of nested repositories, duplicated test setups, and mismatched package metadata.

Core Features & Use Cases

  • Core-Plugin Conversion: Renames and restructures plugins to follow baserCMS core conventions such as the bc- prefix, PascalCase namespaces, and baserproject package naming.
  • Monorepo Integration: Removes standalone artifacts and registers the plugin in root-level Git ignore rules, Composer metadata, PHPUnit suites, PHPDoc paths, and split-repository configuration.
  • Operational Deployment: Supports scenarios where a third-party plugin must be promoted into baserCMS core, aligned with shared test infrastructure, and prepared for split-to-read-only repository publishing.

Quick Start

Ask this Skill to convert a specific baserCMS plugin directory into a core plugin and return the exact file, config, and naming changes needed for monorepo integration.

Frequently Asked Questions about basercms-core-plugin-convert

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

FAQPage Schema
How do I convert a standalone baserCMS plugin into a monorepo core plugin?▼

To convert a standalone baserCMS plugin into a monorepo core plugin, rename packages with the bc- prefix, remove standalone artifacts, and wire the plugin into root-level test, autoload, and deployment configuration.

What does promoting a plugin to baserCMS core require in composer and PHPUnit configuration?▼

Promoting a plugin to baserCMS core requires updating composer metadata, PHPUnit bootstrap, and corePlugins settings to align the standalone plugin with the shared monorepo test infrastructure.

When do I need to update split_monorepo registration and .gitignore for baserCMS plugins?▼

You need to update split_monorepo registration and .gitignore when integrating a promoted baserCMS core plugin to prepare it for split-to-read-only repository publishing and remove standalone repository friction.

Does converting a baserCMS plugin to a core plugin change namespaces and phpdoc paths?▼

Yes, converting a baserCMS plugin to a core plugin applies PascalCase namespaces, baserproject package naming, and updates phpdoc paths while preserving compatibility throughout the monorepo integration.

Can I use this plugin conversion process for third-party plugins outside the baserproject namespace?▼

Yes, the conversion process supports scenarios where a third-party plugin must be promoted into baserCMS core, aligning it with shared test infrastructure and root-level deployment configuration.

Why does monorepo integration remove standalone artifacts from baserCMS plugins?▼

Monorepo integration removes standalone artifacts from baserCMS plugins to eliminate duplicated test setups and nested repositories, restructuring the plugin to follow core conventions safely.