How do I install the Ops Diff skill?

Run npx skillmds@latest add rbutinar/ops-diff in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Ops Diff skill do?

Compare Local vs Remote State It is listed under Coding & Dev Tools on SkillMD.

Is Ops Diff safe to use?

SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ops Diff?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ops Diff free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ops Diff?

rbutinar (@rbutinar) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ops Diff by rbutinar — Agent Skill

Name: Ops Diff
Rating: 4.2 (5 reviews)
Author: rbutinar

File contents

/ops-diff — Compare Local vs Remote State

You are executing a diff operation: comparing assembled local files (src/ + overlay + patches) against the last pulled remote state (state/{env}/{scope}/).

This skill is a thin wrapper around the ade-ops CLI: python -m core.cli diff.

Usage

/ops-diff                                # interactive — ask for env and scope
/ops-diff dev notebooks                  # diff notebooks for dev
/ops-diff cert notebooks                 # diff notebooks for cert
/ops-diff prod power_bi                  # diff power_bi for prod
/ops-diff cert notebooks --file foo.py   # filter to a specific file

Arguments

$ARGUMENTS — optional: {env} {scope} with optional --file {filter}

Parse arguments from: $ARGUMENTS.

Behavior

Step 1: Resolve Project

Find the active project (nearest ancestor of cwd with config/project.yaml). Pass it via --project {project_root} to the CLI.

Step 2: Resolve Environment & Scope

If not provided, ask the user. Use python -m core.cli status to list available env × scope combinations.

Step 3: Check State Exists

If state/{env}/{scope}/ is empty or missing, the CLI will warn. Surface:

No state for {env}/{scope}. Run /ops-pull {env} {scope} first to download the current remote state.

Do not proceed without state — diff needs something to compare against.

Step 4: Execute Diff

python -m core.cli diff --project {project_root} --env {env} --scope {scope}

Optional flags:

--filter {pattern} to narrow to specific files
--no-content to suppress unified diff output (summary only)

For all, iterate over the project's scopes.

Step 5: Interpret & Report

The CLI summary uses these markers:

Marker	Meaning
`+` (local-only)	Files in assembled `src/` not in state — would be added by push
`-` (remote-only)	Files in state not in assembled `src/` — exist remotely but not locally
`~` (modified)	Files differ between local and state — would be updated by push
`=` (identical)	Files match — no action needed

After the diff, suggest next steps:

Changes present → "Run /ops-push {env} {scope} to deploy."
In sync → "No changes to push."
Remote-only files → "These exist remotely but not in src/. Push will not delete them — manual cleanup if unwanted."

Safety

Diff is read-only. Reads src/, overlays, patches, and state/. Writes nothing.
Always safe to run. No confirmation needed.

Error Handling

No state → direct user to /ops-pull first
Empty src/ → warn that everything will show as remote-only
Overlay not found → show the error, suggest checking overlays/

---name: ops-diffdescription: Compare Local vs Remote State---# /ops-diff — Compare Local vs Remote StateYou are executing a **diff** operation: comparing assembled local files (`src/` + overlay + patches) against the last pulled remote state (`state/{env}/{scope}/`).This skill is a thin wrapper around the ade-ops CLI: `python -m core.cli diff`.## Usage```/ops-diff # interactive — ask for env and scope/ops-diff dev notebooks # diff notebooks for dev/ops-diff cert notebooks # diff notebooks for cert/ops-diff prod power_bi # diff power_bi for prod/ops-diff cert notebooks --file foo.py # filter to a specific file```## Arguments- `$ARGUMENTS` — optional: `{env} {scope}` with optional `--file {filter}`Parse arguments from: `$ARGUMENTS`.## Behavior### Step 1: Resolve ProjectFind the active project (nearest ancestor of cwd with `config/project.yaml`).Pass it via `--project {project_root}` to the CLI.### Step 2: Resolve Environment & ScopeIf not provided, ask the user. Use `python -m core.cli status` to list available env × scope combinations.### Step 3: Check State ExistsIf `state/{env}/{scope}/` is empty or missing, the CLI will warn. Surface:> No state for {env}/{scope}. Run `/ops-pull {env} {scope}` first to download the current remote state.Do not proceed without state — diff needs something to compare against.### Step 4: Execute Diff```bashpython -m core.cli diff --project {project_root} --env {env} --scope {scope}```Optional flags:- `--filter {pattern}` to narrow to specific files- `--no-content` to suppress unified diff output (summary only)For `all`, iterate over the project's scopes.### Step 5: Interpret & ReportThe CLI summary uses these markers:| Marker | Meaning ||---|---|| `+` (local-only) | Files in assembled `src/` not in state — would be **added** by push || `-` (remote-only) | Files in state not in assembled `src/` — exist remotely but not locally || `~` (modified) | Files differ between local and state — would be **updated** by push || `=` (identical) | Files match — no action needed |After the diff, suggest next steps:- Changes present → "Run `/ops-push {env} {scope}` to deploy."- In sync → "No changes to push."- Remote-only files → "These exist remotely but not in `src/`. Push **will not delete them** — manual cleanup if unwanted."## Safety- Diff is **read-only**. Reads `src/`, overlays, patches, and `state/`. Writes nothing.- Always safe to run. No confirmation needed.## Error Handling- **No state** → direct user to `/ops-pull` first- **Empty src/** → warn that everything will show as remote-only- **Overlay not found** → show the error, suggest checking `overlays/`

Frequently asked questions

Ops Diff