arn-infra-report

Arness Infra Report

Report an Arness Infra workflow issue by running a diagnostic and filing a GitHub issue on the Arness plugin repository. The arn-infra-doctor agent analyzes Infra configuration and behavior — it never reads project source code or business logic.

Workflow

Step 0: Smart Routing

Before proceeding, check whether the user's issue actually belongs to a different Arness plugin:

1. Read the ## Arness section from the project's CLAUDE.md (if it exists).
2. Check the user's description for keyword signals:
   • Code keywords: "plan", "spec", "execute", "taskify", "swift", "standard", "batch", "ship", "PR", "review-pr", "assess", "catch-up", "document-project", "save-plan"
   • Spark keywords: "discover", "prototype", "greenfield", "stress test", "naming", "brainstorming", "feature extract", "visual sketch", "use cases"
3. If Code signals detected: "This sounds like an Arness Code issue. Run /arn-code-report instead."
4. If Spark signals detected: "This sounds like an Arness Spark issue. Run /arn-spark-report instead."
5. If the user confirms it is actually an Infra issue, proceed.

---

Step 1: Explain the Process

Inform the user:

"I'll help you report an Arness Infra workflow issue. Here's how this works:

1. You describe what happened — which skill you used and what went wrong
2. I'll run a diagnostic that checks Infra's configuration and expected behavior (I won't read your project code)
3. You'll review the issue report before it's submitted
4. The issue gets filed on the Arness plugin repository for the maintainers

Your project code and business logic are never included in the report."

---

Step 2: Gather User Description

Ask the user using AskUserQuestion:

• "What happened? Which Arness Infra skill were you using and what went wrong?"

Let the user type a free-form description. This becomes the user_description for the diagnostic.

---

Step 3: Check Prerequisites

1. Detect the plugin's GitHub repository:
   • Read the repository field from ${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json. Parse owner/repo from the URL.
   • Fallback: git -C ${CLAUDE_PLUGIN_ROOT} remote get-url origin. Extract owner/repo from the URL (strip .git suffix and https://github.com/ or [email protected]: prefix).