At the moment there`s a migration_config.yaml file with all conversions shipped with the wheel. So, this can be extended (PRs welcome). I am pretty sure we did not catch all conversions.
--config is the parameter for custom YAML.
Further development Idea: We could add an command line parameter to point to an "additional rule" file.
A nice helper When I run it (installed in a pyenv virtualenv via pip) I get Could not find plone_codemod.import_migrator in any configured modules though.
$ plone-codemod ../collective.behavior.banner/src
Plone 5.2 → 6.x Migration Tool
Source: /Users/pbauer/workspace/collective.behavior.banner/src
Config: /Users/pbauer/.pyenv/versions/3.13.12/envs/codemod/lib/python3.13/site-packages/plone_codemod/migration_config.yaml
=== Phase 1: Python import migration (libcst) ===
Initializing libcst in ../collective.behavior.banner/src
Successfully wrote default config file to /Users/pbauer/workspace/collective.behavior.banner/src/.libcst.codemod.yaml
Loaded 129 import mappings from /Users/pbauer/.pyenv/versions/3.13.12/envs/codemod/lib/python3.13/site-packages/plone_codemod/migration_config.yaml
Running PloneImportMigrator on ../collective.behavior.banner/src ...
stderr: Could not find plone_codemod.import_migrator in any configured modules
[...]