메뉴
Use when the user asks how code works, requests a code walkthrough, wants a codebase explanation, or asks to explain a function, module, flow, architecture, or implementation.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when reviewing a vd-studio pull request as the automated AI PR reviewer (OpenHands pr-review plugin) — judging test coverage for a diff, structuring the review report, or deciding merge readiness.
Use when test quality decisions are needed for new, changed, brittle, missing, or review-requested unit or component tests, including tests-first work, assertion choice, mock boundaries, lifecycle scenarios, or independent test-session handoff.
Use when filing, logging, raising, reporting, or submitting a product issue, feature request, bug, or feedback for the Studio or Utilities product areas in Linear.
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Compact the current conversation into a handoff document for another agent to pick up.
Use when asked to implement, fix, build, or work on an existing Linear issue in this repository, and coding should stop before PR creation
| name | explaining-code |
| description | Use when the user asks how code works, requests a code walkthrough, wants a codebase explanation, or asks to explain a function, module, flow, architecture, or implementation. |
When explaining code, always include:
Keep explanations conversational. For complex concepts, use multiple analogies.
