code-review

스타1

포크1

업데이트2026년 4월 27일 10:34

Review changes for bugs, regressions, missing tests, and maintainability risks.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

felixpahlke

felixpahlke/bobster

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Code Review

Use this skill when asked to review a patch, pull request, or local diff.

Review stance

Lead with findings ordered by severity.
Ground every finding in a concrete file and line.
Prioritize behavioral bugs, data loss, security issues, regressions, and missing tests.
Keep summaries secondary to findings.
Say clearly when no issues are found and name any residual risk.

Finding quality

Explain the failure mode, not just the disliked pattern.
Mention the triggering condition.
Keep suggested fixes scoped to the reviewed change.
Avoid broad refactors unless they are needed to correct the issue.

이 저장소의 다른 Skills

같은 저장소

customercare-mcp-builder

felixpahlke/bobster

Build MCP servers for customer care agents following Watson Orchestrate specifications. Guides agents through tool creation, transaction patterns, authentication, widgets, and context management with strict adherence to reference specifications. Use when creating customer care MCP servers.

2026-04-271

sop-builder

felixpahlke/bobster

Expert guidance for building a Standard Operating Procedure (SOP) from a workflow diagram, Langflow JSON, n8n JSON, BPMN model or workflow description. Focuses on business problem, data requirements, and business logic in plain language.

2026-04-271

watsonx-orchestrate

felixpahlke/bobster

explains how to work with watsonx-orchestrate (also: wxo, orchestrate) and the corresponding adk (cli). How to create & update agents, tools and other entities in orchestrate. Use this whenever asked anything wxo / orchestrate / watsonx orchestrate related.

2026-04-271

frontend-design

felixpahlke/bobster

Create distinctive, production-grade frontend interfaces with high design quality.

2026-04-271

name	code-review
description	Review changes for bugs, regressions, missing tests, and maintainability risks.

Code Review

Use this skill when asked to review a patch, pull request, or local diff.

Review stance

Lead with findings ordered by severity.
Ground every finding in a concrete file and line.
Prioritize behavioral bugs, data loss, security issues, regressions, and missing tests.
Keep summaries secondary to findings.
Say clearly when no issues are found and name any residual risk.

Finding quality

Explain the failure mode, not just the disliked pattern.
Mention the triggering condition.
Keep suggested fixes scoped to the reviewed change.
Avoid broad refactors unless they are needed to correct the issue.