원클릭으로 Manus에서 모든 스킬 실행

codex-review

스타9

포크0

업데이트2026년 4월 6일 20:44

Requests an independent code review from OpenAI Codex CLI, critically evaluates its findings, and applies warranted fixes. Activates when: the user says /codex-review, asks for a Codex review, or wants an external AI review of changes.

설치

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

Manus에서 실행

출처

SanderMuller

SanderMuller/Stopwatch

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

다운로드

Manus에서 실행

Codex Code Review

Run an independent code review using OpenAI Codex CLI, then critically evaluate and apply warranted findings.

Step 1: Determine what to review

Check what has changed:

git diff --stat HEAD
git diff --stat --staged

If there are uncommitted changes, review those (--uncommitted). If the working tree is clean, review the latest commit (--commit HEAD).

Step 2: Run Codex review

Run the appropriate command:

For uncommitted changes:

codex exec review --full-auto --uncommitted "Review for correctness, security, edge cases, and test coverage gaps. This is a Laravel validation package. Focus on: rule compilation ordering, fast-check correctness, FormRequest lifecycle compatibility, and cross-field wildcard handling. Be concise — only report real issues, not style preferences."

For the latest commit:

codex exec review --full-auto --commit HEAD "Review for correctness, security, edge cases, and test coverage gaps. This is a Laravel validation package. Focus on: rule compilation ordering, fast-check correctness, FormRequest lifecycle compatibility, and cross-field wildcard handling. Be concise — only report real issues, not style preferences."

For changes against main:

codex exec review --full-auto --base main "Review for correctness, security, edge cases, and test coverage gaps. This is a Laravel validation package. Focus on: rule compilation ordering, fast-check correctness, FormRequest lifecycle compatibility, and cross-field wildcard handling. Be concise — only report real issues, not style preferences."

Step 3: Critically evaluate findings

Codex findings are suggestions, not mandates. For each finding:

Is it a real bug? — Verify by reading the code. Don't trust Codex's assessment blindly.
Is it already tested? — Check if existing tests cover the scenario.
Is it a style preference? — Skip. Don't change working code for style.
Is it a false positive? — Codex may misunderstand Laravel internals or the package's architecture. Verify against the actual behavior.

Step 4: Apply warranted fixes

For findings that are genuine issues:

Fix the code
Run vendor/bin/pest --no-coverage to verify
Run vendor/bin/phpstan analyse src/ --memory-limit=2G to verify

Step 5: Report

Summarize to the user:

## Codex Review Summary

### Applied
- [Issue] — [What was wrong and how you fixed it]

### Dismissed
- [Finding] — [Why it was dismissed: false positive / already tested / style preference]

### No Issues
- [Categories that were clean]

이 저장소의 다른 Skills

같은 저장소

stopwatch-profile

SanderMuller/Stopwatch

Profile a slow request, command, or code path with sandermuller/stopwatch. Activate when the user mentions: slow request, slow endpoint, slow page, slow query, slow job, slow command, slow API call, slow HTTP, performance issue, profile this, why is this slow, where is the time going, optimize, bottleneck, latency, n+1, query count, memory usage, http calls, outbound requests, server-timing.

2026-05-069

pre-release

SanderMuller/Stopwatch

Pre-push / pre-release checklist. Runs Rector, Pint, Pest, PHPStan, audits README + `.ai/` docs for staleness, then commits + pushes, watches CI for green, and drafts release notes against the verified SHA. Activate before: pushing to remote, tagging a release, writing release notes, or when user mentions: pre-release, pre-push, release checklist, ship, cut release, release notes.

2026-05-069

ai-guidelines

SanderMuller/Stopwatch

MUST USE when creating, updating, or managing AI skills and guidelines. Activates when: creating a new skill, editing existing skills, updating coding guidelines, modifying AI instructions, working with .ai/ directory, or when user mentions: skill, CLAUDE.md, guidelines, AI configuration.

2026-04-069

autoresearch

SanderMuller/Stopwatch

Autonomous performance optimization loop. Iteratively reduces query count and execution time by modifying code, benchmarking, and keeping/reverting changes. Activates when: optimizing performance, reducing overhead, improving execution time, benchmarking, or when user mentions: autoresearch, optimize, performance, benchmark.

2026-04-069

backend-quality

SanderMuller/Stopwatch

Runs backend code quality checks in two tiers: Pint + related tests (every change), PHPStan + full suite (completion only). Activate after making changes to PHP files, or when user mentions: phpstan, pint, code quality, static analysis, code style, run checks.

2026-04-069

bug-fixing

SanderMuller/Stopwatch

Test-driven bug fixing workflow. Activates when: fixing bugs, debugging issues, resolving defects, investigating errors, or when user mentions: bug, fix, broken, not working, error, issue, defect, regression.

2026-04-069

name	codex-review
description	Requests an independent code review from OpenAI Codex CLI, critically evaluates its findings, and applies warranted fixes. Activates when: the user says /codex-review, asks for a Codex review, or wants an external AI review of changes.
user_invocable	true

Codex Code Review

Run an independent code review using OpenAI Codex CLI, then critically evaluate and apply warranted findings.

Step 1: Determine what to review

Check what has changed:

git diff --stat HEAD
git diff --stat --staged

If there are uncommitted changes, review those (--uncommitted). If the working tree is clean, review the latest commit (--commit HEAD).

Step 2: Run Codex review

Run the appropriate command:

For uncommitted changes:

codex exec review --full-auto --uncommitted "Review for correctness, security, edge cases, and test coverage gaps. This is a Laravel validation package. Focus on: rule compilation ordering, fast-check correctness, FormRequest lifecycle compatibility, and cross-field wildcard handling. Be concise — only report real issues, not style preferences."

For the latest commit:

codex exec review --full-auto --commit HEAD "Review for correctness, security, edge cases, and test coverage gaps. This is a Laravel validation package. Focus on: rule compilation ordering, fast-check correctness, FormRequest lifecycle compatibility, and cross-field wildcard handling. Be concise — only report real issues, not style preferences."

For changes against main:

codex exec review --full-auto --base main "Review for correctness, security, edge cases, and test coverage gaps. This is a Laravel validation package. Focus on: rule compilation ordering, fast-check correctness, FormRequest lifecycle compatibility, and cross-field wildcard handling. Be concise — only report real issues, not style preferences."

Step 3: Critically evaluate findings

Codex findings are suggestions, not mandates. For each finding:

Is it a real bug? — Verify by reading the code. Don't trust Codex's assessment blindly.
Is it already tested? — Check if existing tests cover the scenario.
Is it a style preference? — Skip. Don't change working code for style.
Is it a false positive? — Codex may misunderstand Laravel internals or the package's architecture. Verify against the actual behavior.

Step 4: Apply warranted fixes

For findings that are genuine issues:

Fix the code
Run vendor/bin/pest --no-coverage to verify
Run vendor/bin/phpstan analyse src/ --memory-limit=2G to verify

Step 5: Report

Summarize to the user:

## Codex Review Summary

### Applied
- [Issue] — [What was wrong and how you fixed it]

### Dismissed
- [Finding] — [Why it was dismissed: false positive / already tested / style preference]

### No Issues
- [Categories that were clean]