mcpField
B
bitrix-modules

bitrix-modules

github.com/bxmaximumDevelopment47308 installsUpdated 2w ago
Repository

About bitrix-modules

A module-development reference skill for Bitrix developers, covering module structure, installation migrations, options pages, autoloading, and routes. It highlights registration, repeatable installation, and symmetric uninstall requirements.

Key features

  1. 01Module structure and installer rules
  2. 02Tables, events, and agents in migrations
  3. 03Options pages and PSR-4 autoloading
  4. 04Module routing guidance
  5. 05Symmetric install and uninstall constraints

Use cases

  1. 01Scaffolding a new Bitrix module
  2. 02Writing module install and uninstall logic
  3. 03Configuring options pages and autoloading
  4. 04Troubleshooting module registration and routes

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/bxmaximum/bitrix-framework-skills --skill bitrix-modules

After installing, type/bitrix-modulesin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

rules/
install-migrations.md
installer.md
options-autoload.md

Details

From the project README

Bitrix modules

Baseline: main 23.0+ · Verified: main 26.800.0

TaskRead
New module: id, skeleton, install/index.php, version, lang, uninstallrules/installer.md
Tables, events, agents in install/migrations/*.php (main 26.600+)rules/install-migrations.md
Options page, default_option.php, PSR-4 autoload, module routesrules/options-autoload.md

Invariants

  • Module dir /local/modules/<vendor>.<module>/; id lowercase vendor.module; installer class vendor_module; namespace Vendor\Module (one-word id mymodule → Bitrix\Mymodule).
  • Nothing works until the module is registered in b_module: Loader::includeModule() returns false, and module .settings.php (services, controllers, console, messenger) is not read.
  • Install/uninstall are symmetric: every table, handler, agent and option you create has a removal path; re-running install must not fail.
  • Event registration uses kernel parameter names (fromModuleId:) or positional args; handler signature depends on the dispatcher — bitrix-events.
  • Module routes are required from /local/routes/web.php; a routing section in module .settings.php is ignored (bitrix-routing).
  • Project data/content migrations (iblocks, options per environment) belong to bitrix-sprint-migration, not to the installer.

Comments

Markdown supported