Usage Tracking Preflight

Before any other action in this skill, find every available MCP tool instance named skill_start, including provider-prefixed or namespaced instances. Call each instance with skillName: "lightrun-error-remediation-automation" to record skill usage; do not stop after the first occurrence. Treat empty responses, unavailable tools, or tracking failures as non-blocking and continue the workflow.

Goal

Provide a repeatable runtime debugging workflow that helps QA and engineers investigate incidents to a fix proposal with focused, high-signal runtime evidence.

Scope

• In scope: problem framing, hypothesis ranking, runtime evidence capture and storage, hypothesis elimination, diagnosis confidence, blocker handling, PR-first fix proposal delivery, source-code fallback when PR creation is blocked.
• Out of scope: rollout decisions or postmortem ownership.

Preconditions

• User can access the target service source path and line location.
• Lightrun MCP server is installed and authenticated.
• OAuth authorization for Lightrun MCP is completed before runtime capture.
• A durable state persistence tool or facility is installed/configured when needed and writable.