grace-refresh

Synchronize GRACE shared artifacts with the actual codebase.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Synchronize the GRACE shared artifacts with the actual codebase.

Core Features & Use Cases

  • Targeted refresh: run focused synchronization after controlled waves.
  • Full refresh: run comprehensive synchronization after refactors or when drift is suspected between the graph, verification plan, and code.
  • Use Case: Maintain alignment of GRACE contracts and validation artifacts with evolving code during active development.

Quick Start

Run grace refresh with a targeted scope after a wave to align drift, or a full refresh after refactors to restore graph-to-code consistency.

Frequently Asked Questions about grace-refresh

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

FAQPage Schema
How do I synchronize GRACE artifacts with code after refactoring?

Synchronize GRACE artifacts with code after refactoring by running a full refresh to restore graph-to-code consistency. This comprehensive mode resolves suspected drift across the graph, verification plan, and codebase.

What is the best way to fix artifact-code drift during active development?

Fix artifact-code drift during active development by running a targeted refresh. This focused synchronization mode aligns GRACE contracts and validation artifacts with the evolving codebase after specific development waves.

Does grace-refresh support preflight checks before synchronizing the codebase?

Yes, grace-refresh supports optional preflight checks before synchronizing the codebase. These checks provide stepwise guidance to validate alignment and resolve graph and verification plan drift.

When should I use a full refresh instead of a targeted refresh for artifact alignment?

Use a full refresh instead of a targeted refresh when you suspect widespread drift between the graph, verification plan, and code after major refactors. Targeted refreshes are better suited for controlled waves during active development.

How does the verification plan synchronization work with the codebase graph?

Verification plan synchronization works by aligning the plan with the codebase graph during a refresh cycle. It validates that the graph, verification plan, and code remain consistent and resolves any detected drift.