How do I install the Processwire Rockmigrations skill?

Run npx skillmds@latest add tomevault-io/processwire-rockmigrations in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Processwire Rockmigrations safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Processwire Rockmigrations?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Processwire Rockmigrations free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Processwire Rockmigrations?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Processwire Rockmigrations by tomevault-io

Name: Processwire Rockmigrations
Author: tomevault-io

Processwire Rockmigrations

Creates and manages ProcessWire schema migrations via RockMigrations — fields, templates, roles, permissions, pages, and modules. Supports config migrations, direct API methods, MagicPages, and PageClass lifecycle hooks (onCreate, onAdded, onSaved). Use when creating or modifying fields, templates, roles, permissions, running migrations, setting up access control, or working with MagicPage and PageClass hooks in ProcessWire.

tomevault-io 647a1e3 2 files · 3.2 KB Updated Sep 17, 2026

File contents

RockMigrations Reference

RockMigrations provides version-controlled migrations for ProcessWire CMS. All migrations define fields, templates, roles, permissions, and pages via PHP code.

File Locations

Type	Location
Config migrations	`site/RockMigrations/{fields,templates,roles,permissions}/[name].php`
Site migrations	`site/modules/Site/Site.migrate.php`
Module source	`site/modules/RockMigrations/RockMigrations.module.php`

Execution

# Run all migrations via ddev
ddev php site/modules/RockMigrations/migrate.php

Migrations also auto-run on module refresh in the ProcessWire backend.

Quick Start — Config Field Migration

// site/RockMigrations/fields/myfield.php
<?php namespace ProcessWire;

return [
    'type' => 'text',
    'label' => 'My Field Label',
    'tags' => 'mytag',
];

Tips

Prefer config migrations over inline API calls for maintainability
One file per asset — easier to track changes in git
Use tags to organize fields/templates by module or feature
Check existing patterns in site/RockMigrations/ for project conventions
For undocumented methods, explore site/modules/RockMigrations/RockMigrations.module.php

Reference Files

Config migrations — field types, template definitions, roles, permissions, and common patterns
Config migration hooks — execution order, circular dependencies, module dependency installation
API methods — direct API via Site.migrate.php: createField, createTemplate, createPage, combined migrations, module installation
MagicPages — lifecycle hooks, Magic Methods, Magic Field Methods, Magic Assets, trait utilities
init() and ready() — attaching hooks directly in PageClasses instead of ready.php

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: processwire-rockmigrationsdescription: Creates and manages ProcessWire schema migrations via RockMigrations — fields, templates, roles, permissions, pages, and modules. Supports config migrations, direct API methods, MagicPages, and PageClass lifecycle hooks (onCreate, onAdded, onSaved). Use when creating or modifying fields, templates, roles, permissions, running migrations, setting up access control, or working with MagicPage and PageClass hooks in ProcessWire.---# RockMigrations ReferenceRockMigrations provides version-controlled migrations for ProcessWire CMS. All migrations define fields, templates, roles, permissions, and pages via PHP code.## File Locations| Type | Location ||------|----------|| Config migrations | `site/RockMigrations/{fields,templates,roles,permissions}/[name].php` || Site migrations | `site/modules/Site/Site.migrate.php` || Module source | `site/modules/RockMigrations/RockMigrations.module.php` |## Execution```bash# Run all migrations via ddevddev php site/modules/RockMigrations/migrate.php```Migrations also auto-run on module refresh in the ProcessWire backend.## Quick Start — Config Field Migration```php// site/RockMigrations/fields/myfield.php<?php namespace ProcessWire;return [ 'type' => 'text', 'label' => 'My Field Label', 'tags' => 'mytag',];```## Tips1. **Prefer config migrations** over inline API calls for maintainability2. **One file per asset** — easier to track changes in git3. **Use tags** to organize fields/templates by module or feature4. **Check existing patterns** in `site/RockMigrations/` for project conventions5. **For undocumented methods**, explore `site/modules/RockMigrations/RockMigrations.module.php`## Reference Files- [Config migrations](config-migrations.md) — field types, template definitions, roles, permissions, and common patterns- [Config migration hooks](config-migration-hooks.md) — execution order, circular dependencies, module dependency installation- [API methods](api-methods.md) — direct API via `Site.migrate.php`: createField, createTemplate, createPage, combined migrations, module installation- [MagicPages](magic-pages.md) — lifecycle hooks, Magic Methods, Magic Field Methods, Magic Assets, trait utilities- [init() and ready()](init-ready.md) — attaching hooks directly in PageClasses instead of ready.php---> Converted and distributed by [TomeVault](https://tomevault.io/claim/gebeer) — claim your Tome and manage your conversions.

Frequently asked questions