sync

Check session artifacts, codebase context, and workspace integrity before execution.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures that agents have the latest and most reliable context before execution, mitigating the risks of stale information and potential errors.

Core Features & Use Cases

  • Session Artifacts Sync: Synchronize DISCUSSION.md, PLAN.md, EXECUTION.md, and REVIEW.md to ensure all necessary session information is current.
  • Codebase Context Refresh: Refreshes the codebase context relevant to the planned scope, ensuring up-to-date understanding of the project state.
  • Git State and Workspace Check: Validates the workspace and git state to prevent issues with code changes or conflicts.
  • Dependency and Config Verification: Checks for drift between the plan and current codebase, ensuring dependencies and configurations are in sync.
  • Blocker Identification: Identifies any blockers or issues that would prevent a successful execution before they occur.
  • Use Case: Before implementing a feature, this Skill would ensure that all documentation, code, and dependencies are up-to-date and conflict-free.

Quick Start

Use the sync skill to prepare the environment for the upcoming feature implementation in the 'feature/new-branch' session.

Frequently Asked Questions about sync

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

FAQPage Schema
How do I check codebase context and session artifacts before execution?

To check codebase context and session artifacts before execution, perform a read-only sync to validate the latest state of DISCUSSION.md, PLAN.md, and EXECUTION.md. This synchronizes session information and refreshes codebase context to ensure up-to-date understanding.

Why does dependency verification fail due to workspace and git state mismatches?

Dependency verification fails due to workspace and git state mismatches when drift occurs between the plan and current codebase. Validating workspace integrity and read-only git access identifies potential blockers, configuration drift, and conflicts before execution begins.

What is the best way to identify blockers and pre-execution readiness issues?

The best way to identify blockers and pre-execution readiness issues is to run a comprehensive workspace integrity check. This verifies dependencies, configurations, and git state to detect drift between the plan and current codebase before they cause execution failures.

Do I need read-only git access to synchronize session artifacts?

Yes, you need read-only git access to synchronize session artifacts. Checking the latest state of session artifacts, codebase context, and workspace integrity requires a valid session path, workspace access, and read-only git access to validate dependencies successfully.

Can I validate configuration drift between PLAN.md and the current codebase?

Yes, you can validate configuration drift between PLAN.md and the current codebase. The synchronization process checks for drift between the plan and current codebase state, ensuring dependencies and configurations remain in sync before feature implementation.