원클릭으로 Manus에서 모든 스킬 실행

codex-upstream-sync

스타0

포크0

업데이트2026년 6월 1일 06:56

Maintain Agent UI against upstream OpenAI Codex App Server schema drift. Use for protocol drift checks, schema refreshes, CODEX_PROTOCOL_COMMIT updates, method classification, and upstream sync PR creation.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

nyosegawa

nyosegawa/agent-ui

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Codex Upstream Sync

Use this skill when maintaining Agent UI against upstream OpenAI Codex App Server changes, especially when the user asks to check protocol drift, refresh generated schemas, update CODEX_PROTOCOL_COMMIT, classify new App Server methods, or create a PR for Codex App Server updates.

Intent

Keep Agent UI aligned with Codex App Server without turning upstream updates into unattended merges. This skill is for interactive or scheduled Codex Automation runs that detect drift, open a reviewable PR, and leave semantic UI work to a Codex agent or human reviewer.

Hard Rules

Do not edit files inside third_party/codex; update only the submodule pointer.
Do not push directly to main.
Do not publish npm packages.
Do not merge the PR created by this skill.
Do not replace the weekly Codex App Automation cadence with a scheduled GitHub Actions workflow unless the user explicitly asks for that change.
Treat generated schema changes as the beginning of review, not the completed update.
Classify every new stable and experimental method before calling the PR done.

First Checks

Read references/protocol-review.md.
Read references/codex-automation-prompt.md if the task is a scheduled or manual Codex Automation run.
Confirm third_party/codex is initialized and matches the checked-in generated schema commit before starting.
Confirm this repository has a clean working tree.
Run the drift report:
```
bun run codex:upstream:drift
```
The drift report compares generated schema against third_party/codex origin/main through a temporary worktree without moving the checked-in submodule pointer.

Standard Update Flow

Inspect the upstream commit and method drift:

bun run codex:upstream:info
bun run codex:upstream:drift

If drift exists, create a branch and PR:

bun run codex:upstream:prepare -- --push --pr --draft

Review generated schema changes in:
- packages/codex/src/generated/
- packages/codex/src/protocol.ts
- packages/codex/package.json
Fix all semantic fallout:
- Protocol method classification.
- Request builders and method result helpers.
- Normalizers and reducer expectations.
- Server-request handling and approval surfaces.
- React hooks, examples, and docs when a user-facing behavior changed.

Run focused validation before pushing follow-up commits:

bun run test:protocol
bun run typecheck
bun run lint
bun run test:api-snapshots
bun run test:package-resolution

For visible behavior changes, also run the relevant fixture or real local Playwright suite.

Completion Criteria

The PR is ready for review only when:

packages/codex/test/protocol.test.ts passes the classification gate.
docs/reference/codex-protocol.md matches the updated method surface.
Generated metadata is consistent across protocol.ts, package metadata, and generated README.
The third_party/codex submodule pointer matches CODEX_PROTOCOL_COMMIT.
Every new method has an explicit owner decision: productized, host-only, experimental available, experimental unsupported, or test-only.
No automation artifacts or temporary reports are committed unless a reviewer explicitly asks for them.

Repository Scripts

scripts/codex-upstream/collect-upstream-info.mjs: prints current and upstream commit metadata.
scripts/codex-upstream/summarize-protocol-drift.mjs: exports upstream protocol schema to a temporary directory and compares generated method lists without changing the repository.
scripts/codex-upstream/prepare-update-branch.mjs: creates an update branch, imports schema, records validation status, optionally pushes, and optionally opens a draft PR.

The script implementations are intentionally outside this skill directory. The skill owns judgment, sequence, and review criteria; repository maintenance commands live under scripts/.

이 저장소의 다른 Skills

같은 저장소

agent-ui

nyosegawa/agent-ui

Integrate, customize, debug, or upgrade Agent UI in external Codex App Server applications. Use when adding Agent UI, building a Codex UI, wiring a same-origin WebSocket bridge, composing React primitives, handling thread lifecycle, canonical resume, thread history, local media helper uploads, local desktop bridge policy, mobile drawer, overlay layers, host-gated workflow recipes, theming with --aui-* tokens, dynamic tools, Agent UI errors, or when the user says Agent UI導入, Codex UI, ローカルCodexアプリ, bridge, attachments, approvals, resume, local media, or upgrade Agent UI.

2026-06-170

agent-ui-feature-planning

nyosegawa/agent-ui

Plan Agent UI repository features before implementation. Use when the user asks to make a feature plan, plan before coding, research/plan/todo/goal prompt, solve a problem group, architecture plan, 実装前に計画, feature planning, PLAN/TODO作成, or goal-prompt generation for this repo. Do not use for small direct edits, review-only requests, npm release operations, upstream sync, browser QA, or external host-app integration unless the user explicitly asks for a planning package.

