aif-qa

Analyze code changes, produce test plans, and detail test cases.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/vanyastaff/flui-v2 --skill aif-qa-vanyastaff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-qa
Source: https://github.com/vanyastaff/flui-v2/tree/main/.claude/skills/aif-qa
Command: npx skills add https://github.com/vanyastaff/flui-v2 --skill aif-qa-vanyastaff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, and includes references (resource) and assets (resource) components.

What problem does it solve?

It simplifies the process of verifying feature implementations by automating change analysis, test planning, and scenario description, thereby reducing manual effort and ensuring thorough testing.

Core Features & Use Cases

  • Change Analysis: Automatically summarizes code changes, assesses risks, and generates change summaries.
  • Test Planning: Creates structured test plans based on the change context and project architecture.
  • Test Scenario Description: Details concrete test cases covering both positive and negative scenarios.
  • Use Case: When a developer pushes updates, QA can quickly generate a risk-based test plan and detailed test cases to verify functionality effectively.

Quick Start

Invoke this skill by describing the feature or change you want to test, such as "test this branch" or "write test plan" for recent updates.

Frequently Asked Questions about aif-qa

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

FAQPage Schema
How do I generate a test plan from code changes automatically?

You can generate a risk-based test plan from code changes by invoking this skill with a command like "test this branch". It automatically analyzes recent updates, assesses risks, and structures a comprehensive test plan based on the project architecture.

How do I write test cases that cover edge cases and adjacent functionality?

To write test cases covering edge cases and adjacent functionality, this skill details concrete positive and negative test scenarios. It systematically analyzes code changes to ensure comprehensive coverage of critical functionality through structured documentation.

What is risk-based testing and how does change analysis support it?

Risk-based testing prioritizes validating critical functionality by assessing the potential impact of code changes. This skill supports risk-based testing by automatically summarizing code updates and evaluating associated risks to guide the creation of targeted test plans.

Do I need git to analyze code changes for quality assurance?

Yes, git is required as a dependency to analyze code changes for quality assurance. The skill relies on git to detect recent updates, summarize change contexts, and produce the risk-based test plans needed for thorough feature validation.

Can I use this test planning workflow for both positive and negative test scenarios?

Yes, this test planning workflow explicitly supports both positive and negative test scenarios. It details concrete test cases that ensure systematic validation of critical, adjacent, and edge case functionality based on the analyzed code changes.