QA Only

Test an application at its browser, API, CLI, job or webhook surface and report reproducible bugs with evidence, without fixing them. Use for 'QA this and report', 'test the app', 'find bugs but don't fix', 'verify this flow works' or when do needs a runtime check of a change.

9 starsTesting & QA Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add borkweb/skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add borkweb/skills --skill qa-only
Manual install
git clone --depth 1 https://github.com/borkweb/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/gstack/qa-only ~/.claude/skills/qa-only

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# QA Report Only

Test and document the requested application at the selected surface using [shared exploration](../qa/exploration.md). The deliverable is a report and evidence; do not edit application code, tests or configuration, commit, push or merge.

Read source when needed to map a requested diff to routes or understand reproduction, including backend changes that affect user flows. Read-only source tracing is compatible with report-only QA. Use the actual verified base; do not assume main.

Follow the selected quick, diff-aware, full or regression scope. Report real findings, including zero when the evidence supports it. Do not force a quota or award untested categories a perfect score. Report unavailable browser, roles, data or checks as incomplete coverage. A healthy tested route does not establish whole-site health.

Write `qa-report-<domain>-<date>.md` in the requested artifact location with scope, tested coverage, issues, repro steps, evidence and limitations. Propose corrections when useful without applying them. Never claim required verification passed when it did not run.
Read the full skill on GitHub

Details

Skill name
qa-only
Repository
borkweb/skills
Path
skills/gstack/qa-only/SKILL.md
License
MIT
Repo updated
18 November 2026

FAQ

What does the QA Only skill do?

Test an application at its browser, API, CLI, job or webhook surface and report reproducible bugs with evidence, without fixing them. Use for 'QA this and report', 'test the app', 'find bugs but don't fix', 'verify this flow works' or when do needs a runtime check of a change.

How do I install the QA Only skill?

Claude Code plugin: /plugin marketplace add borkweb/skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is QA Only popular?

It lives in borkweb/skills, which has 9 GitHub stars and 0 forks.

Related skills

Prototype

9

borkweb/skills

Build a throwaway prototype to flesh out a design before committing to it. Routes between two branches — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route. Use when the user wants to prototype, sanity-check a data model or state machine, mock up a UI, explore design options, or says "prototype this", "let me play with it", "try a few designs".

Frontend & DesignIn 1 list

Agents Md Lint

9

borkweb/skills

Audit and trim AI agent instruction files (AGENTS.md, CLAUDE.md, CONVENTIONS.md, .cursorrules, etc.) by testing which facts an AI agent can discover from code alone. Use when asked to lint, audit, optimize, prune, or trim any agent instruction file in a repository. Removes redundant documentation that wastes context tokens. Supports a dry-run mode that reports findings without modifying files.

AI, LLMs & Agents

Auto Scope

9

borkweb/skills

Scopes a coding task before implementation — names the handful of files actually relevant (read/edit these), the areas to leave alone, and any open scope questions, so work doesn't start by reading the whole repo. Fires proactively at the start of substantive, multi-file, or unfamiliar-area work; stays silent on single-file edits, one-line fixes, questions, and continued work in an area already scoped this session. Use when beginning a feature, bug fix, or refactor that could plausibly touch several files or an area not yet seen this session.

Software Development

Acceptance Orchestrator

9

huytran1120/vietnam-agentic-skills

Use when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.

Testing & QA

QA

9

borkweb/skills

Test an application at its browser, API, CLI, job or webhook surface and fix reproducible bugs within the requested scope, with evidence and appropriate regression checks. Honors report-only and no-commit requests.

Testing & QA

Test Analyze

9

yasunori0418/skills

ISTQB/JSTQB のテスト分析(test analysis)活動を支援するスキル。テストベース(仕様・設計・コード・リスク)を分析して「何をテストすべきか」= テスト条件(test condition)を識別し、test-plan のプロダクトリスク評価があればそれを入力に優先度を付けた test-analysis.md を作る。「何をテストすべきか洗い出して」「テスト条件を整理して」「テスト観点を出して」「テスト分析して」と依頼されたときに使う。テストケースの導出(test-design)は対象外。単発のテスト作成依頼(単にユニットテストを書きたいだけ)も対象外。/test-analyze <テスト対象名> で明示的に呼び出されたときのみ使用する。

Testing & QA

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.