issue

Generate redacted GitHub bug report drafts from Spark session context.

1|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/automatedigital/spark --skill issue-automatedigital
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue
Source: https://github.com/automatedigital/spark/tree/main/skills/github/issue
Command: npx skills add https://github.com/automatedigital/spark --skill issue-automatedigital

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Filing detailed, reproducible GitHub bug reports for the Spark AI agent harness requires manually gathering session context, logs, and environment details, while risking the accidental exposure of sensitive credentials like API keys and tokens in public issues. This skill eliminates that manual work and includes built-in redaction to keep shared reports safe.

Core Features & Use Cases

  • Automated Evidence Collection: Pulls relevant session context, logs, screenshots, and environment details (Spark version, OS, surface type) from the current Spark session without manual copy-pasting.
  • Built-in Sensitive Data Redaction: Automatically strips API keys, bearer tokens, OAuth codes, and private config values from all collected evidence to prevent accidental data leaks.
  • Approval-First Submission Workflow: Generates a fully formatted, maintainer-ready issue draft and requires explicit user approval before any submission, eliminating the risk of accidental public posts.
  • Use Case: If you encounter a bug in the Spark CLI while working on a project, invoke this skill to auto-compile all relevant context into a ready-to-submit GitHub issue that you can review and approve before it goes public.

Quick Start

Invoke the issue skill to generate a redacted, detailed GitHub bug report draft from your current Spark session for review and approval before submission.

Frequently Asked Questions about issue

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

FAQPage Schema
How do I file a GitHub bug report for Spark without exposing my API keys?

Drafting a GitHub bug report for Spark with built-in redaction automatically strips API keys, bearer tokens, and OAuth codes from session context and logs. This prevents accidental exposure of sensitive credentials in public issues while compiling reproducible details.

How do I automatically gather logs and session context for a Spark bug report?

Automated evidence collection pulls relevant session context, logs, environment details, and reproduction evidence from active Spark sessions. This eliminates manual copy-pasting by extracting Spark version, OS, and surface type directly into a formatted issue draft.

Can I review a GitHub issue draft before it gets submitted publicly?

An approval-first submission workflow generates a fully formatted, maintainer-ready GitHub issue draft that requires explicit user approval before any submission. This eliminates the risk of accidental public posts by gating the final action.

Does the bug report drafting process work across the Spark CLI, browser dashboard, and macOS app?

Bug report drafting applies to user-reported Spark bugs across CLI, browser dashboard, remote dashboard, and macOS desktop app surfaces. It ensures all required triage context is included regardless of the specific Spark interface used.

What is the best way to report a Spark AI agent harness bug with full reproduction evidence?

The best way to report a Spark bug is invoking an automated drafting process that compiles active session context, logs, and reproduction evidence into a redacted GitHub issue. This ensures maintainers receive reproducible details without sensitive private user data.