gf/openspec/specs/code-quality-gates/spec.md

# code-quality-gates Specification

## Purpose
TBD - created by archiving change add-unit-test-coverage-requirements. Update Purpose after archive.
## Requirements
### Requirement: Submitted code changes include unit tests
The project SHALL require every submitted code change to include unit tests that directly cover the affected logic and expected behavior of the changed code path in the affected package.

#### Scenario: Behavior-changing code is submitted
- **WHEN** a contribution adds or changes code in the repository
- **THEN** the submission SHALL include unit tests that exercise the affected logic or preserve the expected behavior of the changed code path before the change is considered complete

### Requirement: Newly added code meets the coverage baseline
The project SHALL require the newly added code in a submission to maintain unit-test coverage of at least 80%, and reviews SHALL treat 90% or above as the preferred target when that level is feasible without artificial or low-value tests.

#### Scenario: Coverage falls below the minimum
- **WHEN** the newly added code in a submission is covered below 80%
- **THEN** the change SHALL not satisfy the project quality requirement

#### Scenario: Coverage meets the minimum baseline
- **WHEN** the newly added code in a submission reaches 80% or higher coverage
- **THEN** the change SHALL satisfy the minimum coverage requirement

#### Scenario: Coverage reaches the preferred target
- **WHEN** the newly added code in a submission reaches 90% or higher coverage
- **THEN** the change SHALL satisfy the preferred coverage target for the project
feat(cmd/gf): add gendao fileNameCase and ai coding stuffs (#4764) This pull request introduces new and updated prompt and instruction documents for the experimental OPSX workflow system, providing detailed, step-by-step guidance for proposing, applying, archiving, and exploring changes using OpenSpec. The changes standardize workflow guardrails, clarify user interactions, and ensure consistent artifact handling across all major workflow operations. OPSX Workflow Prompt Additions and Enhancements: * Propose Workflow - Adds `.agents/prompts/opsx/propose.md` outlining how to propose a new change, including artifact creation order, dependency handling, and user input requirements. Emphasizes using schema-defined instructions and templates, and clarifies that context/rules are for internal guidance only. * Apply Workflow - Introduces `.agents/prompts/opsx/apply.md` detailing the process for implementing tasks from an OpenSpec change. Covers change selection, context reading, task loop execution, state handling, and output formatting. Includes guardrails for ambiguity, blockers, and minimal change scope. * Archive Workflow - Adds `.agents/prompts/opsx/archive.md` specifying the process for archiving completed changes, including artifact/task completion checks, delta spec sync assessment, user prompts for incomplete work, and summary output. Ensures robust handling of archive naming conflicts and user confirmations. * Explore Mode - Adds `.agents/prompts/opsx/explore.md` describing "explore mode" for non-implementation discovery, problem investigation, and requirements clarification. Outlines stance, behaviors, and guardrails for thinking and artifact capture without code changes. Documentation Standardization: * Markdown Formatting Standards - Adds `.agents/instructions/markdown-format.instructions.md` to standardize markdown document formatting, including heading levels, code block usage, list formatting, and language-specific punctuation rules for improved clarity and consistency. 2026-04-25 17:47:05 +08:00			`# code-quality-gates Specification`

			`## Purpose`
			`TBD - created by archiving change add-unit-test-coverage-requirements. Update Purpose after archive.`
			`## Requirements`
			`### Requirement: Submitted code changes include unit tests`
			`The project SHALL require every submitted code change to include unit tests that directly cover the affected logic and expected behavior of the changed code path in the affected package.`

			`#### Scenario: Behavior-changing code is submitted`
			`- WHEN a contribution adds or changes code in the repository`
			`- THEN the submission SHALL include unit tests that exercise the affected logic or preserve the expected behavior of the changed code path before the change is considered complete`

			`### Requirement: Newly added code meets the coverage baseline`
			`The project SHALL require the newly added code in a submission to maintain unit-test coverage of at least 80%, and reviews SHALL treat 90% or above as the preferred target when that level is feasible without artificial or low-value tests.`

			`#### Scenario: Coverage falls below the minimum`
			`- WHEN the newly added code in a submission is covered below 80%`
			`- THEN the change SHALL not satisfy the project quality requirement`

			`#### Scenario: Coverage meets the minimum baseline`
			`- WHEN the newly added code in a submission reaches 80% or higher coverage`
			`- THEN the change SHALL satisfy the minimum coverage requirement`

			`#### Scenario: Coverage reaches the preferred target`
			`- WHEN the newly added code in a submission reaches 90% or higher coverage`
			`- THEN the change SHALL satisfy the preferred coverage target for the project`