메뉴
Use when the user wants a PR scope assessment surfaced directly — "is this PR too big", "how should I split this", "chunk this into PRs", "scope check", or before opening a large PR. Runs the pr-scope-analyzer agent and relays its full output verbatim.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/egladman/dotfiles-darwin --skill pr-scope명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Use when writing a git commit message, or rewording existing unpushed ones, so they match this user's format. Triggers on "commit this", "write the commit message", "fix the commit messages", "reword the commits", "clean up my commit history". The format is short and dry, no conventional-commit prefixes, no Co-Authored-By trailer, semicolons to separate multiple thoughts, and only letters digits spaces and semicolons.
Use when renaming a Go symbol (a function, method, type, variable, struct field, or package-level identifier) across a module. Triggers on "rename this go function", "rename X to Y in this package", "rename this symbol everywhere", "rename this variable". Uses `gopls rename` for a type-correct module-wide rename instead of text substitution.
Run every go-review-* skill (style, nit, skeptic, and legibility if applicable) in parallel against a target Go directory and merge the findings. Use when the user wants a full review pass — e.g. "ultra-review @pkg/foo", "run all the go reviews on internal/search", "give me everything you've got on this package". Fans out via the Agent tool, deduplicates findings, and returns one combined report. Does not write code.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | pr-scope |
| description | Use when the user wants a PR scope assessment surfaced directly — "is this PR too big", "how should I split this", "chunk this into PRs", "scope check", or before opening a large PR. Runs the pr-scope-analyzer agent and relays its full output verbatim. |
Run the pr-scope-analyzer agent and surface its complete output to the user.
When a subagent finishes, its final message is returned to the top-level model as a tool result — the user never sees it directly. Left alone, the top-level model paraphrases the agent's carefully-formatted impact table, verdict, and dependency graph into a lossy summary. This skill exists to stop that: the agent's formatting is the deliverable, and it must reach the user intact.
Dispatch the agent. One Agent call, subagent_type: pr-scope-analyzer, run_in_background: false (you need the result in this turn). In the prompt, tell it what to assess: the current branch's changes by default, or a specific ref/directory if the user named one. The agent computes its own diff and carries its own instructions — keep the prompt to what to look at.
Relay verbatim. Your entire response is the agent's final message, reproduced exactly — the impact table, the verdict line, and the split recommendation with its dependency graph, character for character, in the layout the agent produced. Preserve the code fences and alignment. Add nothing before it and change nothing inside it.
You may add commentary only below the reproduced output, and only if the user asked a follow-up question the agent's report doesn't already answer. If they just asked for a scope check, the reproduced output is the whole response.
