aif-qa

Automate QA by generating change summaries, test plans, and test cases.

Updated Jun 13, 2026
One-click install
npx skills add https://github.com/n-marusov/vedo-help --skill aif-qa-n-marusov
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: aif-qa
Source: https://github.com/n-marusov/vedo-help/tree/main/.agents/skills/aif-qa
Command: npx skills add https://github.com/n-marusov/vedo-help --skill aif-qa-n-marusov

SYSTEM DOCUMENTATION & REQUIREMENTS

πŸ’‘ This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the QA workflow for testing feature or task implementations, generating change summaries, test plans, and test scenarios.

Core Features & Use Cases

  • Change Summary Generation: Analyze code changes, assess risks, and produce summaries.
  • Test Plan Creation: Based on change summaries, create structured test plans.
  • Test Case Description: Describe concrete test scenarios based on the test plan.
  • Use Case: When a developer says "test this feature" or "write test plan for this branch", the Skill generates the necessary documentation.

Quick Start

Run /aif-qa change-summary <branch> to generate a change summary for a specific branch.

Frequently Asked Questions about aif-qa

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

FAQPage Schema
How do I automate QA workflow and generate test plans for feature branches?β–Ό

You can automate QA workflows by analyzing code changes to generate change summaries, structured test plans, and concrete test scenarios. Running a command like `/aif-qa change-summary <branch>` parses the codebase and produces the necessary documentation for testing feature implementations.

What is code change summary generation in software testing?β–Ό

Code change summary generation analyzes codebase modifications to assess risks and produce summaries. This process evaluates feature implementations to determine impact, serving as the foundation for creating structured test plans and specific test cases.

How do I write test cases based on code changes in my repository?β–Ό

To write test cases from code changes, the Skill parses configuration files and analyzes the codebase to describe concrete test scenarios. It uses the generated change summary and structured test plan to automate the creation of these test case descriptions.

Can I use QA automation scripts without external dependencies?β–Ό

Yes, QA automation scripts can run without external dependencies. The Skill operates independently using predefined scripts and references to parse configuration files and analyze code changes for generating test plans and change summaries.

What is the best way to create structured test plans from codebase analysis?β–Ό

The best way to create structured test plans is by automating codebase analysis to assess risks and generate change summaries first. The Skill then uses these summaries to automatically produce structured test plans and describe concrete test scenarios.

Does QA automation work for analyzing specific feature branches?β–Ό

Yes, QA automation works for specific feature branches by executing predefined scripts that parse configuration files and analyze code changes. You can generate a change summary for a specific branch to assess risks and create corresponding test plans.