Qa Phase

Organization

ww-w-ai

qa-phase

Run QA tests at various levels (L1-L5) for features under PDCA management. Integrates with MCP tools to execute structured test plans. Use proactively when user asks to test, validate, or run QA on a feature. Triggers: qa, test, QA, quality assurance, run tests, test plan, 테스트, QA, 품질 보증, 검증, 테스트 실행, テスト, QA, 品質保証, テスト実行, 测试, QA, 质量保证, 运行测试, prueba, QA, aseguramiento de calidad, ejecutar pruebas, test, QA, assurance qualité, exécuter les tests, Test, QA, Qualitätssicherung, Tests ausführen, test, QA, garanzia di qualità, eseguire test Do NOT use for: unit test writing (just write them), production monitoring

Overview

Publisher	ww-w-ai
Repository	`bkit-gemini`
Skill name	`qa-phase`
Stars	66
Forks	16
Bundled files	Instructions only
License	Apache-2.0
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by ww-w-ai on GitHub. Read the source before you install it.

Installation

Install the Qa Phase AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/ww-w-ai/bkit-gemini.git /tmp/bkit-gemini
mkdir -p .claude/skills
cp -r /tmp/bkit-gemini/skills/qa-phase .claude/skills/qa-phase

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Qa Phase in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Qa Phase on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Qa Phase is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

QA Phase Skill

Structured QA testing with 5 levels from syntax to production-readiness

Commands

Command	Description	Example
`/qa-phase [feature]`	Run default (L2) QA	`/qa-phase user-auth`
`/qa-phase [feature] --level L1`	Syntax check only	`/qa-phase user-auth --level L1`
`/qa-phase [feature] --level L3`	Full test suite	`/qa-phase user-auth --level L3`
`/qa-phase [feature] --level L5`	Production readiness	`/qa-phase user-auth --level L5`

MCP Integration

This skill uses the bkit_qa_run MCP tool to execute QA tests.

How to Execute

Parse the feature name and level from arguments
Call bkit_qa_run with { feature, level }
Display results with pass/fail indicators
If failures found, suggest specific fixes

QA Levels

L1: Syntax and Lint

File syntax validation (node -c, tsc --noEmit, etc.)
Linting rules (ESLint, Prettier)
Import/require resolution check
No build errors

L2: Unit and Logic (Default)

All of L1, plus:

Unit test execution (Jest, Mocha, Vitest)
Test coverage check (minimum threshold)
Logic validation against Design document
Edge case identification

L3: Integration

All of L2, plus:

API endpoint testing
Database query validation
Third-party service mock testing
Cross-module interaction tests

L4: End-to-End

All of L3, plus:

User flow testing (Playwright, Cypress)
Browser compatibility (if web)
Performance benchmarks
Accessibility checks (a11y)

L5: Production Readiness

All of L4, plus:

Security scan (dependency audit, OWASP checks)
Load testing results review
Rollback verification
Documentation completeness
Deploy checklist validation

Test Plan Generation

When no existing tests are found:

Read the Design document for the feature
Extract testable requirements
Generate a test plan with:
- Test case descriptions
- Expected inputs and outputs
- Edge cases to cover
Write test plan to docs/qa/{feature}-test-plan.md

Output Format

markdown
## QA Report: {feature} (Level {level})

### Summary
- Level: L2 (Unit and Logic)
- Total checks: 24
- Passed: 22
- Failed: 2
- Coverage: 87%

### Results

#### L1: Syntax and Lint
- [PASS] File syntax valid (8/8 files)
- [PASS] ESLint clean (0 errors, 2 warnings)

#### L2: Unit and Logic
- [PASS] Unit tests (18/20 passing)
- [FAIL] Missing test for edge case: empty input
- [FAIL] Coverage below threshold (87% < 90%)

### Recommendations
1. Add test for empty input handling in src/validators/user.js
2. Add tests for error paths in src/api/auth.js to reach 90% coverage

Integration with PDCA

QA Phase maps to the Check phase:

Complete implementation (Do phase)
Run /qa-phase {feature} --level L2 for initial check
Fix issues and re-run until passing
Run /qa-phase {feature} --level L3+ for deeper validation
Results feed into /pdca analyze match rate calculation

Frequently asked questions

What does the Qa Phase AI skill do?

Why use Qa Phase on TypingMind?

Because you install it once and use it with any model. Qa Phase is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Qa Phase in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/ww-w-ai/bkit-gemini/tree/main/skills/qa-phase. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Qa Phase?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Qa Phase?

As many as you like. As long as a model supports skills, you can use Qa Phase with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Qa Phase AI skill free?

Yes. It is published on GitHub by ww-w-ai under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Angular Developer

affaan-m

CommunityPopular

Angular コードを生成し、アーキテクチャガイダンスを提供します。プロジェクトの作成、コンポーネント、またはサービスを作成するとき、または反応性（シグナル、linkedSignal、リソース）、フォーム、依存性注入、ルーティング、SSR、アクセシビリティ（ARIA）、アニメーション、スタイリング（コンポーネントスタイル、Tailwind CSS）、テスト、または CLI ツール作成のベスト…

Skill Creator

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a…

Next Cache Components Adoption

vercel

OrganizationPopular

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the `cacheComponents` flag, work…

Next Cache Components Optimizer

vercel

OrganizationPopular

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

QA Phase Skill

Commands

MCP Integration

How to Execute

QA Levels

L1: Syntax and Lint

L2: Unit and Logic (Default)

L3: Integration

L4: End-to-End

L5: Production Readiness

Test Plan Generation

Output Format

Integration with PDCA

Frequently asked questions

Related AI Skills

Set up your own AI workspace now