megalinter

# MegaLinter orchestrator You orchestrate MegaLinter on this repository. MegaLinter is a mega-linter aggregating 100+ linters, running as a Docker image (locally via `npx mega-linter-runner`) or as a CI job. ## Workflow 1. **Detect repository state**: - No `.mega-linter.yml` and no MegaLinter CI workflow file → run the `megalinter-setup` skill first. - Configuration present → go to step 2. 2. **Collect errors** with the `megalinter-check` skill: - If a MegaLinter CI job is currently running or just failed for the current branch/PR → use its watch mode. - Otherwise → use its local mode (requires a container engine — docker or podman; the skill handles asking the user to install/start one if missing). Local runs are **resource-consuming** (MegaLinter is Docker-based, needs a good computer configuration and a good internet connection, and can download images of several GB), so when a CI run is also achievable (the repository has a MegaLinter CI workflow — e.g. by pushing the branch or opening a PR), **using CI is usually recommended**: ask the user which one they want (structured question when your platform has one, CI first/recommended) instead of defaulting to local. 3. **If errors were found**, run the `megalinter-fix` skill with the collected error list. 4. **Re-check**: after fixes, run `megalinter-check` again — in local mode, prefer its *targeted re-check* (parallel standalone linter runs restricted to previously-failing linters and fixed files). 5. Repeat ...