qa-init

Initializes QASE context by detecting project stack and generating config files.

1|Updated Mar 3, 2026

Search Tags:#code quality #architecture #persistence #initialization #context detection #qase

Ready to run

npx skills add https://github.com/dev-gios/agent-teams-qa --skill qa-init

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-init
Source: https://github.com/dev-gios/agent-teams-qa/tree/main/skills/qa-init
Command: npx skills add https://github.com/dev-gios/agent-teams-qa --skill qa-init

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill initializes the QASE (QA-Squad-Excellence) review context within a project, detecting its unique characteristics to tailor future code quality reviews.

Core Features & Use Cases

Project Context Detection: Analyzes tech stack, architecture patterns, existing quality tooling, security posture, and accessibility baseline.
Persistence Backend Setup: Configures either 'engram' or 'openspec' for storing review context and artifacts, or operates ephemerally if 'none'.
Configuration Generation: Creates qaspec/config.yaml and qaspec/init.yaml for 'openspec' mode, defining project-specific rules and context.
Use Case: When starting a new project or integrating QASE into an existing one, run qa-init to establish the foundational context for all subsequent code quality checks.

Quick Start

Initialize QASE in the current project.

Frequently Asked Questions about qa-init

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I initialize code quality review context for an existing project?▼

To initialize code quality review context, run the setup process to detect your project stack, architecture, and existing quality tooling. It bootstraps a persistence backend and generates configuration files to tailor future code reviews.

What is project context detection for code quality reviews?▼

Project context detection for code quality reviews is the process of analyzing tech stack, architecture patterns, and existing quality tools. This mechanism ensures that automated checks are tailored to the specific characteristics of your codebase.

How do I configure a persistence backend for storing review artifacts?▼

Configuring a persistence backend for storing review artifacts involves selecting 'engram', 'openspec', or 'none' during initialization. This choice dictates whether your context and artifacts are stored persistently or operated ephemerally.

Does this code quality initialization work with any tech stack?▼

Yes, this code quality initialization works by analyzing project files like package.json to detect the tech stack. It identifies architectural patterns and existing quality tools to tailor the review context to your specific environment.

What configuration files are generated during code review context setup?▼

During code review context setup, the process generates `qaspec/config.yaml` and `qaspec/init.yaml` when using the 'openspec' persistence mode. These files define project-specific rules and context for tailored code quality reviews.

When should I not use a persistence backend for review artifacts?▼

You should not use a persistence backend for review artifacts when you want ephemeral operation. Selecting 'none' during initialization bypasses 'engram' or 'openspec' setup, operating without storing persistent context or artifacts.