Ext Ops Panel
Open dashboard
Comparison

lightrun vs engineer-debugging

lightrun is a plugin bundle for AI coding tools published by lightrun-platform. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). engineer-debugging is a plugin bundle for AI coding tools published by Seth Ford. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-11-12. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacelightrunengineer-debugging
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 27
Not marked · First seen
Not listed
Community marketplace sethdford/claude-skills Not listed Listed
Version: 1.0.0
Forks (GitHub): 9
Stars (GitHub): 46
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

lightrun vs engineer-debugging
Factlightrunengineer-debugging
Marketplaces that list it11
Stars (GitHub) (differs)27 (worse)46 (better)
Forks (GitHub) (differs)0 (worse)9 (better)
Last releaseNot publishedNot published
Where it runsInstalls as a plugin bundleInstalls as a plugin bundle
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)411
LicenceMITMIT
Repository (differs)github.com/lightrun-platform/lightrun-aigithub.com/sethdford/claude-skills
Changes in the last 7 days00
First seen (differs)2026-10-112026-11-05

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

lightrun

In its own words, on Claude Code: claude-plugins-community:

Lightrun's runtime investigation toolkit for Claude Code. Guides deterministic, evidence-first debugging of live applications by capturing real production behavior — variable state, stack traces, and execution flow — without redeploys or service restarts. Includes a mandatory preflight check that grounds investigations in actual runtime evidence, plus a blocker-aware handoff format that produces structured, reproducible debugging reports for engineering teams.

engineer-debugging

In its own words, on Community GitHub marketplaces:

Systematic debugging, root cause analysis, memory leaks, concurrency, postmortems.

How to run each

lightrun As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install lightrun@claude-community

engineer-debugging As a Claude Code plugin

Claude Code
/plugin marketplace add sethdford/claude-skills
/plugin install engineer-debugging@claude-skills

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: lightrun · What it can do: engineer-debugging · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built