qa-issue-report

Convert vague bug reports into structured GitHub or GitLab issues with code references.

25|1|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/parhumm/jaan-to --skill qa-issue-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-issue-report
Source: https://github.com/parhumm/jaan-to/tree/main/adapters/codex/skillpack/skills/qa-issue-report
Command: npx skills add https://github.com/parhumm/jaan-to --skill qa-issue-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turning vague bug reports into actionable GitHub/GitLab issues by automatically collecting context, code references, media, and environment details, while preserving user privacy.

Core Features & Use Cases

  • Two-phase workflow with a hard stop for human review
  • Code reference discovery and attachment handling
  • Platform-agnostic submission to GitHub or GitLab

Quick Start

Describe the issue you want to file and invoke the qa-issue-report skill to generate a complete, privacy-safe issue draft for GitHub or GitLab.

Frequently Asked Questions about qa-issue-report

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

FAQPage Schema
How do I convert vague bug reports into structured GitHub issues?

To convert vague bug reports into structured GitHub issues, this skill automatically collects context, discovers code references, and generates a comprehensive draft with descriptions, reproduction steps, and environment details for review.

Can I submit structured issues to both GitHub and GitLab repositories?

Yes, you can submit structured issues to both platforms. The skill supports platform-agnostic submission to GitHub or GitLab using REST APIs or CLI-based commands after completing the privacy sanitization and review phases.

How does privacy sanitization work when filing code references in bug reports?

Privacy sanitization works by implementing a hard stop for human review in a two-phase workflow. This ensures sensitive data is removed from code references, media attachments, and environment details before any issue is submitted.

What is the best way to attach media and code references when filing a feature request?

The best way to attach media and code references is to describe the feature request and invoke the skill. It automatically discovers relevant code references and handles media attachments to create a comprehensive issue draft.

Do I need to manually format environment details and reproduction steps for GitLab issues?

No, you do not need to manually format environment details and reproduction steps. The skill automatically captures this comprehensive context and structures it before submitting the issue to your GitLab repository.