grace-reviewer

Validate module contracts and documentation for GRACE integrity.

3|2|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/ShutovKS/tts-server --skill grace-reviewer-shutovks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grace-reviewer
Source: https://github.com/ShutovKS/tts-server/tree/main/.opencode/skills/grace-reviewer
Command: npx skills add https://github.com/ShutovKS/tts-server --skill grace-reviewer-shutovks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GRACE integrity reviewer ensures semantic markup, module contracts, and knowledge-graph coherence across code changes, preventing drift during development and audits.

Core Features & Use Cases

  • Scoped-gate reviews for active execution waves to block unsafe changes.
  • Wave-audit mode to validate cross-module consistency before merging waves.
  • Full-integrity audits at phase boundaries to restore global coherence.

Quick Start

Trigger a scoped-gate review on the changed module to validate GRACE integrity.

Frequently Asked Questions about grace-reviewer

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

FAQPage Schema
How do I validate module contracts and documentation for GRACE integrity in code projects?

To validate GRACE integrity, apply scoped-gate, wave-audit, or full-integrity review modes to check module contracts, verification plans, and documentation. This process prevents drift and ensures alignment across changed files, graph updates, and verification evidence with traceable log evidence.

What is the best way to prevent knowledge-graph drift during code reviews?

Preventing knowledge-graph drift requires applying wave-audit mode to validate cross-module consistency before merging waves, or running full-integrity audits at phase boundaries to restore global coherence across semantic markup and module contracts.

When do I need to run a full-integrity audit versus a scoped-gate review?

Run a scoped-gate review on active execution waves to block unsafe changes immediately, whereas a full-integrity audit is needed at phase boundaries to restore global coherence and validate semantic markup across the entire project.

Does GRACE integrity verification work for cross-module consistency checks before merging?

Yes, GRACE integrity verification supports wave-audit mode specifically designed to validate cross-module consistency before merging waves, guarding against drift and ensuring alignment across graph updates and verification evidence.

How do I ensure semantic markup and contract compliance across changed files?

Ensuring semantic markup and contract compliance involves triggering a scoped-gate review on the changed module to validate GRACE integrity. This provides clear remediation guidance and traceable log evidence for any detected drift.