megalinter-check

# MegaLinter check Collect the current MegaLinter errors and produce a compact error list that the `megalinter-fix` skill can consume. ## Choose a mode - **Watch mode** — a MegaLinter CI job exists for the current branch/PR (running or completed): parse its logs. No Docker needed. - **Local mode** — no CI job available, or the user wants a pre-push check: run MegaLinter with Docker via `npx mega-linter-runner`. - **Targeted re-check** (local, after fixes): re-run only the previously-failing linters in parallel standalone images. ## Watch mode 1. Detect the provider from `git remote get-url origin` and the CI config files present. 2. Load the matching provider guide from this skill's directory — **only the one you need**: - GitHub Actions → `providers/github.md` - GitLab CI → `providers/gitlab.md` - Azure Pipelines → `providers/azure.md` - Bitbucket Pipelines → `providers/bitbucket.md` 3. Follow the guide: locate the MegaLinter job, wait for completion if running, fetch the logs of the MegaLinter step. 4. Parse the MegaLinter summary (the `❌`/`✅` table) and per-linter error sections. ## Local mode Before the first local run, make sure the user is aware that running MegaLinter locally is **resource-consuming**: it needs a reasonably powerful machine (CPU, RAM, free disk space) and a good internet connection — MegaLinter is Docker-based and the first run downloads a large image (can be several GB depending on the flavor). Because of this, **watch mode (CI does...