aif-qa

Generate test plans and executable test cases from git branch changes.

Updated May 16, 2026
One-click install
npx skills add https://github.com/vulikjulik/DeepLom --skill aif-qa-vulikjulik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-qa
Source: https://github.com/vulikjulik/DeepLom/tree/main/.opencode/skills/aif-qa
Command: npx skills add https://github.com/vulikjulik/DeepLom --skill aif-qa-vulikjulik

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the tedious, inconsistent manual work of creating test plans and test cases for new feature or task implementations, ensuring no critical edge cases, regression risks, or high-priority functional gaps are missed during QA.

Core Features & Use Cases

  • Change Summary Analysis: Automatically analyze git branch changes to identify modified components, associated risks, and affected system areas.
  • Structured Test Plan Generation: Create prioritized, scoped test plans aligned with change analysis, covering functional, regression, edge case, and security testing requirements.
  • Concrete Test Case Creation: Generate executable, step-by-step test scenarios with specific test data for positive, negative, and edge case validation.
  • Use Case: For example, when a developer completes a branch adding new MetaMask wallet login functionality, use this skill to analyze the changes, generate a test plan covering role-based access and session handling, and write concrete test cases for valid/invalid wallet signatures and permission checks.

Quick Start

Use the aif-qa skill to run the full QA pipeline (change summary, test plan, and test cases) for your current feature branch.

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 git branch changes?

Generating a test plan from git branch changes involves analyzing modified components and associated risks to produce a prioritized, structured test plan covering functional, regression, and edge case testing requirements.

What is automated test case creation for feature testing?

Automated test case creation for feature testing is generating executable, step-by-step scenarios with specific test data for positive, negative, and edge case validation based on analyzed code changes.

Can I use this QA workflow for regression testing on specific features?

Yes, you can apply this QA workflow for regression testing on specific features by analyzing git-backed code changes to identify affected system areas and translating them into structured, dependency-aware test plans.

Does this test planning tool work with standard git-workflow development?

Yes, this test planning tool works with standard git-workflow development by analyzing code changes from feature branches to automatically identify modified components, associated risks, and affected system areas.

What's the best way to analyze code changes for risk before writing test cases?

The best way to analyze code changes for risk before writing test cases is to perform change summary analysis on git branches to identify modified components and prioritize high-risk functional areas for test plan generation.