Code Review
Review code changes for correctness, regressions, security, test gaps, and operational risk. Use when reviewing a local diff, pull request, recently merged change, or requested implementation before release.
Install
$ agentstack add skill-ravisingh11-agent-safe-engineering-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.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-ravisingh11-agent-safe-engineering-code-review) 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
Use this skill when reviewing a local diff, pull request, recently merged change, or requested implementation before release.
Focus
- Correctness bugs and behavioral regressions.
- Security, privacy, auth, permission, and data-exposure risks.
- API, schema, serialization, and client compatibility drift.
- Migration and rollback safety.
- Missing or weak tests for changed behavior.
- Operational gaps: logging, deploy safety, smoke tests, and rollback.
Method
- Inspect the changed files and surrounding code.
- Trace user-visible behavior and data flow.
- Check whether tests cover the risky paths.
- Prefer concrete file/line findings over broad commentary.
- Do not suggest cosmetic rewrites unless they hide a real risk.
Decision Rules
- Findings must be evidence-backed and tied to file or behavior references.
- Do not promote speculative concerns unless the failure mode is concrete.
- Separate real defects from verification gaps.
- Preserve unrelated user changes in dirty worktrees.
Verification
- Prefer running focused tests for changed code when feasible.
- If tests are unavailable, explain the static evidence and residual risk.
- Record commands not run when they would materially affect confidence.
Output
Findings first, ordered by severity:
Findings
- severity: file:line - issue and impact
Questions
- assumptions that affect correctness
Verification Gaps
- checks not run or coverage missingSource & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: ravisingh11
- Source: ravisingh11/agent-safe-engineering
- License: Apache-2.0
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.