메뉴
Use this skill automatically when you feel your code ready for human review. This means the code works and achieves a stated goal, verified by your own tests and/or, if you deem it necessary, human testing.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Ask Claude Code to make a taste-driven call on something ambiguous — UI polish, prose phrasing, naming, formatting. Use when you'd otherwise guess.
Prepare Hubble desktop releases using tag-triggered GitHub Releases. Use when cutting, automating, or explaining app releases, version bumps, tags, GitHub Actions publishing, Electron artifacts, or updater release management.
Review a pull request or local branch diff for correctness, security, lifecycle, error handling, tests, and meaningful performance risks. Use when asked to review PR changes, a branch, a commit range, or the current working tree and return a structured review.
Request an automated review of the current pull request, address valid feedback, and repeat until approval. Use after opening a PR and before handing it to a human reviewer.
Add a user-facing entry to CHANGELOG.md for work that just landed. Use when wrapping up a feature/fix, or when asked to record what changed. Called standalone or from the `done` skill.
Open a pull request for the current branch. Use whenever asked to make/create/open a PR.
| name | simplify |
| description | Use this skill automatically when you feel your code ready for human review. This means the code works and achieves a stated goal, verified by your own tests and/or, if you deem it necessary, human testing. |
Review changes in the current branch, or in the state the user specifies. Apply these criteria without changing behavior:
Names: Shorten verbose names while keeping them clear. Prefer human-readable concepts (baseline) over compound phrases that are more mechanical / academic (lastObservedDiskContent).
Combine related concepts: If two types, functions, or constants overlap significantly, merge them. The fewer distinct concepts a reader must hold in their head, the better. Example: two union types sharing 3 of 4 values → one type with shorter value names.
Derivability: If a value can be computed from other values already in scope, don't pass or store it separately. Removing derivable state often simplifies signatures, types, and control flow in one move. Example: an isDirty parameter that's always derived from computing editorContent !== baseline can be dropped.
Scope: Only touch code in the staged diff. Run existing tests after every change.
