// Add a new MegaLinter flavor (language-specific Docker image). Use when creating a new specialized Docker image variant.
| name | add-flavor |
| description | Add a new MegaLinter flavor (language-specific Docker image). Use when creating a new specialized Docker image variant. |
| allowed-tools | Read Grep Glob Bash Edit Write |
| argument-hint | ["flavor-name"] |
| model | sonnet |
Guide through adding a new flavor named $ARGUMENTS.
Steps:
megalinter/descriptors/schemas/megalinter-descriptor.jsonschema.json — add the new flavor name to enum_flavorsflavors/$ARGUMENTS/descriptor_flavors arrays in the relevant megalinter/descriptors/*.megalinter-descriptor.yml files for each language/tool this flavor should includemake megalinter-build to auto-generate:
flavors/$ARGUMENTS/Dockerfileflavors/$ARGUMENTS/action.ymlflavors/$ARGUMENTS/flavor.jsonflavor.json for the linter list)CHANGELOG.md in the repository root (not docs/) — add one line under Flavors in the beta section:
- Add new `<flavor-name>` flavor for <what languages/tools it targets>
user/add-<flavor-name>-flavorGuided workflow for adding a new linter to MegaLinter. Use when a contributor needs to add support for a new linting tool.
Add a new output reporter to MegaLinter. Use when adding support for a new CI system or output format.
Gather requirements for a MegaLinter change by asking clarifying questions until the problem is fully understood. First step of the contribution workflow.
Design a MegaLinter solution and write a technical specification. Second step of the contribution workflow, use after /analyze.
Diagnose MegaLinter .mega-linter.yml configuration issues. Use when linters aren't running as expected or configuration seems wrong.
End-to-end workflow to fix a GitHub issue — collect context, analyze, implement on a branch, open a PR, then hand off to /pr-watch-fix until CI is green.