메뉴
The house pre-PR flow — port gates green, CodeRabbit CLI review on the branch diff, evidence-based triage, then present everything and WAIT for human approval. Use when a branch is feature-complete, before any commit/push/PR.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Update the okf/ knowledge bundle after a change to the system — the touched concepts, their index entries, the affected diagrams, and the bundle log. Use at the end of any change that alters system shape (an agent, a Kind, a route, a check name, a package, an env var, a port convention), or standalone when the bundle has drifted from reality.
Convert acceptance criteria, Jira tickets, Gherkin scenarios, PRDs, or any product requirements into a filled-in spec under specs/ using this repo's templates. Use when translating PM artifacts or informal asks into an add, change, migrate, or remove spec ready for implementation.
Scaffold a new deterministic, agent-free tooling package on the modern pair, with tests and its knowledge concept. Use when the system needs a new platform capability (an API client, ingress, transport, notifier-style package) rather than a new workflow.
Scaffold a new workflow agent end-to-end on the modern pair — ingest Kind, dispatcher registration, agent package, tests, webhook route, and the knowledge updates. Use when adding an entirely new workflow (a new fixer, digest, or reviewer-style agent) to the system.
Interview the user one question at a time to resolve every unfilled marker in a spec file (`<!-- TODO -->`, raw template placeholder prose, `<YYYY-MM-DD>`-style header stubs, empty plan steps, unconfirmed reverse-spec presumptions). Use on hand-authored specs, stale specs, or when the user says "grill me" or "stress-test this plan". The conversion skills (/ac-to-spec, /reverse-spec) embed this logic inline, so freshly-converted specs don't need a separate pass. Recommends an answer for every question, explores the codebase and okf bundle instead of asking when it can, and writes resolutions back with a Decisions log.
Execute a library, API, or framework swap on a port — mechanical migration that preserves observable behavior, verified against the shipped API. Use when bumping a major SDK version (e.g. the ADK), swapping a library, or moving to a new provider API.
| name | review-branch |
| description | The house pre-PR flow — port gates green, CodeRabbit CLI review on the branch diff, evidence-based triage, then present everything and WAIT for human approval. Use when a branch is feature-complete, before any commit/push/PR. |
Run the full house review flow on the current branch. The output is a reviewed, triaged diff presented to the human — not a commit, push, or PR.
Parameters: base (optional, default main — pass the stacked-base branch for stacked PRs)
Usage examples:
/review-branch # review the branch diff against main
/review-branch feat/base-pr # stacked branch: review against its base
Gate definitions live in okf/tooling/ci-gates.md; parity rules used in triage live in okf/standards/language-parity.md. This skill is a thin driver.
Run /verify diff (escalate to /verify full for cross-port changes). Do not start the CodeRabbit review while any gate is red — review noise on broken code wastes everyone's time.
coderabbit review --agent --base main # or --base <stacked-base>
150-file cap: the CLI refuses diffs larger than 150 files. When the diff is bigger, scope by directory and run once per touched top-level dir:
coderabbit review --agent --base main --dir go/
coderabbit review --agent --base main --dir okf/
For every finding, exactly one of:
Never blind-accept a finding just to clear the list, and never decline with only "seems fine" — no evidence, no decline.
If step 3 changed code, re-run the affected gates. Optionally re-run CodeRabbit on the delta to confirm the fixes didn't introduce new findings.
Present to the human, then stop:
git diff --stat <base>...HEAD + what/why in prose)Do not commit, push, or open a PR. No auto-commit is house convention — changes stay in the working tree until the human explicitly approves. Only proceed to commit/push/PR when told to.