skills.rest
ichinya
ichinyaCOMMUNITY
Explore all skills by this author →
GitHub

aif-qa

Analyze code changes and generate structured QA artifacts across branches and pull requests.

Updated Aug 27, 2026
Search Tags:#documentation#qa#verification#branching#test-cases#test-plan#change-analysis
One-click install
npx skills add https://github.com/ichinya/idshka --skill aif-qa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aif-qa
Source: https://github.com/ichinya/idshka/tree/main/.codex/skills/aif-qa
Command: npx skills add https://github.com/ichinya/idshka --skill aif-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

QA teams need structured outputs that capture change context and generate actionable testing guidance across change summaries, test plans, and test cases.

Core Features & Use Cases

  • Generate a change summary from code changes compared to a base.
  • Produce a coherent test plan aligned with the identified changes.
  • Create concrete test cases and evidence templates for validation.
  • Support the full QA pipeline (--all) for end-to-end verification.

Quick Start

Invoke the QA workflow by specifying a mode (change-summary, test-plan, or test-cases) or use --all for the full pipeline.

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 code changes across branches?▼

To generate a test plan from code changes, analyze the differences between your current branch and a base branch to produce a change summary, then align a structured test plan with those identified modifications.

What is the best way to create structured test cases for a pull request?▼

Creating structured test cases for a pull request involves analyzing the code changes and generating concrete validation steps, constraints, and acceptance criteria with evidence templates to ensure comprehensive coverage.

Can I run the full QA verification pipeline from change summary to test cases at once?▼

Yes, you can run the full QA verification pipeline at once by invoking the workflow with the --all flag, which produces change summaries, test plans, and test cases end-to-end.

Do I need any external dependencies to generate change summaries for my codebase?▼

No, you do not need any external dependencies to generate change summaries for your codebase, as the QA workflow operates independently to analyze code changes and produce structured testing artifacts.

How does change analysis work for creating QA documentation?▼

Change analysis for creating QA documentation works by comparing code modifications against a base reference to extract context, which is then formatted into structured change summaries and actionable test plans.

When should I use automated test case generation instead of manual test planning?▼

Automated test case generation should be used when you need structured, coherent test plans and evidence templates quickly derived from code changes across branches, ensuring clear steps and acceptance criteria without manual effort.

Related Skills

Explore More Software Engineering Skills→
JsplixJsplix

code-review-pr-body

Generate structured pull request body drafts from git diffs.

Community
Intermediate
dangelesdangeles
6

completion-verifier

Verify task completion against acceptance criteria and generate a verification report.

Community
Advanced
telagodtelagod
68

git-workflow

Implement and manage Git workflows with branching, commit, and pull request guidelines.

Community
Intermediate
seiei-sogenseiei-sogen

dev-webtest-plan

Generate and update Playwright end-to-end test plans from development specifications.

Community
Advanced