insites-sync

Sync application files to the Insites staging environment and validate with insites-cli audit.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/insites-io/insites-logic-engine --skill insites-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: insites-sync
Source: https://github.com/insites-io/insites-logic-engine/tree/main/skills_examples/insites-sync
Command: npx skills add https://github.com/insites-io/insites-logic-engine --skill insites-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of pushing application files to an Insites staging environment and checking whether the change is safe and valid afterward.

Core Features & Use Cases

  • Staging Sync: Sync a single file or an entire set of app changes to the staging instance.
  • Automatic Validation: Run post-sync audit checks to catch syntax, linting, and file-related issues early.
  • Scoped File Handling: Work only with approved app paths such as views, assets, translations, emails, GraphQL, schema, and API call definitions.
  • Use Case: A developer updates a Liquid template, syncs it to staging, and immediately confirms there are no Liquid syntax or audit errors.

Quick Start

Ask the assistant to sync your changed app file to Insites staging and run validation afterward.

Frequently Asked Questions about insites-sync

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

FAQPage Schema
How do I sync app files to Insites staging and validate Liquid syntax?

To sync app files to Insites staging, you push repository changes under approved app paths and then validate Liquid syntax by running a post-sync audit. This process catches missing-file or syntax errors immediately after the staging deployment.

What is the process for staging app file changes in Insites?

Staging app file changes in Insites involves synchronizing repository updates from approved directories like app/views and app/lib to the staging environment, followed by an automatic validation audit to ensure file integrity and correct Liquid syntax.

Can I sync module files and external directories to Insites staging?

No, you cannot sync module files to Insites staging. The sync process enforces an app-only scope, strictly excluding modules and limiting file handling to approved application paths such as app/graphql, app/schema, app/translations, and app/assets.

How do I run an audit after syncing files to Insites staging?

You run an audit after syncing files by using the insites-cli audit command. This post-sync validation step verifies the synchronization outcome and surfaces any linting, missing-file, or Liquid syntax errors early before further deployment.

Why does my Insites staging sync fail with missing-file errors?

Your Insites staging sync fails with missing-file errors when the synchronization process detects issues within the approved app paths. Running the post-sync insites-cli audit surfaces these specific file-related and Liquid syntax errors for you to resolve.