aif-qa

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

31|2|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/letuhao/lore-weave --skill aif-qa-letuhao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-qa
Source: https://github.com/letuhao/lore-weave/tree/main/.cursor/skills/aif-qa
Command: npx skills add https://github.com/letuhao/lore-weave --skill aif-qa-letuhao

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 what changed in a branch, assesses risks, and produces a structured manual QA workflow — change summary, test plan, and concrete test cases — saved as Markdown artifacts. ## Core Features & Use Cases - Change Summary: Analyzes git diffs and commit history against a base branch, explores changed files, and produces a risk-assessed summary with evidence tied to files and commits. - Test Plan: Builds a structured test plan from the change summary, defining scope, test types, priorities, test data, and acceptance criteria. - Test Cases: Describes concrete manual test scenarios (positive, negative, edge case, regression) with steps, expected results, and test data. - Use Case: After finishing a feature branch, run the full pipeline to get a complete QA package — what changed, what to verify, and exactly how to verify it — without writing the plan by hand. ## Quick Start Ask the assistant to run the QA pipeline on your current branch, for example: run aif-qa with --all to analyze this branch and produce the change summary, 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 argument and a branch name. It reads the previously generated change-summary artifact for that branch, defines scope and test types, and saves a structured test-plan.md with priorities and acceptance criteria.

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

Use the change-summary mode, which diffs the branch against the configured base branch, lists commits and changed files, explores key files, and produces a risk-assessed summary with evidence linked to files and commits.

Can I run change summary, test plan, and test cases in one step?

Yes, pass the --all flag to run the full pipeline sequentially. Each stage saves its artifact and the next stage starts automatically without inter-stage prompts, stopping if any stage fails.

Does the QA workflow work without a git repository?

Yes. If git is disabled or the directory is not a git work tree, the skill switches to manual change context mode and asks you to provide a pasted diff, a changed-file list, or a short implementation description.

Why does test-cases mode stop with an artifact not found error?

Test cases require both change-summary.md and test-plan.md artifacts for the resolved branch. The stages are strictly sequential, so you must run change-summary and test-plan first before generating test cases.

Can QA artifacts be generated in languages other than English?

Yes. The skill reads language settings from .ai-factory/config.yaml and writes artifacts in the configured artifact language, translating headings, steps, and expected results while keeping code identifiers, paths, and commands unchanged.