Skip to content
cccskills
FreePublished on GitHub

rdd-advisory-transport

Guide changes to RDD reviewer integrations through a shared Go contract, a common set of processing rules. Define adapter boundaries, validate result handling, and check that runtime migrations preserve existing review outcomes.

OriginalShow the original description

Trigger: reviewer transport, advisory transport, review adapter, lens prompt/schema, OpenCode reviewer plugin, Codex reviewer, ReviewProviderContract. Enforce the shared Go advisory reviewer transport contract.

See how to install

Good for

  • Moving reviewer invocation into a shared Go contract
  • Checking that adapters only invoke reviewers and return raw output
  • Verifying review outcomes during a runtime migration
  • Validating Codex support before advertising availability

Files included (3)

  • SKILL.md4.3 KB
  • references/issue-impact-matrix.md6.9 KB
  • references/shared-advisory-transport-proposal.md20.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Activation Contract

Load when changing how any runtime (Claude Code, OpenCode, Codex, future) invokes an RDD reviewer, refuter, or fix validator, or when touching reviewer prompts, lens evidence, result schemas, adapters, or transport capability policy.

Hard Rules

  • One Go provider contract owns binding, frozen evidence, lens mandate, prompt, result schema, byte budget, JSON extraction, and admission. Start from existing native sources (reviewLensContextBlock, ReviewerResultSchema, RunReviewCaptureResult, CaptureAdmittedReviewerResult); never build a parallel system.
  • Adapters only invoke the reviewer and return raw bytes plus a transport error. An adapter must never parse bindings, rebuild prompts, copy schemas, apply local budgets, parse JSON, capture or preserve results, hold retry state, or decide blocking.
  • Runtime output is advisory: it cannot create authority, mutate review state, mint a receipt, or open a gate. Only Go admission does.
  • Byte budget refuses before invocation; never truncate. Malformed, truncated, or incomplete input never becomes PASS, complete, or a clean receipt.
  • No OpenCode restart, child isolation, special session, or OPENCODE_DISABLE_* variables. An ordinary running session is sufficient.
  • The RDD semantic pipeline is untouchable: lens selection, severity meanings, candidate causality, refuter adjudication, bounded correction, verification, terminal receipt, and read-only review-context evaluation. These are review-lifecycle concerns only; ordinary repository policy owns delivery.
  • Refuter and fix validator consume the same provider contract. A validator that could not inspect produced no verdict — surface a blocked decision; never record it as failed (that irreversibly consumes the single correction).
  • Capability advertisement requires shared-contract conformance plus organic runtime proof. Codex stays unadvertised until both positive and fail-closed proofs pass.
  • Transport failures never consume a correction budget, duplicate a capture, or strand a lineage.
  • Historical receipts stay readable; never rewrite provider_command or runtime_interception descriptors.

Decision Gates

ConditionAction
Logic fits "prompt/evidence/schema/validation"It belongs in the Go contract, never an adapter.
Adapter cannot expose raw final outputRuntime stays typed unavailable; no artifact-parser workaround.
Cutover slice exceeds 1000 lines/PRChained PRs on the tracker; advertisement flip lands last.
Shared prompt changes any semantic outcomeSTOP; regression against baseline blocks the slice.
Slice touches negotiated START / repository_contextCoordinate with the deferred Wave 7 switch-removal finding first.

Execution Steps

  1. Freeze the boundary: contract-level tests around current native prompt/evidence/schema/admission.
  2. Extract the Go provider contract; differential-test against current admission.
  3. Add adapter-minimality static guards (no binding types, prompt text, schema copies, budgets, parsers, capture, retry in adapters) — from the first adapter slice, not last.
  4. Cut Claude + OpenCode over without an advertised intermediate path; delete the OpenCode plugin and isolation machinery in the same release slice.
  5. Prove Codex organically before advertising; retire historical transport code last.
  6. Gate every slice on the bench journey corpus diff: all journeys unchanged.

Output Contract

Report per slice: contract surface touched, adapter minimality guard status, bench corpus diff result, semantic regression result, capability advertisement state, and any unresolved maintainer decision (e.g. receipt provider_contract descriptor).

References

  • references/shared-advisory-transport-proposal.md — full proposal: architecture, deletion candidates, test plan, risks.
  • references/issue-impact-matrix.md — per-issue dispositions under the shared contract; a maintainer condition in an issue's own thread always outranks its row.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

branch-pr

FreeSummary

Prepare pull requests by checking approved issue links, change-type labels, and required automated checks. Draft the repository’s PR template using observed test results, while leaving commits, pushes, PR creation, and merging under human control.

  • Preparing a branch for review
  • Drafting a PR linked to an approved issue
  • Checking required CI before declaring a PR merge-ready
Gentleman-Programming/gentle-ai7.9KUpdated Oct 23, 2026

chained-pr

FreeSummary

Split changes exceeding 400 lines into linked pull requests with clear boundaries and dependencies. Choose a chain structure, keep tests and documentation with each work unit, and document review order, verification plans, and justified size exceptions.

  • Splitting a change that exceeds 400 lines
  • Planning PRs that can merge independently
  • Coordinating a feature through a draft tracker PR
Gentleman-Programming/gentle-ai7.9KUpdated Oct 23, 2026

Structure guides, READMEs, design documents, and pull request descriptions so readers can find answers quickly. Put outcomes first, introduce details gradually, and use examples, tables, and checklists to support understanding and review.

  • Reorganizing a long or dense README
  • Writing an onboarding guide for new contributors
  • Making a pull request's review steps clear
Gentleman-Programming/gentle-ai7.9KUpdated Oct 23, 2026

comment-writer

FreeSummary

Draft clear, considerate comments for code reviews, issue replies, and team updates. Put the actionable point first, explain technical reasons when needed, and give a concrete next step while matching the conversation’s language.

  • Requesting a code change with a clear reason
  • Replying to a contributor’s issue
  • Writing a brief asynchronous team update
Gentleman-Programming/gentle-ai7.9KUpdated Oct 23, 2026

gentle-ai-bench

FreeSummary

Create and verify gentle-ai journeys, which are scripted sequences of product actions. Check their declarations separately from actual execution, review outdated expectations after behavior changes, and record execution results for pull requests.

  • Adding a product operation journey
  • Updating expectations after behavior changes
  • Reproducing a bench failure from CI
Gentleman-Programming/gentle-ai7.9KUpdated Oct 23, 2026

Prepare Gentle AI changes for review by linking approved issues, following branch and commit naming rules, and drafting pull requests with observed test results. Check change size and required automated checks before claiming readiness.

  • Preparing a branch for a fix or feature
  • Drafting a pull request linked to an approved issue
  • Organizing test results and reviewer notes
Gentleman-Programming/gentle-ai7.9KUpdated Oct 23, 2026

See all skills by Gentleman-Programming

Report a problem with this skill