huang
353621d923
All checks were successful
构建并部署到测试环境（无 SSH） / build-and-deploy (push) Successful in 6m33s
**变更说明**: - 删除所有 *_test.go 文件（单元测试、集成测试、验收测试、流程测试） - 删除整个 tests/ 目录 - 更新 CLAUDE.md：用"测试禁令"章节替换所有测试要求 - 删除测试生成 Skill (openspec-generate-acceptance-tests) - 删除测试生成命令 (opsx:gen-tests) - 更新 tasks.md：删除所有测试相关任务 **新规范**: - ❌ 禁止编写任何形式的自动化测试 - ❌ 禁止创建 *_test.go 文件 - ❌ 禁止在任务中包含测试相关工作 - ✅ 仅当用户明确要求时才编写测试 **原因**: 业务系统的正确性通过人工验证和生产环境监控保证，测试代码维护成本高于价值。 Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
132 lines
4.2 KiB
Markdown
132 lines
4.2 KiB
Markdown
---
|
|
description: Sync delta specs from a change to main specs
|
|
---
|
|
|
|
Sync delta specs from a change to main specs.
|
|
|
|
This is an **agent-driven** operation - you will read delta specs and directly edit main specs to apply the changes. This allows intelligent merging (e.g., adding a scenario without copying the entire requirement).
|
|
|
|
**Input**: Optionally specify a change name after `/opsx-sync` (e.g., `/opsx-sync add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
|
|
|
|
**Steps**
|
|
|
|
1. **If no change name provided, prompt for selection**
|
|
|
|
Run `openspec list --json` to get available changes. Use the **AskUserQuestion tool** to let the user select.
|
|
|
|
Show changes that have delta specs (under `specs/` directory).
|
|
|
|
**IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.
|
|
|
|
2. **Find delta specs**
|
|
|
|
Look for delta spec files in `openspec/changes/<name>/specs/*/spec.md`.
|
|
|
|
Each delta spec file contains sections like:
|
|
- `## ADDED Requirements` - New requirements to add
|
|
- `## MODIFIED Requirements` - Changes to existing requirements
|
|
- `## REMOVED Requirements` - Requirements to remove
|
|
- `## RENAMED Requirements` - Requirements to rename (FROM:/TO: format)
|
|
|
|
If no delta specs found, inform user and stop.
|
|
|
|
3. **For each delta spec, apply changes to main specs**
|
|
|
|
For each capability with a delta spec at `openspec/changes/<name>/specs/<capability>/spec.md`:
|
|
|
|
a. **Read the delta spec** to understand the intended changes
|
|
|
|
b. **Read the main spec** at `openspec/specs/<capability>/spec.md` (may not exist yet)
|
|
|
|
c. **Apply changes intelligently**:
|
|
|
|
**ADDED Requirements:**
|
|
- If requirement doesn't exist in main spec → add it
|
|
- If requirement already exists → update it to match (treat as implicit MODIFIED)
|
|
|
|
**MODIFIED Requirements:**
|
|
- Find the requirement in main spec
|
|
- Apply the changes - this can be:
|
|
- Adding new scenarios (don't need to copy existing ones)
|
|
- Modifying existing scenarios
|
|
- Changing the requirement description
|
|
- Preserve scenarios/content not mentioned in the delta
|
|
|
|
**REMOVED Requirements:**
|
|
- Remove the entire requirement block from main spec
|
|
|
|
**RENAMED Requirements:**
|
|
- Find the FROM requirement, rename to TO
|
|
|
|
d. **Create new main spec** if capability doesn't exist yet:
|
|
- Create `openspec/specs/<capability>/spec.md`
|
|
- Add Purpose section (can be brief, mark as TBD)
|
|
- Add Requirements section with the ADDED requirements
|
|
|
|
4. **Show summary**
|
|
|
|
After applying all changes, summarize:
|
|
- Which capabilities were updated
|
|
- What changes were made (requirements added/modified/removed/renamed)
|
|
|
|
**Delta Spec Format Reference**
|
|
|
|
```markdown
|
|
## ADDED Requirements
|
|
|
|
### Requirement: New Feature
|
|
The system SHALL do something new.
|
|
|
|
#### Scenario: Basic case
|
|
- **WHEN** user does X
|
|
- **THEN** system does Y
|
|
|
|
## MODIFIED Requirements
|
|
|
|
### Requirement: Existing Feature
|
|
#### Scenario: New scenario to add
|
|
- **WHEN** user does A
|
|
- **THEN** system does B
|
|
|
|
## REMOVED Requirements
|
|
|
|
### Requirement: Deprecated Feature
|
|
|
|
## RENAMED Requirements
|
|
|
|
- FROM: `### Requirement: Old Name`
|
|
- TO: `### Requirement: New Name`
|
|
```
|
|
|
|
**Key Principle: Intelligent Merging**
|
|
|
|
Unlike programmatic merging, you can apply **partial updates**:
|
|
- To add a scenario, just include that scenario under MODIFIED - don't copy existing scenarios
|
|
- The delta represents *intent*, not a wholesale replacement
|
|
- Use your judgment to merge changes sensibly
|
|
|
|
**Output On Success**
|
|
|
|
```
|
|
## Specs Synced: <change-name>
|
|
|
|
Updated main specs:
|
|
|
|
**<capability-1>**:
|
|
- Added requirement: "New Feature"
|
|
- Modified requirement: "Existing Feature" (added 1 scenario)
|
|
|
|
**<capability-2>**:
|
|
- Created new spec file
|
|
- Added requirement: "Another Feature"
|
|
|
|
Main specs are now updated. The change remains active - archive when implementation is complete.
|
|
```
|
|
|
|
**Guardrails**
|
|
- Read both delta and main specs before making changes
|
|
- Preserve existing content not mentioned in delta
|
|
- If something is unclear, ask for clarification
|
|
- Show what you're changing as you go
|
|
- The operation should be idempotent - running twice should give same result
|