trickle-labs

Create a GitHub Pull Request for pg_ripple. Use when: opening a PR, submitting code for review, creating a draft PR, publishing a branch, proposing changes. Handles branch creation policy, PR description writing, Unicode-safe body file, and CODEOWNERS review requirements.

Fix CI workflow failures for pg_ripple. Use when: a GitHub Actions run fails, a test panics, cargo pgrx errors appear, PostgreSQL build deps are missing, argument-passing errors occur, or deadlocks appear in the test suite. Covers pgrx 0.17 + PostgreSQL 18 specific patterns and all known failure modes encountered in this project.

Implement a specific pg_ripple roadmap version. Use when: implementing a milestone like v0.2.0, v0.3.0; delivering roadmap features; building SPARQL engine, SHACL, Datalog, HTAP, bulk loading, federation. Covers Rust/pgrx 0.17, PostgreSQL 18, VP storage, dictionary encoding, SPARQL translation.

Enrich a pg_ripple release roadmap with prioritised items across six quality pillars: correctness, stability, performance, scalability, ease-of-use, and test coverage. Use when planning a new release, fleshing out a milestone, or reviewing what gaps exist before tagging a version.

Release a pg_ripple version. Use when: tagging a release, preparing release notes, running the release checklist, creating a GitHub release. Covers pre-release verification, changelog finalization, GitHub release creation.

Reviews and improves the pg_trickle documentation in docs/. Checks accuracy against source code, fixes broken links, removes duplication, identifies gaps, and enforces consistency. Use when auditing docs quality, preparing a release, or after significant code changes. Produces a prioritised proposal and optionally writes it to a file.

Implement all items for a specific version in the pg_trickle roadmap. Use when: working through a milestone, implementing a release, or completing planned features. Drives a full implementation loop — reads plan docs, implements each item, keeps status up to date, asks the user when blocked, and reports what remains at the end.

Create or update a pull request for pg_trickle. Use when: opening a new PR, fixing a garbled PR description, updating an existing PR body, or preparing a PR after finishing a feature or fix. Handles the safe body-file workflow to avoid Unicode corruption.

Enrich a pg_trickle release roadmap with prioritised items across six quality pillars: correctness, stability, performance, scalability, ease-of-use, and test coverage. Use when planning a new release, fleshing out a milestone, or reviewing what gaps exist before tagging a version.

Release workflow for pg-tide. Use when: cutting a release, bumping the version, preparing a new version, tagging a release, publishing pg-tide, incrementing the version number.

Run the full rockstream "implement a roadmap version" pipeline end-to-end — Orient, Plan, Implement, Prove, Sign Off — by delegating each phase to a scoped subagent. Use when the user asks to "implement version X", "run the implement-version workflow", "do orient/plan/implement/prove/signoff for vX.Y", or wants all seven implement-version-*.prompt.md phases run in order automatically instead of manually running each prompt and typing /compact between them.

Release workflow for rs-polygraph. Use when: cutting a release, bumping the version, preparing a release commit and tag.