메뉴
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/ffsshhttiikk/opencode-agents-skills --skill code-review명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
SOC 직업 분류 기준
| name | code-review |
| description | Code review best practices and guidelines |
| license | MIT |
| compatibility | opencode |
| metadata | {"audience":"developers","category":"code-quality"} |
When performing code reviews or addressing feedback.
**High: SQL Injection Vulnerability**
The user input is directly concatenated into the SQL query:
```python
query = f"SELECT * FROM users WHERE email = '{email}'"
Risk: An attacker could inject malicious SQL to extract or modify database data.
Fix: Use parameterized queries:
cursor.execute("SELECT * FROM users WHERE email = ?", (email,))
Required change - this is a security issue that must be fixed before merge.
### Improvement Suggestion
```markdown
**Medium: Consider using a context manager**
The current code manually manages the database connection:
```python
connection = get_db_connection()
try:
process_data(connection)
finally:
connection.close()
Suggestion: Using a context manager ensures proper cleanup even on exceptions:
with get_db_connection() as connection:
process_data(connection)
This is more Pythonic and handles edge cases automatically. Not blocking, but recommended.
### Style/Convention
```markdown
**Low: Line length**
This line exceeds our 100 character limit:
```python
some_function(argument_one, argument_two, argument_three=some_value, argument_four=other_value)
Fix: Break onto multiple lines:
some_function(
argument_one,
argument_two,
argument_three=some_value,
argument_four=other_value,
)
We use Black formatter - running black . will auto-fix this.
### Positive Reinforcement
```markdown
**Great work!** The error handling here is excellent. Using a custom exception hierarchy makes the code very clear about what can go wrong and where. Thanks for the thorough docstrings too!
[] Code compiles/runs without errors
[] Tests pass (unit, integration, e2e)
[] No security vulnerabilities
[] Performance is acceptable
[] Follows naming conventions
[] Adequate error handling
[] Input validation present
[] No hardcoded secrets
[] No debug code left in
[] Documentation updated
[] Comments are helpful
[] No dead code
[] No code duplication
[] Logging is appropriate
[] Metrics/monitoring if needed