qa-engineer

Systematically test features, validate fixes, and log results in .standup workflows.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/mxnyawi/opencode-standup --skill qa-engineer-mxnyawi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-engineer
Source: https://github.com/mxnyawi/opencode-standup/tree/main/skills/qa-engineer
Command: npx skills add https://github.com/mxnyawi/opencode-standup --skill qa-engineer-mxnyawi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA engineers help teams deliver reliable software by systematically testing features, catching bugs early, and validating fixes before release.

Core Features & Use Cases

  • Test new features implemented by the developer
  • Identify bugs, edge cases, and usability issues
  • Write and maintain test cases
  • Validate bug fixes
  • Maintain your progress logs and task list
  • Ensure test coverage is adequate
  • Perform regression testing

Quick Start

Launch the QA workflow for the current project to begin testing and logging results.

Frequently Asked Questions about qa-engineer

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

FAQPage Schema
How do I track bugs and maintain QA logs for feature releases?

To track bugs and maintain QA logs, use this Skill to systematically test per-feature releases, log testing results in .standup workflows, and update task tracking lists with structured bug reports.

What is the best way to perform regression testing on recent bug fixes?

The best way to perform regression testing on bug fixes is to launch the QA workflow to validate fixes, ensure adequate test coverage, and verify that new changes do not break existing software functionality.

Can I use this for manual testing and automated test case management?

Yes, this Skill applies to both manual and automated testing. It helps you write and maintain test cases, identify edge cases, and ensure test coverage is adequate across your QA testing cycles.

Does this workflow require specific dependencies for task tracking and log management?

No, this workflow has zero dependencies. It natively handles task tracking and log management within .standup workflows, allowing you to maintain progress logs without requiring external integrations.

When should I not use this approach for software quality assurance?

You should not use this approach if your project lacks a defined workflow for per-feature releases or regression cycles, as it relies on structured task tracking and .standup workflows to log testing results.