qa-level-assessment

Determine QA levels for software changes by scoring risk and complexity.

Updated Jan 22, 2026

Search Tags:#testing #qa #quality-assurance #code-review #risk #pull-request

Ready to run

npx skills add https://github.com/884js/agent-skills --skill qa-level-assessment

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-level-assessment
Source: https://github.com/884js/agent-skills/tree/main/skills/qa-level-assessment
Command: npx skills add https://github.com/884js/agent-skills --skill qa-level-assessment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill helps teams determine the appropriate QA rigor for PRs and story changes by combining narrative descriptions, code diffs, and dialogue to assess risk and propose actionable QA levels.

Core Features & Use Cases

Follows a three-phase workflow (Phase 1 Information gathering, Phase 2 Risk evaluation, Phase 3 QA level decision) to systematically assess changes.
Supports structured risk scoring with predefined criteria for potential issues, including data handling, external integrations, and schema changes.
Produces a clear QA plan including test scope, required reviews, and recommended QA personnel based on the computed score.

Quick Start

Provide the story overview and PR diffs to get a QA level assessment.

Frequently Asked Questions about qa-level-assessment

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

FAQPage Schema

How do I determine the right QA level for a pull request?▼

To determine the right QA level for a pull request, evaluate the risk and complexity of code changes using a scoring model that combines probability coefficients with risk factors like data handling and schema changes. This produces a clear, actionable QA level.

What is risk-based QA assessment for code changes?▼

Risk-based QA assessment for code changes is a three-phase workflow that gathers information, evaluates risk, and decides a QA level by scoring potential issues across code, tests, and requirements to propose appropriate test scope and reviewers.

How do I assess risk in code reviews before testing?▼

Assess risk in code reviews by applying structured risk scoring with predefined criteria to evaluate potential issues from external integrations, data handling, and schema changes, outputting a targeted QA plan with required personnel.

Can I use story descriptions and PR diffs to evaluate testing scope?▼

Yes, you can use story descriptions and PR diffs to evaluate testing scope. The skill combines narrative descriptions, code diffs, and dialogue to systematically assess risk and produce a targeted QA plan with recommended reviewers.

What is the best way to automate QA level assignment for story changes?▼

The best way to automate QA level assignment for story changes is implementing a scoring model that combines a probability coefficient with multiple risk factors across code, tests, and requirements to output a clear QA level.

When should I use a structured scoring model for quality assurance?▼

Use a structured scoring model for quality assurance when evaluating PRs or story changes involving high-risk factors like external integrations and schema changes, ensuring computed scores translate directly into a clear QA level and test scope.