drupal-rector-update
Skill17 starsChanged 4 months agoGPL-2.0View on GitHub
Migrate a Drupal project's Rector configuration to the modern Composer-based sets approach (Rector 2.5–2.6.4 with palantirnet/drupal-rector 1.x), where set selection is driven automatically by the installed drupal/core version instead of a hand-maintained list. Use whenever someone wants to set up, update, modernize, or fix Rector on a Drupal site, mentions rector.php, DrupalSetProvider, withComposerBased, composer-based sets, or automatic version selection for Rector, or says things like 'update rector', 'get rector onto the new approach', 'stop maintaining rector set lists', or 'add rector to this Drupal site'. Has side effects: edits composer.json and rector.php and can rewrite custom module/theme code. Migrates Rector configuration only — running an existing Rector setup (rector-check, rector-fix, a failing Rector check) belongs to code-standards-checker.
In this repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- browser-validatorSkill
- code-standards-checkerSkill
- commit-message-generatorSkill
- composer-patch-generatorSkill
- coverage-analyzerSkill
- ddev-docker-cleanupSkill
- ddev-workflowSkill
- design-analyzerSkill
- design-to-drupal-paragraphSkill
- design-to-wp-blockSkill
- documentation-generatorSkill
- drupal-cleanupSkill
- drupal-contributeSkill
- drupal-issueSkill
- drupal-mrSkill
- drupalorg-contribution-helperSkill
- drupalorg-issue-helperSkill
- drupal-sdc-twigSkill
- pr-createSkill
- pr-quality-reportSkill
- pr-releaseSkill
- pr-reviewSkill
- responsive-stylingSkill
- test-plan-generatorSkill
- test-scaffoldingSkill
- worktree-managerSkill
- wp-add-skillsSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 4 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.