qa-init

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.

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.

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.

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.

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.

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.