sopify

Installation

Two-step install (recommended for first-time review):

curl -fsSL -o sopify-install.sh https://github.com/evidentloop/sopify/releases/latest/download/install.sh
sed -n '1,40p' sopify-install.sh
bash sopify-install.sh --target codex:en-US

Windows PowerShell:

iwr https://github.com/evidentloop/sopify/releases/latest/download/install.ps1 -OutFile sopify-install.ps1
Get-Content sopify-install.ps1 -TotalCount 40
.\sopify-install.ps1 --target codex:en-US

The repo-local install path remains available for developers and maintainers:

bash scripts/install-sopify.sh --target codex:en-US
python3 scripts/install_sopify.py --target claude:en-US --workspace /path/to/project

Install targets:

• codex:zh-CN
• codex:en-US
• claude:zh-CN
• claude:en-US
• copilot

The protocol works with any host. Verified runtime integrations today:

Notes:

• Use sopify status / sopify doctor for detailed capability claims and live diagnostics
• Availability expresses the current delivery tier, while Validation coverage describes what has already been validated

Setup Paths

• install.sh --target codex:... / claude:... installs the selected host prompt layer and the Sopify payload. Most users do not need --workspace; that is an advanced prewarm path for maintainers or CI.
• install.sh --target copilot bootstraps the current workspace, creates .sopify-skills/sopify.json, updates .gitignore, and distributes Copilot instruction files. Pass --workspace <path> to target another repo, --language <lang> to control output language, or --no-copilot to skip Copilot files.
• bootstrap.sh remains available as a compatibility alias and forwards to install.sh --target copilot.

For the full setup guide, see Getting Started. For a step-by-step demo, see External Repo Quickstart.

After Install

• Use ~go when you want Sopify to manage the full task workflow for you.
• Interrupt anytime — come back (even in a different tool) and resume from where you left off.
• Complex changes can get an independent review before execution starts.
• Run status to see current progress, doctor to troubleshoot.

Verify Your Install

python3 scripts/sopify_status.py --format text
python3 scripts/sopify_doctor.py --format text

• will bootstrap on first project trigger: the host install is ready and the project-local runtime has not been prepared yet
• workspace outcome: stub_selected [continue]: the workspace runtime entry is healthy
• Payload or bundle corruption errors (for example global_bundle_missing, global_bundle_incompatible, or global_index_corrupted): repair the install and retry

Quick Start

curl -fsSL https://github.com/evidentloop/sopify/releases/latest/download/install.sh | bash -s -- --target codex:en-US

After install, use ~go to start a managed workflow. See Installation for other targets, platforms, and verification.

Already in a Sopify-managed repo? Open any AI host and continue the unfinished task — it picks up from where you left off. Full walkthrough →

---

Configuration

Start from the example config:

cp examples/sopify.config.yaml ./sopify.config.yaml

Most commonly used settings:

brand: auto
language: en-US

workflow:
  mode: adaptive
  require_score: 7

plan:
  directory: .sopify-skills

Notes:

• workflow.mode supports strict / adaptive / minimal
• plan.directory only affects newly created knowledge and plan directories

Command Reference

Most users only need ~go and ~go plan; maintainer validation commands live in CONTRIBUTING.md.

Q: How do I reset learned preferences?

Delete or clear .sopify-skills/user/preferences.md; keep feedback.jsonl only if you still want the audit trail.

Q: Where are plan packages stored?

By default they live under .sopify-skills/ in the project root. To change that:

plan:
  directory: .my-custom-dir

This only affects newly created directories; existing history is not migrated automatically.

FAQ