Skip to content

feat(verify): detect semantic planning residue#1373

Draft
Seekers2001 wants to merge 1 commit into
Fission-AI:mainfrom
Seekers2001:codex/verify-semantic-relevance
Draft

feat(verify): detect semantic planning residue#1373
Seekers2001 wants to merge 1 commit into
Fission-AI:mainfrom
Seekers2001:codex/verify-semantic-relevance

Conversation

@Seekers2001

Copy link
Copy Markdown

What changed

  • add Relevance as a fourth verification dimension in both the generated openspec-verify-change skill and /opsx:verify command
  • audit changed implementation elements for traceable links to requirements, tasks, design decisions, or necessary enabling roles
  • require reference and data-flow evidence before reporting planning residue
  • keep pre-existing debt out of scope and downgrade uncertain findings to suggestions
  • update the verify documentation and add parity coverage for both generated templates

Why

Issue #1073 proposes an optional semantic cleanup checkpoint after implementation and before verification/archive. This draft integrates that checkpoint into the existing optional /opsx:verify workflow rather than adding another command. It keeps the workflow surface small while placing the check immediately before archive.

Impact

This changes generated verification instructions and documentation only. It does not automatically remove code or block archive; it reports evidence-backed warnings and suggestions for human review.

Validation

  • OPENSPEC_TELEMETRY=0 ./node_modules/.bin/vitest run — 100 test files, 1,876 tests passed
  • node build.js
  • ./node_modules/.bin/eslint src/ — 0 errors
  • git diff --check

Review note

This is a draft specifically to confirm that extending /opsx:verify is preferable to introducing a separate checkpoint command.

Prepared with Codex assistance and reviewed locally for scope and false-positive boundaries.

Addresses #1073

@coderabbitai

coderabbitai Bot commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: c16dace7-e765-419d-a417-e36e16b54e90

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant