og

Synchronize a plurigrid fork via cherry-picking with DuckDB-backed state tracking.

60|13|Updated Dec 22, 2025
One-click install
npx skills add https://github.com/plurigrid/asi --skill og
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: og
Source: https://github.com/plurigrid/asi/tree/main/skills/og
Command: npx skills add https://github.com/plurigrid/asi --skill og

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The og skill orchestrates a plurigrid fork by cherry-picking from the original remote and tracking interactions with a DuckDB-backed buffer, enabling time-travel style analysis of changes.

Core Features & Use Cases

  • Time travel for state exploration: Jump to previous commit rounds.
  • DuckDB-backed buffers: Track crdt.el state and color invocations.
  • Rewrite tracking: Monitor GayMCP rewrites and palette mutations.

Quick Start

Fetch from the og remote and perform a cherry-pick with a DuckDB buffer, then travel to a prior drand round.

Frequently Asked Questions about og

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

FAQPage Schema
How do I track state changes across commits using time-travel replay in DuckDB?

Time-travel replay in DuckDB lets you jump to previous commit rounds and inspect state snapshots. The og Skill records CRDT.el sexp state and color invocations in DuckDB buffers, enabling deterministic replay of interactions and provenance tracking across collaborative coding workflows.

Can I cherry-pick from a remote while keeping my fork synchronized with DuckDB tracking?

Yes. The og Skill orchestrates cherry-picks from the original remote while maintaining fork synchronization through DuckDB-backed buffers that track CRDT history and monitor GayMCP rewrites, enabling observational state analysis during collaborative development.

What's the best way to monitor CRDT state mutations and palette changes during collaborative editing?

Use DuckDB buffers to record CRDT.el state and Gay.jl color invocations with drand beacon data for provenance. The og Skill implements an observational bridge pattern that tracks all mutations and rewrites, supporting deterministic replay of the full interaction history.

Does DuckDB support storing and replaying CRDT history with color provenance metadata?

Yes. DuckDB buffers in the og Skill store CRDT.el sexp state, Gay.jl color invocations, and drand beacon data as provenance records. This enables deterministic replay and historical analysis of state changes in time-travel workflows.

How do I perform a cherry-pick with observational history tracking for collaborative forks?

Fetch from the og remote, execute a cherry-pick operation, and use the DuckDB buffer to record CRDT state and color changes. Then traverse to prior drand rounds for observational time-travel analysis of the collaborative interaction history.