본문으로 건너뛰기
cccskills
무료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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

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

설치 방법 보기

이럴 때 유용합니다

  • 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

포함된 파일(3)

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

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

branch-pr

무료

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.9천2026년 10월 22일 업데이트

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.9천2026년 10월 22일 업데이트

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.9천2026년 10월 22일 업데이트

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.9천2026년 10월 22일 업데이트

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.9천2026년 10월 22일 업데이트

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.9천2026년 10월 22일 업데이트

Gentleman-Programming의 스킬 모두 보기

이 스킬의 문제 신고