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.

1. 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.

1. If errors were found, run the megalinter-fix skill with the collected error list.
2. 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).
3. Repeat steps 3-4 at most 3 times. If errors remain after 3 iterations, stop and report the remaining errors with your recommendation (fix manually, disable rules, or disable linters).
4. Performance: if megalinter-check reported slow_linters (even on a green run), relay its performance suggestions to the user at the end of the loop — speed wins are proposed, never applied without agreement.

Rules

• Never commit or push on the default branch (main/master): create a branch like megalinter/fix-<topic> first.
• Ask the user before disabling any linter or rule, and before pushing commits.
• Never force-push, with one exception: when MegaLinter itself pushed a [MegaLinter] Apply linters fixes commit onto the watched branch, megalinter-check amends it with a 🤖 prefix and re-pushes it with --force-with-lease to re-trigger the CI checks (see its "MegaLinter auto-fix commits" section for the conditions). Never use plain --force, and never force-push in any other situation.
• Keep the user informed with a short status after each phase (errors found, fixes applied, remaining).

Optimization: sub-agents (Claude Code and compatible agents)

If your environment supports spawning sub-agents (e.g. a Task/Agent tool) and the megalinter-watcher, megalinter-runner, megalinter-fixer agent definitions are available:

• Installed as an agent plugin (Claude Code, Cursor, Copilot), they ship with the plugin. Some platforms list them under a namespaced name (megalinter:megalinter-watcher), others under the bare name.
• Installed as skills, the megalinter-setup skill copies them into your platform's agents folder (e.g. .claude/agents/, .opencode/agent/, .github/agents/ where the file name ends with .agent.md) under their bare names.

Use whichever of the two forms your platform actually lists, and fall back to inline execution if neither is available.

Then:

• Delegate CI watching to megalinter-watcher and local runs to megalinter-runner — they keep the large logs out of your context and return only a compact error list.
• Fan out one megalinter-fixer per failing linter to fix several linters in parallel.

If sub-agents are not available, perform every step inline following the skill instructions.