arc-debug

Automate structured debugging of arc-tracked tasks in OpenCode.

1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/SentioLabs/agent-nexus --skill arc-debug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: arc-debug
Source: https://github.com/SentioLabs/agent-nexus/tree/main/opencode-marketplace/plugins/arc/skills/arc-debug
Command: npx skills add https://github.com/SentioLabs/agent-nexus --skill arc-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to debugging arc-tracked tasks in OpenCode, guiding reproduce, evidence gathering, root cause analysis, and safe verification before implementing fixes.

Core Features & Use Cases

  • Reproduce and document failure scenarios with exact steps to ensure consistent debugging across environments.
  • Evidence-centric analysis gather logs, traces, and relevant state data to support root-cause hypotheses.
  • Guided verification validate fixes with controlled checks and rollback plans to prevent regressions.

Quick Start

Begin by reproducing the issue with exact steps, capture evidence, and document the root cause before proposing a fix.

Frequently Asked Questions about arc-debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug failing tasks in OpenCode without causing regressions?▼

Debugging failing tasks in OpenCode requires structured reproduction, evidence collection, and guided verification before applying fixes. This approach enforces root-cause analysis with controlled checks and rollback plans to prevent regressions.

What is the best way to find the root cause of unexpected behavior in arc-tracked tasks?▼

Finding the root cause of unexpected behavior involves gathering logs, traces, and relevant state data to support hypotheses. Testing these hypotheses systematically ensures accurate root-cause analysis before proposing fixes.

How do I reproduce a failure scenario consistently across different environments?▼

Reproducing a failure scenario consistently requires documenting exact steps to trigger the issue. Capturing evidence during these controlled reproductions ensures the debugging process remains reliable across different environments.

Can I use automated debugging for stack traces and failing tests in OpenCode arcs?▼

Automated debugging applies to stack traces, failing tests, and unexpected behavior across OpenCode arcs. It automates structured evidence collection and hypothesis testing to guide verification and fix proposals.

Do I need to capture logs and traces before fixing arc-tracked bugs?▼

Capturing logs, traces, and relevant state data is required before fixing arc-tracked bugs. This evidence-centric analysis supports root-cause hypotheses and enables guided verification with controlled checks and rollback plans.