원클릭으로
diagnose-config
// Diagnose MegaLinter .mega-linter.yml configuration issues. Use when linters aren't running as expected or configuration seems wrong.
// Diagnose MegaLinter .mega-linter.yml configuration issues. Use when linters aren't running as expected or configuration seems wrong.
| name | diagnose-config |
| description | Diagnose MegaLinter .mega-linter.yml configuration issues. Use when linters aren't running as expected or configuration seems wrong. |
| allowed-tools | Read Grep Glob |
| argument-hint | ["config-file-path"] |
| model | sonnet |
Diagnose MegaLinter configuration. Read the .mega-linter.yml (or path provided in $ARGUMENTS) and check for:
.mega-linter.yml, which overrides descriptor defaults. Both .mega-linter.yml and .megalinter.yml are recognized.ENABLE_LINTERS/DISABLE_LINTERS take precedence over ENABLE/DISABLE (descriptor-level). You can't enable a linter if its descriptor is disabled.FILTER_REGEX_INCLUDE/FILTER_REGEX_EXCLUDE regex syntax_ separator matching the generated name DESCRIPTOR_LINTERNAME (e.g., PYTHON_PYLINT_ARGUMENTS, not pylint_arguments)flavors/<flavor>/flavor.jsonPRE_COMMANDS and POST_COMMANDS syntax (each needs command and cwd fields, cwd is root or workspace)_ separator in linter-specific varsVALIDATE_ALL_CODEBASE=true in CI (slow — usually want diff-only){LINTER}_FILTER_REGEX_INCLUDE/EXCLUDE overrides global filtersReference megalinter/config.py for the full resolution logic.
Add a new MegaLinter flavor (language-specific Docker image). Use when creating a new specialized Docker image variant.
Guided 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.
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.