percolate

Run dry-run diffs, safety scans, and confirmation gates before rsync publishing.

5|2|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/dbc-oduffy/coordinator-claude --skill percolate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: percolate
Source: https://github.com/dbc-oduffy/coordinator-claude/tree/main/plugins/coordinator/skills/percolate
Command: npx skills add https://github.com/dbc-oduffy/coordinator-claude --skill percolate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents risky or accidental publication of coordinator plugin files by forcing a deterministic dry-run with visibility, content-leakage scanning, drift detection, and an explicit PM confirmation gate before any real rsync and CI smoke run.

Core Features & Use Cases

  • Dry-run diff + impact framing: Runs the publish pipeline in dry-run mode and summarizes what will be added/modified/deleted, including an impact-radius gut-check (top directories, file types, and sensitive paths).
  • Policy-aware coverage drift checks: Surfaces potential coverage drift since the last policy review using the source tree vs the .percolate-ignore file.
  • Content-leakage scanning and publish safety gates: Greps only the about-to-be-published files in severity tiers, blocks on HIGH findings, and forces confirmation on MEDIUM findings.
  • Inverse-drift detection against destination: Detects whether the publish repo has commits touching files that will be overwritten, warning the PM before proceeding.
  • Deterministic publish orchestration with hooks + optional CI smoke: Performs the real run after confirmation, executes registered per-target pre-ci hooks, and runs run-all-checks.py when available.

Quick Start

Use /percolate coordinator-claude to dry-run, scan for risky content and drift, ask for PM confirmation when needed, then publish and optionally run CI smoke.

Frequently Asked Questions about percolate

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

FAQPage Schema
How do I prevent accidental file deletions when publishing plugin updates to a release repository?

To prevent accidental file deletions during plugin updates, you can run a rsync dry-run diff that summarizes added, modified, and deleted files before executing the real publication. This impact framing highlights top directories and sensitive path changes for review.

What is content leakage scanning and how does it gate plugin releases?

Content leakage scanning greps about-to-be-published files in severity tiers to block risky publications. HIGH severity findings automatically block the release, while MEDIUM findings force an explicit PM confirmation gate before any real rsync occurs.

How do I detect inverse drift against a destination publish repository before syncing?

Inverse drift detection checks the publish repository for commits touching files that will be overwritten by the upcoming sync. This mechanism warns the PM before proceeding, preventing accidental overwrites of untracked destination changes.

Can I run CI smoke checks after safely publishing plugin files?

Yes, you can run CI smoke checks by executing run-all-checks.py after the real rsync completes. The workflow performs deterministic publish orchestration by running registered pre-ci hooks first, then triggering the CI smoke run.

What prerequisites are needed to gate plugin publications with dry-run diff and safety scans?

To gate plugin publications, you need target registration in publish-targets.sh and percolate setup readiness via .percolate-ignore. You also need preconfigured percolate hook directories to enable tiered grep scanning and CI smoke execution.