ワンクリックで
add-reporter
// Add a new output reporter to MegaLinter. Use when adding support for a new CI system or output format.
// Add a new output reporter to MegaLinter. Use when adding support for a new CI system or output format.
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.
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.
| name | add-reporter |
| description | Add a new output reporter to MegaLinter. Use when adding support for a new CI system or output format. |
| allowed-tools | Read Grep Glob Edit Write |
| argument-hint | ["reporter-name"] |
| model | sonnet |
Guide through adding a new reporter named $ARGUMENTS to MegaLinter.
Steps:
megalinter/reporters/<Name>Reporter.py extending megalinter.Reportermanage_activation() — check env var like <NAME>_REPORTER=true to enable/disableproduce_report() — generate the report outputinitialize(), add_report_item()megalinter/MegaLinter.pyConsoleReporter.py, TapReporter.pyGithubCommentReporter.py, GitlabCommentReporter.pyJsonReporter.py, SarifReporter.pyApiReporter.py, EmailReporter.pyCHANGELOG.md in the repository root (not docs/) — add one line under Reporters in the beta section:
- Add <ReporterName>: <what CI system or output format it supports, one sentence>
user/add-<reporter-name>-reporter