Read design review notes attached to a pull request’s screenshots, locate the affected components, and fix the product code using the team’s design rules. Repeat the review and inspect screenshots to verify the result.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Design notes on a PR, "Design review (advisory)" in the evidence check, "worth fixing", layout.split-row, OW-LIST, a reviewer says the UI looks off. Use to read what the design review found on a PR's screenshots, fix it in code, and prove the note is gone.
설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Every PR that records evidence screenshots gets an advisory design review. Its notes ride in the Evidence preview check, next to the evidence they are about: one summary line, and the notes as the check's text. They never change the evidence verdict, but a note marked Worth fixing is a defect a careful designer would send back. Fix it, or say in the PR why the screen is right.
sha=$(gh pr view <pr> --json headRefOid --jq .headRefOid)
check() { gh api "repos/{owner}/{repo}/commits/$sha/check-runs?check_name=Evidence%20preview" --jq ".check_runs[0].output.$1"; }
check summary # ends with "Design review (advisory): 3 notes, 1 worth fixing." or "no notes."
check text # the notes, then the same notes as JSON
Each note gives:
| Field | Use it to |
|---|---|
| rule | layout.* was measured from the DOM (exact). S2, V2… are DESIGN.md; OW-* are the OpenWork Design rules in evals/design-review/rubric.md (judged from pixels; may vary run to run) |
| Screenshot | the spec step that took it, and the spec file |
| Where in the code | grep for the hook ([data-library-row="…"] → data-library-row) or the class list to find the component |
| Reproduce | the command that re-records the screenshots and reviews them locally |
The JSON block at the end of the check text has the same notes for scripts. The screenshots themselves are in the review report the check links to.
--json output, not prose:
pnpm evals:e2e <slug> --local && pnpm --dir evals design:review -- --test-run latest --json
(judged notes need OPENAI_API_KEY or ANTHROPIC_API_KEY; measured ones do not).evals/design-review/rubric.md before changing anything: the fix follows
the team's pattern, not the note's wording.Design review (advisory): no notes. or lists only what you decided to keep.A judged note can be wrong, and a team decision can outrank a generic rule.
Leave the code, and put one line in the PR body under Evidence:
Design review: kept OW-LIST-HEADER on the Library; the columns are compared (see DESIGN.md S2).
Do not edit the rubric to silence a note in the same PR that triggers it.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Manage OpenWork feature releases with feature flags, switches that control access to new behavior. Register features before coding, release them by organization and deployment, prepare a global shutdown option, and remove temporary flags after rollout.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Connect OpenCode browser tools to a locally running OpenWork Electron app to inspect its UI, enter a task, and check the response. This skill supports exploration and debugging through CDP, Chrome's remote control protocol.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Check added lines in a change for information identifying customers, prospects, partners, or outside individuals. Report locations and generic remediation without reproducing identities, and escalate cases where the information is already public.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Connects supported AI clients, including Claude Code and Codex, to OpenWork through MCP, a protocol for accessing external tools. It guides account sign-in and verifies that tools for finding and running organization capabilities are available.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review an outside contributor’s pull request before running its code. Identify concealed behavior, obfuscated code, risky dependencies, and build hooks, with file locations and specific checks for maintainers to follow up.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create an OpenCode plugin for OpenWork with custom tools and hooks, which run code at specific events. The skill builds the plugin file and adds its entry to the project configuration.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.