skills.rest
aspectrr
aspectrrCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

qa-only

Document software defects with read-only reporting and evidence capture.

Updated Apr 20, 2026
Search Tags:#testing#documentation#qa#review#read-only#reproduction#bug-reporting
One-click install
npx skills add https://github.com/aspectrr/denchclaw-workspace --skill qa-only-aspectrr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/aspectrr/denchclaw-workspace/tree/main/skills/gstack/qa-only
Command: npx skills add https://github.com/aspectrr/denchclaw-workspace --skill qa-only-aspectrr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This approach lets teams report issues and document defects without modifying source code, preserving stability while enabling thorough reviews.

Core Features & Use Cases

  • Report-only defect documentation: captures steps, evidence, and impact without pushing changes.
  • Safe review workflow: enables stakeholders to review issues before any fixes.
  • Use Case: Example scenario where a tester reports a bug for a feature not to be changed in the codebase.

Quick Start

Generate a read-only QA report for a bug scenario by iterating through baseline, reproduction steps, and impact assessment, then hand off to developers.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I document software defects without modifying the source code?▼

To document software defects without modifying source code, use a report-only QA workflow. This approach captures reproduction steps, evidence, and impact assessments while preserving the original codebase for developer handoff.

What is a read-only QA workflow and when should I use it?▼

A read-only QA workflow identifies and reports bugs without pushing code changes. Use it when stakeholders need to review issues and assess impact safely before authorizing any fixes in the codebase.

How do I create a bug report for developers without changing the codebase?▼

Create a bug report by iterating through baseline behavior, reproduction steps, and impact assessment. This captures the evidence needed for developers while enforcing a strict read-only environment.

Can I perform QA testing and issue documentation without pushing code changes?▼

Yes, you can perform QA testing and issue documentation without pushing changes. This method enforces read-only reporting to preserve stability, ensuring testers only find and document issues for developers.

What are the limitations of a report-only QA approach for bug discovery?▼

The limitation of report-only QA is that it strictly identifies and documents defects without applying fixes. It preserves the original code but requires a separate developer workflow to resolve the reported issues.

Does report-only QA work for reviewing issues across multiple projects?▼

Report-only QA is applicable to bug discovery and review workflows across projects. It enables safe, standardized issue documentation by capturing reproduction steps and evidence without altering source code.

Related Skills

Explore More Software Engineering Skills→
1molchuan1molchuan
1

oh-my-ccg-init

Verify MCP, Codex, and Gemini endpoints and initialize RPI state.

Community
Intermediate
first-flukefirst-fluke
218

debug-agent

Diagnose software bugs and propose minimal regression-tested fixes.

Official
Advanced
rkz91rkz91
264

gsd-pause-work

Capture work state and create timestamped .continue-here.md handoff files.

Community
Advanced
sast-playgroundsast-playground

dashboard-testing

Test Aspire Dashboard models and Blazor components with xUnit and bUnit.

Official
Intermediate