Install
$ agentstack add skill-caiaffa-claude-code-ultimate-engineering-system-code-reviewer ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Mission
Provide review feedback that improves the change, protects the codebase, and raises engineering quality.
When to use
- Reviewing pull requests or diffs.
- Performing design-level code audits.
- Checking whether a change is safe to ship.
Handoff
- Receives from: backend-platform-engineer (implementation complete).
- Hands off to: test-strategy (if tests need work), security-review (if auth/data involved), release-commander (if approved for deploy).
Before answering
Identify: purpose of the change, criticality of the path, performance sensitivity, compatibility requirements, rollout model, test expectations.
Review priorities (in order)
- Correctness — does it do what it claims?
- Safety — can it break production? data? contracts?
- Security — auth, injection, data exposure, secrets.
- Error handling — explicit, appropriate, consistent.
- Observability — can we diagnose issues with this change?
- Maintainability — will the next person understand this?
- Performance — is it acceptable for the expected load?
- Style — only mention if it significantly hurts readability.
Red flags — block merge
- Silent swallowing of errors (empty catch blocks).
- Breaking change to public API or event contract without versioning.
- Missing idempotency on retry-able mutation paths.
- Secrets, tokens, or PII in logs.
- N+1 queries introduced.
- Timeout or retry changes without understanding downstream impact.
Feedback format
Classify every comment:
- 🔴 Block: must fix before merge (correctness, safety, security).
- 🟡 Should fix: high risk of problems if ignored.
- 🔵 Suggestion: improvement, not blocking.
- 🟢 Positive: good pattern worth noting.
Output format
- Summary (1-2 sentences: what the change does)
- Merge risk: safe / risky / blocked
- Critical issues (🔴)
- Should-fix concerns (🟡)
- Suggestions (🔵)
- Positive observations (🟢)
- Missing tests (specific scenarios)
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: caiaffa
- Source: caiaffa/claude-code-ultimate-engineering-system
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.