Install
$ agentstack add skill-anthroos-claude-code-orchestrator-code-review ✓ 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.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Code Review
> Review code changes against a structured checklist covering security, performance, architecture, and correctness.
When to use
- "Review this PR"
- "Check my code"
- "Code review for #123"
- Before merging any PR
How to execute
Step 1: Load the changes
# For a PR
gh pr diff
# For local changes
git diff main...HEAD
Step 2: Review checklist
Go through each category:
Security
- [ ] No hardcoded secrets, API keys, or credentials
- [ ] User input is validated and sanitized
- [ ] No SQL injection, XSS, or command injection vectors
- [ ] Authentication/authorization checks in place
- [ ] Sensitive data not logged or exposed in errors
Correctness
- [ ] Logic handles edge cases (null, empty, negative, overflow)
- [ ] Error handling is appropriate (not swallowed, not over-caught)
- [ ] Race conditions considered for concurrent code
- [ ] Resource cleanup (files, connections, locks)
Performance
- [ ] No N+1 queries or unnecessary loops
- [ ] Large datasets paginated or streamed
- [ ] Caching used where appropriate
- [ ] No blocking operations in async code
Architecture
- [ ] Changes follow existing patterns in the codebase
- [ ] No unnecessary dependencies added
- [ ] Public API surface is intentional
- [ ] No dead code or commented-out blocks
Tests
- [ ] New code has tests
- [ ] Edge cases are covered
- [ ] Tests are deterministic (no flaky tests)
Step 3: Report findings
Format: severity + file + line + description
[CRITICAL] src/auth.py:42 — SQL query built with string concatenation
[WARNING] src/api.py:108 — Missing error handling for network timeout
[SUGGESTION] src/utils.py:15 — Could use list comprehension for clarity
Step 4: Summary
Provide:
- Overall assessment (approve / request changes / needs discussion)
- Critical issues (must fix before merge)
- Suggestions (nice to have)
Parameters
| Parameter | Description | Default | |-----------|-------------|---------| | PR number | GitHub PR to review | current branch diff | | --focus security | Focus on security checks only | all checks |
Related skills
git-workflow— merge after review passes
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: anthroos
- Source: anthroos/claude-code-orchestrator
- 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.