Results for “qa”

Independent quality assurance for one SDD Composy task in qa_required: CA coverage, unit/integration/E2E, accessibility, responsiveness, environment, and evidence inventory, producing the QA report and requesting evidence_required. Use when a task finished execution — 'rodar o QA da task', 'testar a TASK-003', 'validar a implementação'. Do NOT use for code review (sdd-review), the final verdict (sdd-verify), or test runs outside an SDD task.

The English summary is being prepared. Showing the original description.

Report-only QA testing. Systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa instead. Proactively suggest when the user wants a bug report without any code changes. (gstack) Voice triggers (speech-to-text aliases): "bug report", "just check for bugs".

The English summary is being prepared. Showing the original description.

Orchestrate the QA team through a full testing cycle — qa-lead strategy and test plan, qa-manual-tester case writing, execution, sign-off.

The English summary is being prepared. Showing the original description.

Run a conversational QA session where the user reports bugs or issues, and file durable Beads issues using project domain language. Use when the user wants to report bugs, do QA, file issues conversationally, or mentions a QA session.

The English summary is being prepared. Showing the original description.

Test Slack authentication, message creation and cleanup, and OpenClaw message handling. Collect evidence from stored messages and test runs, while distinguishing what API checks prove from interactions that require observation in the actual Slack client.

• Check Slack authentication and channel access
• Test message creation, editing, and deletion
• Verify OpenClaw message handling and replies

Test SwiftUI apps on a real iPhone or iPad by repeatedly capturing screens, analyzing them, taking actions, and verifying results. An embedded HTTP server enables interaction, with optional remote access through Tailscale.

• Find bugs in an iPhone app on a real device
• Check an iPad app on a real device
• Test screen behavior using Swift source and screenshots

Investigate bugs in browser flows, APIs, command-line tools, background jobs, workers, and webhooks. Produce a structured report with reproduction steps and evidence or browser scores, without changing code to fix the issues.

• Investigating bugs without changing code
• Preparing bug reports with reproduction steps
• Checking API and background processing issues

Find and fix bugs in websites, APIs, command-line tools, and background processes. Choose from three testing depths, verify fixes, and receive evidence of the changes plus a summary of readiness for release.

• Test a website and fix bugs
• Check API or command-line behavior
• Verify background jobs and webhook processing

Create a draft pull request for reviewing Storybook changes. Prepare a title, required labels, and a description using the repository template, including verified manual testing steps that another maintainer can follow.

• Submit Storybook changes for review
• Choose category, CI, and manual QA labels
• Prepare reproducible manual testing instructions

Check the appearance and interaction states of web pages, terminal interfaces, and paginated documents. Uses captured images, light and dark themes, viewport comparisons, and independent reviews to produce evidence-backed verdicts for each checklist item.

• Checking a UI after implementation changes
• Comparing a page with a design reference
• Finding Japanese text clipping and awkward wrapping

Breaks long-running goals into small, verifiable steps, tracks progress, and records evidence from actual operation. Checkpoints preserve what has been proven so work can resume after interruptions and continue toward explicit completion criteria.

• Managing a long-running development goal
• Resuming work after an interruption
• Recording evidence for completion criteria

Add end-to-end tests, which check complete usage flows, and API tests for features that already work. Follow the project's existing test setup to extend automated coverage without introducing a separate testing approach.

• Adding automated tests to an existing feature
• Testing complete usage flows with E2E tests
• Adding API tests using the existing test setup

Set up Antigravity 2.0 Agent Manager alongside Antigravity IDE to coordinate parallel development agents. Assign roles and folder boundaries, review their changes in the editor, and use Git checkpoints to manage shared work.

• Setting up Agent Manager alongside the IDE
• Assigning frontend, backend, and QA roles
• Separating editing scopes to avoid conflicts

Check Codewhale release readiness through ordered tests, builds, version checks, and manual terminal checks. Record command results and observed behavior, including responsiveness, route isolation, and follow-up input handling, while explicitly identifying any skipped checks.

• Run automated checks on the actual release branch
• Check whether a PR merges into the release branch
• Manually test terminal responsiveness and input behavior

Find the QwenPaw documentation and source files most relevant to a question. This skill maps topics such as installation, configuration, skills, and memory to likely reading paths, helping an agent focus its investigation.

• Finding installation and configuration references
• Locating documentation for skills and MCP
• Tracing memory and multi-agent behavior

Configure tools and skills for sub-agents before dispatching development tasks. Role presets cover implementation, planning, reviews, testing, and verification, with defined boundaries for what each agent should do and whether it may modify files.

• Setting tool permissions before spawning a sub-agent
• Separating implementation, planning, and review roles
• Configuring agents for review without file changes

Find relevant QwenPaw documentation and source files for questions about setup, configuration, skills, memory, and other features. It maps question keywords to likely file paths so the agent can read and verify the right material.

• Find documentation for installation or configuration questions
• Locate source files related to skills or memory
• Identify where to investigate errors or CLI behavior

Turn user stories and acceptance criteria into detailed test scenarios. Define objectives, starting conditions, user roles, actions, and observable results, including invalid inputs and boundary cases, so a quality assurance team can carry out the checks.

• Writing test cases from user stories
• Preparing acceptance test scenarios
• Checking invalid inputs and boundary cases

Create or update a sprint plan, a short development work plan, using existing work items, completed work, and available capacity. Organize priorities, carryover, dependencies, and risks, and produce a progress report.

• Plan the next sprint around available capacity
• Re-estimate unfinished work carried into the next sprint
• Update task priorities and estimates

Create an onboarding document for a new contributor or agent, tailored to their role. Gather project context, relevant conventions, key files, current work, and suggested first tasks into a practical starting guide.

• Preparing a guide for a new programmer
• Orienting designers or narrative contributors
• Sharing current work with QA or production staff

Break a large game development feature into implementation tasks with clear acceptance criteria. Each task carries relevant requirements and design decisions, with test specifications added when the selected review mode includes a QA review.

• Break a game feature into implementation tasks
• Carry requirements and design decisions into task files
• Define acceptance criteria and test specifications

Test CodexBar against real provider services, check application settings, and verify menu contents. Use command-line checks and visual evidence to distinguish authentication problems, API mismatches, and display issues before a release.

• Checking provider connections before a release
• Investigating missing usage data or authentication failures
• Comparing menu contents with enabled providers

Prepare Handsontable changes for review by checking branch names, running required checks, and creating or updating draft pull requests. Fill the project template with test evidence and add changelog entries in the required order.

• Submitting a feature or documentation branch for review
• Updating a pull request description with test evidence
• Adding a changelog entry after opening a pull request

Review and install community skills from monitored registries. Check sources, licenses, permissions, and quality; display the full SKILL.md and findings; then install and record the result only after explicit user approval.

• Reviewing a community skill before installation
• Checking permissions, network calls, and file changes
• Comparing sources and licenses against an allowlist