openspec-change-reviewer

Name: openspec-change-reviewer
Availability: InStock
Author: Emergent

Review OpenSpec change plans for consistency and codebase alignment.

1|Updated Feb 6, 2026

Search Tags:#design #documentation #consistency #codebase #review #openspec #gaps

Ready to run

npx skills add https://github.com/emergent-company/emergent.memory --skill openspec-change-reviewer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-change-reviewer
Source: https://github.com/emergent-company/emergent.memory/tree/main/.opencode/skills/openspec-change-reviewer
Command: npx skills add https://github.com/emergent-company/emergent.memory --skill openspec-change-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill rigorously reviews proposed changes to OpenSpec documentation against the codebase, identifying logical errors, inconsistencies, and gaps to ensure a high-quality, well-aligned plan.

Core Features & Use Cases

Artifact Analysis: Ingests and analyzes proposals, specs, designs, and tasks.
Consistency Checks: Verifies logical flow between different stages of the change plan.
Codebase Verification: Cross-references plan elements with the actual codebase using search tools.
Gap Identification: Pinpoints missing edge cases, dependencies, tooling, and areas needing more detail.
Use Case: Before merging a new feature, use this Skill to ensure the design document accurately reflects the implementation tasks and doesn't overlook critical error handling or necessary database migrations.

Quick Start

Use the openspec-change-reviewer skill to review the 'add-user-profiles' change.

Frequently Asked Questions about openspec-change-reviewer

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

FAQPage Schema

How do I verify logical consistency between OpenSpec design artifacts and the codebase?▼

To verify logical consistency between OpenSpec artifacts and the codebase, ingest the proposal, specs, design, and task files to check their logical flow, then cross-reference the plan elements with the actual codebase using search tools to confirm alignment.

What is the best way to identify gaps in OpenSpec change plans?▼

Identifying gaps in OpenSpec change plans requires executing a multi-phase review process that analyzes ingested artifacts to pinpoint missing edge cases, dependencies, tooling, testability, and areas requiring further detail.

Can I check if my design document accurately reflects implementation tasks before merging?▼

Yes, you can check if a design document accurately reflects implementation tasks by running a multi-phase review that verifies logical consistency between artifacts and aligns the proposed changes with the actual codebase to find missing error handling or migrations.

How do I review OpenSpec changes for missing dependencies and edge cases?▼

Reviewing OpenSpec changes for missing dependencies and edge cases involves analyzing proposal, specs, design, and task artifacts to identify gaps in testability, tooling, and edge cases through active search and component verification.

Does OpenSpec codebase alignment verification require active search tools?▼

Yes, OpenSpec codebase alignment verification requires active search tools to cross-reference the proposed change plan elements with the actual codebase components, ensuring the design accurately reflects the implementation tasks.