원클릭으로
severity-classification
Classify review findings into blocking, non-blocking, or note with consistent merge-risk rules.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Classify review findings into blocking, non-blocking, or note with consistent merge-risk rules.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Resolve GitHub PR review comments safely, read unresolved comments, validate each issue, make minimal fixes, test, commit, and resolve.
Use zero-install context minimization first, with optional local optimization tooling when available.
Accessibility review for semantic HTML, ARIA, keyboard support, focus, screen readers, contrast, and WCAG-oriented issues.
API and contract review for OpenAPI/AsyncAPI/protobuf changes, backwards compatibility, schemas, status codes, and examples.
Architecture review for SOLID, layering, boundaries, coupling, cohesion, extensibility, and maintainability.
Backend review for handlers, services, validation, errors, transactions, dependency boundaries, and service contracts.
| name | severity-classification |
| description | Classify review findings into blocking, non-blocking, or note with consistent merge-risk rules. |
| license | MIT |
blocking means the PR should not merge as-is:
non_blocking means it should be fixed soon but can merge if accepted by owner:
note means useful context, not a requested change.
Do not inflate severity. If uncertain, use non_blocking or omit the finding.