aif-qa

To generate a test plan from git branch changes, an automated QA workflow compares your branches to assess functional risks and outputs structured test plans. Running this skill with the --all flag creates a full QA pipeline for your current branch.

Automated regression testing analyzes code changes to identify risks and affected areas before merging. It standardizes feature verification by automatically generating change summaries, comprehensive test plans, and concrete test scenarios based on specific implementation details of a branch.

Yes, you need project-specific architecture and description files to generate manual QA artifacts. These files provide the necessary context to ensure context-aware verification and produce accurate change summaries, test plans, and test cases for your feature testing.

Yes, you can manually input code changes for test case generation without relying solely on git branches. The system operates by comparing git branches or accepting manual input to assess functional and regression risks and generate structured test cases.

The best way to standardize feature testing documentation is to implement an automated QA workflow that generates consistent change summaries, test plans, and test cases. This addresses manual overhead and inconsistency by producing structured manual QA artifacts for every new feature.

Generated test cases may miss edge cases if the system lacks sufficient project context. Providing accurate project-specific architecture and description files ensures context-aware verification, allowing the system to produce comprehensive test scenarios covering edge cases before merging.