Code Review & Quality

Code review, refactoring, debugging, maintainability, and engineering quality

skills in category: 15,943
pages available: 665

Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.

Open in full browser

Browse code review & quality skills

Showing 2,089–2,112 of 15,943 skills

Encapsulate CollectionA컬렉션 getter가 내부 List/Set을 직접 노출하는 것을 방지 — unmodifiable 반환 + add/remove 메서드 제공. "컬렉션 캡슐화", "getter가 List 그대로 노출", "unmodifiable로", "/encapsulate-collection" 요청 시 사용. 단, 컬렉션과 관련 로직을 전용 클래스로 뽑는 것은 /first-class-collection이 적합. /encapsulate-collection [commit-ref]로 호출.code-qualitygojavaVotes: 0GitHub stars: 8
Discover Value ObjectAPrimitive Obsession 제거 — 검증·연산이 따라다니는 primitive 필드(금액+통화, 이메일 문자열 등)를 도메인 개념을 담은 Value Object로 치환. "값 객체 도입", "primitive obsession", "Money 클래스로", "/discover-value-object" 요청 시 사용. 단, 함께 전달되는 파라미터 묶음을 객체로 바꾸는 것은 /introduce-parameter-object, 컬렉션을 감싸는 것은 /first-class-collection이 적합. /discover-value-object [commit-ref]로 호출.code-qualitygojavaVotes: 0GitHub stars: 8
Decompose ConditionalA복잡한 if/then/else의 조건식과 각 분기를 의미 있는 메서드로 추출하여 가독성 향상. "조건문 분해", "if 가독성", "복잡한 조건식에 이름 붙여", "/decompose-conditional" 요청 시 사용. 단, 같은 결과를 내는 조건문들을 하나로 합치는 것은 /consolidate-conditional, 타입별 분기를 클래스로 바꾸는 것은 /replace-conditional-with-poly가 적합. /decompose-conditional [commit-ref]로 호출.code-qualitygojavaVotes: 0GitHub stars: 8
Consolidate ConditionalA동일한 결과를 내는 여러 조건문(OR 나열·중첩 AND)을 하나로 통합하고 의미 있는 boolean 메서드로 추출. "조건문 합쳐", "같은 결과 반환하는 if 정리", "중첩 if 평탄화", "/consolidate-conditional" 요청 시 사용. 단, 여러 메서드에 흩어진 동일 조건을 호출자 쪽으로 올리는 것은 /lift-up-conditional, 복잡한 조건식·분기를 메서드로 쪼개는 것은 /decompose-conditional이 적합. /consolidate-conditional [commit-ref]로 호출.code-qualitygojavaVotes: 0GitHub stars: 8
Review PrAReview a PR with JIRA validation, architecture checks, impact analysis, and interactive recommendationscode-qualityrustgoVotes: 0GitHub stars: 5
PrACommit all changes, push to a new branch, and create a pull request using the repo's PR template. Use ONLY when the user has explicitly asked for a pull request in so many words — e.g. "make a PR", "open a pull request", "PR this", "submit this as a PR". Never use it for a request that stops short of a PR (commit, push, branch), and never infer it from finished work.code-qualitygobashVotes: 0GitHub stars: 570
Symptom CheckACheck whether a proposed non-trivial bug fix restores the underlying invariant or only hides a symptom. Use after initial debugging and before production edits; not for trivial mechanical changes, greenfield features, or broad audits. Diagnosis and review remain read-only unless implementation is authorized.code-qualitygodebuggingVotes: 0GitHub stars: 12
Interpretability AuditAAudit code for intent transparency and reader comprehension. Use for understandable, readable, self-explanatory, naming, or future-maintainer clarity reviews; not for bug/security, architecture, DX, or lint-only reviews.code-qualitygosecurityVotes: 0GitHub stars: 12
Dx AuditAAudit a codebase's AI developer experience, including project instructions, verification commands, automation, onboarding traps, and collaboration friction. Not for ordinary bug, security, architecture, readability, or PR reviews.code-qualitygorefactoringVotes: 0GitHub stars: 12
Design AuditAAudit code architecture and maintainability for unnecessary complexity, premature or missing abstractions, duplication, unclear boundaries, and refactoring opportunities. Not for bug, security, or readability-only reviews.code-qualitygotestingVotes: 0GitHub stars: 12
Symptom CheckACheck whether a proposed non-trivial bug fix restores the underlying invariant or only hides a symptom. Use after initial debugging and before production edits; not for trivial mechanical changes, greenfield features, or broad audits. Diagnosis and review remain read-only unless implementation is authorized.code-qualitygodebuggingVotes: 0GitHub stars: 12
Interpretability AuditAAudit code for intent transparency and reader comprehension. Use for understandable, readable, self-explanatory, naming, or future-maintainer clarity reviews; not for bug/security, architecture, DX, or lint-only reviews.code-qualitygosecurityVotes: 0GitHub stars: 12
Dx AuditAAudit a codebase's AI developer experience, including project instructions, verification commands, automation, onboarding traps, and collaboration friction. Not for ordinary bug, security, architecture, readability, or PR reviews.code-qualitygorefactoringVotes: 0GitHub stars: 12
Design AuditAAudit code architecture and maintainability for unnecessary complexity, premature or missing abstractions, duplication, unclear boundaries, and refactoring opportunities. Not for bug, security, or readability-only reviews.code-qualitygotestingVotes: 0GitHub stars: 12
Optimize Agent InstructionsAOptimize project agent instruction files. Use for optimize/improve/clean up/review Claude.md or making persistent CLAUDE.md or AGENTS.md guidance more concise, concrete, and reliable; not for ordinary docs or code reviews.code-qualitygogitVotes: 0GitHub stars: 12
Self ReviewAScrape Claude Code session history to find repeated user corrections, preferences, and contextual guidance, then surface candidates for CLAUDE.md or memory. Use when the user wants to review past sessions for self-improvement, find patterns in their feedback, or bake recurring preferences into persistent configuration.code-qualityrustgoVotes: 0GitHub stars: 3
PrAOpen a pre-populated GitHub PR creation page in the browser, with a title and body drafted in nvie's personal writing style. Use when the user runs /pr, or asks to "open a PR", "create a PR", or "draft a PR" for the current branch. This skill never creates the PR itself -- the user reviews and submits it manually.code-qualitygobashVotes: 0GitHub stars: 3
Pr ReviewAReview one or more GitHub pull requests as a progressive, understanding-first code review -- start at the highest altitude (what does it do, how, what to grasp before the details) and descend one abstraction layer at a time only when asked. Built for a senior engineer who wants to understand a PR before spending review time on it. Use when the user runs /pr-review with one or more PR links (often a frontend + backend pair), or asks to "review this PR" / "review these PRs". Treats the code dif...code-qualitygoreactVotes: 0GitHub stars: 3
MikadoAMikado method workflow for complex refactorings. Use when the user invokes /mikado, mentions "mikado graph", or wants to break a large code change into safe, incremental steps with automatic revert-on-failure.code-qualitygonodeVotes: 0GitHub stars: 3
Parser InternalsAunderstand, debug, or extend the cfmleditor-lsp parser — scanner tokenisation, the two parse loops, call-site extraction, and how the unresolved command workscode-qualitygoexpressVotes: 0GitHub stars: 4
Intellij IdeaAHow to use IntelliJ IDEA's MCP tools as a read-only semantic oracle while coding Java/Spring Boot. Use this skill WHENEVER the IntelliJ MCP server is connected and the task involves understanding or validating the codebase — finding where a symbol is used, understanding a type, or checking for problems. Consult it before reaching for grep on a Java question, and after any batch of edits. The agent is the sole writer; IntelliJ never mutates files and never runs code.code-qualityrustgoVotes: 0GitHub stars: 15
Code Quality ReviewAJava code quality checklist for Spring Boot applications, plus design placement and workload fit against the project's recorded briefs. Load when conducting code quality reviews.code-qualitypythongoVotes: 0GitHub stars: 15
Code Quality GateABuild, test, format, and lint requirements that must pass before code review. Load when checking implementation completeness or running the quality gate.code-qualitypythonrustVotes: 0GitHub stars: 15
GolandAHow to use GoLand's MCP tools as a read-only semantic oracle while coding Go. Use this skill WHENEVER the GoLand MCP server is connected and the task involves understanding or validating the codebase — finding where a symbol is used, understanding a type, or checking for problems. Consult it before reaching for grep on a Go-symbol question, and after any batch of edits. The agent is the sole writer; GoLand never mutates files and never runs code.code-qualityrustgoVotes: 0GitHub stars: 15