sync

Validates session artifacts, git state, and plan drift before code execution.

Updated Jul 28, 2026
One-click install
npx skills add https://github.com/truongnat/Restly --skill sync-truongnat
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sync
Source: https://github.com/truongnat/Restly/tree/main/.agents/skills/sync
Command: npx skills add https://github.com/truongnat/Restly --skill sync-truongnat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents often execute against stale plans, dirty workspaces, or outdated assumptions, causing failed or destructive changes. This Skill performs a read-only pre-execution check that surfaces drift, blockers, and risks before any code is modified. ## Core Features & Use Cases - Session Artifact Sync: Reads DISCUSSION.md, PLAN.md, TASKS.md, and EXECUTION.md to confirm the plan is current and aligned with the codebase. - Workspace & Git State Checks: Detects dirty changes, conflict markers, branch mismatches, and out-of-scope modifications without mutating anything. - Readiness Gate: Produces a SYNC.md report with an explicit PASS / CONCERNS / FAIL verdict so execution only proceeds when safe. - Use Case: After returning to a task from last week, run this Skill to verify PLAN.md still matches the repo, find the resume point in TASKS.md, and confirm no unknown dirty changes exist before continuing implementation. ## Quick Start Use the sync skill to check my session artifacts, git state, and plan drift, then tell me whether it is safe to start execution.

Frequently Asked Questions about sync

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

FAQPage Schema
How do I verify a plan is still valid before executing code changes?▼

Run a read-only sync that compares PLAN.md and TASKS.md against the current codebase, git state, and dependencies. It reports drift items with type and impact, then issues a PASS, CONCERNS, or FAIL readiness verdict before any execution.

What should an AI agent check before modifying a repository?▼

The agent should confirm session artifacts exist, check for dirty changes and conflict markers, verify the current branch matches the workflow rules, and confirm files referenced in tasks still exist. All of this happens read-only, without mutating task progress.

Does the sync skill modify files or task progress?▼

No. Sync is read-only by default and never mutates TASKS.md progress, resolves conflicts, or touches dirty changes. Its only write is the SYNC.md report documenting facts, risks, and the readiness verdict.

When should I not run a pre-execution sync check?▼

Skip it for pure brainstorming, general knowledge questions, or small fresh-context tasks where the user provides full file context. It is also unnecessary when the user explicitly asks to skip repo checks.

What happens when sync detects merge conflicts or unknown dirty changes?▼

The readiness verdict becomes FAIL and execution is blocked. The report recommends resolving conflicts or asking the user to confirm ownership of dirty changes before proceeding.