skills.rest
putrawitama
putrawitamaCOMMUNITY
Explore all skills by this author →
GitHub

qa-only

Identify and document QA issues without applying code changes.

1|1|Updated Mar 31, 2026
Search Tags:#workflow#documentation#qa#review#quality-assurance#read-only#bug-report
One-click install
npx skills add https://github.com/putrawitama/DenchClaw --skill qa-only-putrawitama
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/putrawitama/DenchClaw/tree/main/skills/gstack/qa-only
Command: npx skills add https://github.com/putrawitama/DenchClaw --skill qa-only-putrawitama

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enable teams to identify and document QA issues without applying any code changes, ensuring a clear, read-only bug-report trail.

Core Features & Use Cases

  • Read-only QA investigation that navigates the target application, locates issues, and compiles them into a structured report.
  • Suitable for peer reviews, bug-bash sessions, or when fixes are deferred, ensuring traceability without altering production code.
  • Use Case: A reviewer inspects a feature, logs issues with steps to reproduce, and hands off a formal QA REPORT to developers.

Quick Start

Run a read-only QA review and export a structured QA REPORT.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I perform a read-only QA review without altering the source code?▼

A read-only QA review investigates the target application to identify and document issues without applying fixes. It navigates the application, logs issues with steps to reproduce, and compiles a structured bug report.

Can I generate a structured bug report for peer review without fixing the code?▼

Yes, you can generate a structured bug report for peer review by logging issues with evidence and steps to reproduce. This read-only methodology ensures traceability without altering production code.

What is the best way to document QA issues for a bug-bash session?▼

The best way to document QA issues for a bug-bash session is to use a read-only investigation process. This locates issues within the target application and compiles them into a formal QA report for developer handoff.

Does this QA workflow apply fixes to the target application during review?▼

No, this QA workflow does not apply fixes to the target application during review. It follows a strictly read-only methodology to ensure a clear bug-report trail and ends with a structured QA report.

When do I need a read-only quality assurance process instead of direct code changes?▼

You need a read-only quality assurance process when fixes are deferred or during peer reviews. It allows a reviewer to inspect a feature, log issues with steps to reproduce, and hand off a formal QA report.

What limitations exist when using a read-only QA methodology for bug reporting?▼

The primary limitation of this read-only QA methodology is that it does not perform any code changes. It strictly identifies and documents issues, meaning developers must implement the fixes separately.

Related Skills

Explore More Software Engineering Skills→
balic-AI-ML-R-D-Resourcesbalic-AI-ML-R-D-Resources

security-audit-context-building

Map architecture, trust boundaries, and data flows for security audit scoping.

Official
Advanced
brianwestphalbrianwestphal
1

hs-bug

Create categorized Hot Sheet bug tickets from issue descriptions.

Community
Intermediate
semicolon-devteamsemicolon-devteam

e2e-test

Automate Playwright end-to-end tests to validate runtime browser behavior.

Official
Advanced
OneWave-AIOneWave-AI
245

code-review-pro

Review code for security vulnerabilities, performance bottlenecks, and maintainability issues.

Official
Basic