arn-spark-report

Diagnose Arness Spark issues and draft GitHub issues for review.

31|3|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/AppsVortex/arness --skill arn-spark-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arn-spark-report
Source: https://github.com/AppsVortex/arness/tree/main/plugins/arn-spark/skills/arn-spark-report
Command: npx skills add https://github.com/AppsVortex/arness --skill arn-spark-report

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill automates diagnosing Arness Spark issues and filing public GitHub issues on the Arness plugin repository. It ensures that project source code and business logic are never uploaded.

Core Features & Use Cases

  • Diagnose Spark issues using the arn-spark-doctor agent to assess configuration and behavior without inspecting user code.
  • File a GitHub issue on the Arness plugin repository with a structured, reviewable draft that includes the user description and diagnostic findings.
  • Smart routing to suggest whether an issue belongs to Arness Code or Arness Infra and route accordingly.
  • Local fallback when GitHub access is unavailable to generate a draft for manual submission.
  • Safety: guarantees no project code, secrets, or business logic is ever exposed in reports.

Quick Start

Describe what happened and which Spark skill you used, and I’ll start the diagnostic and prepare an issue draft.

Frequently Asked Questions about arn-spark-report

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

FAQPage Schema
How do I diagnose Spark workflow problems and misconfigurations without exposing source code?

To diagnose Spark issues safely, this skill analyzes the plugin's configuration to assess behavior without reading or uploading your project source code, ensuring business logic and secrets remain private.

How do I file a GitHub issue for an Arness Spark plugin performance concern?

Filing a GitHub issue for Arness Spark involves generating a structured draft with your description and diagnostic findings, which you review before it submits to the plugin repository.

What happens when I need to report a Spark issue but GitHub access is unavailable?

When GitHub access is unavailable, the diagnostic process falls back to generating a local draft issue containing your description and findings for manual submission.

Does the Spark diagnostic report distinguish between Arness Code and Arness Infra issues?

Yes, the Spark diagnostic report includes smart routing to suggest whether an issue belongs to Arness Code or Arness Infra, directing the draft to the correct repository.

What information do I need to provide to start an Arness Spark diagnostic?

To start the Spark diagnostic, you describe what happened and identify which Spark skill you used, which triggers the assessment and prepares the issue draft.