Determine QA levels for software changes by scoring risk and complexity.
npx skills add https://github.com/884js/agent-skills --skill qa-level-assessment
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
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.
Provide the story overview and PR diffs to get a QA level assessment.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
lemigAnalyze PR diffs for SQL safety, LLM trust boundaries, and side effects.
Negentropy-LabyGenerate structured QA plans from CDDs and story files.
tomholfordReview pull requests for code quality, security, performance, and pattern adherence.
MiDouTechEvaluate product or engineering change risks with a MECE six-dimension matrix.
