skills.rest
InditexTech
InditexTechOFFICIAL
Explore all skills by this author →
WebsiteGitHub

qa

Convert conversational bug reports into durable GitHub issues.

195|16|Updated Feb 18, 2025
Search Tags:#codebase#github#qa#analysis#issues#issue-tracking#bug
One-click install
npx skills add https://github.com/InditexTech/weavejs --skill qa-inditextech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/InditexTech/weavejs/tree/main/code/.agents/skills/qa
Command: npx skills add https://github.com/InditexTech/weavejs --skill qa-inditextech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Interactive QA sessions reduce friction when reporting bugs or issues conversationally and transform descriptions into GitHub issues, using background codebase exploration to provide context and domain language.

Core Features & Use Cases

  • Conversational bug reporting that results in durable GitHub issues.
  • Background codebase exploration to surface domain language and context for issue writing.
  • Guidance on whether to split problems into multiple issues and how to structure them for clarity.

Quick Start

Describe the issue you want to report and let the QA agent explore the codebase to draft a durable GitHub issue.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I report a bug conversationally and create a GitHub issue from it?▼

To report a bug conversationally and create a GitHub issue, you describe the problem to the QA agent, which then explores your codebase for context and files a durable issue with domain-appropriate language.

How does background codebase analysis improve issue reporting?▼

Background codebase analysis improves issue reporting by having an Explore subagent learn your domain language and relevant context, ensuring the generated GitHub issues are accurate and user-facing.

Can I get guidance on whether to split a reported problem into multiple GitHub issues?▼

Yes, you can get guidance on splitting a reported problem into multiple GitHub issues, as the QA agent provides recommendations on issue scoping and how to structure problems for maximum clarity.

How do I ensure my GitHub bug reports remain durable despite codebase changes?▼

To ensure GitHub bug reports remain durable despite codebase changes, the QA agent uses background codebase exploration to write issue descriptions that focus on domain language rather than brittle implementation details.

What is the best way to streamline bug reporting for a development team?▼

The best way to streamline bug reporting is through interactive QA sessions that reduce friction by conversing with users and automatically transforming their problem descriptions into structured GitHub issues.

Do I need a YAML frontmatter in SKILL.md to use this issue tracking agent?▼

Yes, you need a YAML frontmatter in SKILL.md with a name and description, which provides the necessary guidance for issue scoping and outputs for the bug reporting agent to function correctly.

Related Skills

Explore More Software Engineering Skills→
eleva-labseleva-labs

setup-env

Configure environment variables and .env files for frontend environments.

Official
Basic
arvindbattulaarvindbattula

triage

Identify bug root causes and generate GitHub issues with TDD fix plans.

Community
Advanced
dariomazzitellireplik-coderdariomazzitellireplik-coder
1

qa

Create GitHub issues from conversational bug reports with codebase context.

Community
Intermediate
tgmarinhotgmarinho

qa

Create GitHub issues from conversational bug reports.

Community
Intermediate