2026-06-080

npm-release

nyosegawa/agent-ui

Operate Agent UI npm releases for @nyosegawa public packages with one reviewed release PR, local Changesets versioning, automatic main-push publishing, provenance, GitHub Releases, post-publish install smoke, rollback, and deprecation. Use when preparing or running an npm release, adding changesets, creating or reviewing release PRs, publishing packages, or debugging release workflow failures.

2026-06-060

agent-ui-review

nyosegawa/agent-ui

Review Agent UI repository changes, pull requests, branches, diffs, or Codex-generated updates for correctness, product boundary, protocol behavior, server bridge safety, package exports, tests, docs, UI regressions, and release risk. Use when the user asks for review, PR review, branch review, diff audit, safety check, or whether Agent UI changes are ready to merge.

2026-06-050

browser-qa

nyosegawa/agent-ui

Verify Agent UI browser-visible behavior with Playwright and agent-browser. Use for UI, CSS, layout, transcript, composer, approvals, usage, diagnostics, thread history, examples, mobile, overflow, focus, keyboard, click, hit-test, screenshot, accessibility snapshot, or real-local browser QA work.

2026-05-310

example-authoring

nyosegawa/agent-ui

Add, update, or review Agent UI examples, recipes, fixture routes, docs-site examples, Next.js/Vite integrations, local Codex web demos, theming recipes, uploads examples, dynamic tools examples, or example documentation. Use when working in examples/, docs/examples/, docs/recipes/, fixture routes, or browser-visible sample apps.

2026-05-310

name	codex-upstream-sync
description	Maintain Agent UI against upstream OpenAI Codex App Server schema drift. Use for protocol drift checks, schema refreshes, CODEX_PROTOCOL_COMMIT updates, method classification, and upstream sync PR creation.

Codex Upstream Sync

Intent

Hard Rules

Do not edit files inside third_party/codex; update only the submodule pointer.
Do not push directly to main.
Do not publish npm packages.
Do not merge the PR created by this skill.
Do not replace the weekly Codex App Automation cadence with a scheduled GitHub Actions workflow unless the user explicitly asks for that change.
Treat generated schema changes as the beginning of review, not the completed update.
Classify every new stable and experimental method before calling the PR done.

First Checks

Read references/protocol-review.md.
Read references/codex-automation-prompt.md if the task is a scheduled or manual Codex Automation run.
Confirm third_party/codex is initialized and matches the checked-in generated schema commit before starting.
Confirm this repository has a clean working tree.
Run the drift report:
```
bun run codex:upstream:drift
```
The drift report compares generated schema against third_party/codex origin/main through a temporary worktree without moving the checked-in submodule pointer.

Standard Update Flow

Inspect the upstream commit and method drift:

bun run codex:upstream:info
bun run codex:upstream:drift

If drift exists, create a branch and PR:

bun run codex:upstream:prepare -- --push --pr --draft

Review generated schema changes in:
- packages/codex/src/generated/
- packages/codex/src/protocol.ts
- packages/codex/package.json
Fix all semantic fallout:
- Protocol method classification.
- Request builders and method result helpers.
- Normalizers and reducer expectations.
- Server-request handling and approval surfaces.
- React hooks, examples, and docs when a user-facing behavior changed.

Run focused validation before pushing follow-up commits:

bun run test:protocol
bun run typecheck
bun run lint
bun run test:api-snapshots
bun run test:package-resolution

For visible behavior changes, also run the relevant fixture or real local Playwright suite.

Completion Criteria

The PR is ready for review only when:

packages/codex/test/protocol.test.ts passes the classification gate.
docs/reference/codex-protocol.md matches the updated method surface.
Generated metadata is consistent across protocol.ts, package metadata, and generated README.
The third_party/codex submodule pointer matches CODEX_PROTOCOL_COMMIT.
Every new method has an explicit owner decision: productized, host-only, experimental available, experimental unsupported, or test-only.
No automation artifacts or temporary reports are committed unless a reviewer explicitly asks for them.

Repository Scripts

scripts/codex-upstream/collect-upstream-info.mjs: prints current and upstream commit metadata.
scripts/codex-upstream/summarize-protocol-drift.mjs: exports upstream protocol schema to a temporary directory and compares generated method lists without changing the repository.
scripts/codex-upstream/prepare-update-branch.mjs: creates an update branch, imports schema, records validation status, optionally pushes, and optionally opens a draft PR.

The script implementations are intentionally outside this skill directory. The skill owns judgment, sequence, and review criteria; repository maintenance commands live under scripts/.