myna-dev-bug

Extract session details and write a redacted GitHub issue template to tmp/bugs/.

8|1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/agentflock/myna --skill myna-dev-bug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: myna-dev-bug
Source: https://github.com/agentflock/myna/tree/main/.claude/skills/myna-dev-bug
Command: npx skills add https://github.com/agentflock/myna --skill myna-dev-bug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of a filled GitHub issue template from the current testing session, reducing manual context gathering and ensuring consistent bug reporting.

Core Features & Use Cases

  • Auto-detects the exact prompt, wrong output, and involved skill from the session context.
  • Auto-redacts sensitive content and writes a ready-to-submit GitHub issue to tmp/bugs/.
  • Produces a portable report that can be attached to a GitHub issue or shared with a team for faster triage.

Quick Start

Run the skill to generate a filled GitHub issue template from the current session and save it to tmp/bugs/.

Frequently Asked Questions about myna-dev-bug

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

FAQPage Schema
How do I automatically generate a GitHub bug report from a testing session?

To generate a GitHub bug report from a testing session, the skill extracts the exact prompt, incorrect output, and involved skill, then writes a filled, auto-redacted issue template to tmp/bugs/.

What session context is needed to create a filled GitHub issue template?

Creating a filled GitHub issue template requires the current testing session context, which includes the exact prompt, incorrect output, connected MCPs, Claude model used, and any affected files.

Does the bug reporting skill redact sensitive content before exporting?

Yes, the bug reporting skill auto-redacts sensitive content from the session context before producing the portable GitHub issue template and writing it to the tmp/bugs/ directory.

Can I use this skill to record connected MCPs and Claude model details for bug triage?

Yes, you can use this skill to record connected MCPs and Claude model details for bug triage, as it automatically detects and includes this environment information in the generated issue template.

What is the best way to document incorrect skill outputs for team sharing?

The best way to document incorrect skill outputs for team sharing is to run this skill, which produces a portable, redacted bug report that can be attached to a GitHub issue or shared for faster triage.