mega-loop

Plugin mega-loop from marketplace mega-loop in mega-edo/mega-loop-skill. Commands read from the repo's manifest — 2 days ago.

Skills (7)

• connect

  Pick which mega-loop project this session works on. Use when the user says "connect", "which project", "switch project", or before listing bugs / fixing when no project is chosen yet. Lists the user's projects and remembers the one they pick for later commands.

• diagnose

  Read what mega-loop diagnosed from production traces — list the open bugs for your project, and explain one bug's cause + the exact file:line. Use when the user asks "what's broken / what should I fix / where / why" about a mega-loop project, or says "bugs" / "explain". Read-only: it reports, it nev

• fix

  Fix a bug that mega-loop diagnosed from production traces — from inside this session. Use when the user asks to fix/autofix a mega-loop bug, mentions a bug id or bug title from the mega-loop dashboard, or says "fix" / "autofix". One verb; the SERVER decides who fixes: project bound to a GitHub repo

• refine

  Apply maintainer review feedback to an open auto-fix PR/MR — a REVISION, not a fresh fix. Use when the user says "refine", "apply the review comments", "address the PR feedback", or after a maintainer reviews a mega-loop fix PR. Reads the PR's review comments (GitHub / GitLab / Bitbucket), makes the

• trace-analyze

  Grade an AI agent's traces against the readiness checks MEGA Loop runs internally, plus this plugin's own checks of what its detection reads, and produce a report with a fix for every finding — read-only, no edits. Use when the user's traces are missing, fragmented or ignored, when MEGA Loop reports

• trace-fix

  Fix an AI agent's instrumentation so its traces become usable by MEGA Loop — one clean trace per request, OpenInference-compliant — then re-run the validator to prove it. Edits the user's code. Use after trace-analyze finds problems, or when the user asks to make their traces pass MEGA Loop's readin

• trace-gen

  Add tracing to an agent that emits none, then prove the first traces are readable by running the app and grading what came out. Use when a repository has no instrumentation at all, when the user asks how to start tracing, or when MEGA Loop has no traces to read because none are being sent. Use trace

Slash commands (6)

• /mega-loop:bugs

  List the open bugs mega-loop diagnosed for the active project

• /mega-loop:disconnect

  Disconnect this repo from its saved mega-loop project (stop auto-reconnecting)

• /mega-loop:explain

  Explain one mega-loop bug — its cause and the exact file:line

• /mega-loop:groups

  List the project's bugs grouped into packaging units (the shape a fix ships)

• /mega-loop:projects

  List your mega-loop projects (read-only; use /mega-loop:connect to pick one)

• /mega-loop:status

  Show mega-loop status — setup/auth, the connected project, all your projects, and any fix in flight

MCP servers (1)

• mega-loop

  connects to: ${user_config.base_url}/companion/mcp

Hooks (2)

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/hooks/restore-connection.sh

• Stop

  ${CLAUDE_PLUGIN_ROOT}/hooks/gate-on-stop.sh

Similar plugins