aif-qa

Generates change summaries, test plans, and test cases from git branch diffs.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/1t1sCooL/zazyvala-bot --skill aif-qa-1t1scool
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-qa
Source: https://github.com/1t1sCooL/zazyvala-bot/tree/main/.cursor/skills/aif-qa
Command: npx skills add https://github.com/1t1sCooL/zazyvala-bot --skill aif-qa-1t1scool

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manually reviewing a feature branch and figuring out what to test is slow and error-prone. This Skill analyzes the commits and diff of a branch, assesses risks, and produces a structured QA workflow: change summary, test plan, and concrete test cases. ## Core Features & Use Cases - Change Summary: Analyzes git commits and diffs against a base branch, explores key changed files, and produces a risk-assessed summary of what changed. - Test Plan: Builds a structured test plan with scope, test types, priorities, test data, and acceptance criteria based on the change summary. - Test Cases: Writes concrete positive, negative, edge-case, and regression test scenarios with steps, expected results, and test data. - Use Case: After finishing a feature branch, run the full pipeline to get a change summary, a prioritized test plan, and executable test cases saved under .ai-factory/qa/<branch-slug>/. ## Quick Start Ask the AI to run the QA pipeline on your current branch, for example: run aif-qa with --all to analyze this branch and produce a test plan and test cases.

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

Run the skill with the test-plan mode and a branch name. It reads the previously generated change-summary artifact for that branch, defines test scope and types, and saves a structured test plan to the branch's QA artifact directory.

How to analyze what changed in a feature branch before testing?

Use the change-summary mode, which runs git log and git diff against the configured base branch, explores key changed files with subagents, and produces a risk-assessed summary of affected components and testing recommendations.

Can I run the full QA workflow in one command?

Yes, pass the --all flag to run change-summary, test-plan, and test-cases sequentially without inter-stage prompts. Each stage saves its artifact before the next begins, and the pipeline stops if any stage fails.

Does the QA skill write automated tests or use testing frameworks?

No, the skill explicitly does not suggest automated tests or mention testing frameworks. It produces manual QA documentation: change summaries, test plans, and step-by-step test cases with concrete test data.

What happens if the diff is too large to analyze?

If the diff exceeds roughly 1000 lines or there are more than 20 commits, the skill asks how to proceed: analyze everything, limit to the last 20 commits, read files individually via Explore agents, or cancel.

Why does test-plan mode refuse to run on my branch?

Test-plan mode requires an existing change-summary artifact for the resolved branch, and test-cases requires both prior artifacts. Run the earlier stages first, since the workflow enforces strict sequential ordering.