Individual skill
review
Comprehensive security and correctness audit. Use for review, deep review, thermo nuclear, or thermonuclear requests and branch or PR diff audits.
packages/eve-code/extension/skills/review/SKILL.md
Source commit d1578ec3ff6b83ee2a4816018f5d33aa80a504cd
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 7, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 5,820
- Repository last updated
- Nov 7, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent Repository topic
- framework Repository topic
- harness Repository topic
- javascript Repository topic
- markdown Repository topic
- typescript Repository topic
- vercel Repository topic
- sandbox Repository topic
- workflows Repository topic
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 1,576 bytes
Read excerpt
# Deep review
When you can start a fresh-context agent, give it a self-contained audit brief that names the repository, the ref or diff, and an instruction not to edit. Otherwise, audit in this session. Either way, you evaluate the findings and own the final verdict.
Audit changed code and its necessary surrounding context for bugs, broken functionality, security vulnerabilities, developer-experience regressions, and feature-gate leaks. Cite repository evidence for every finding. Report only issues introduced or exposed by code added or modified in the reviewed change.
## Required checks
- Trace cross-package and runtime side effects end to end.
- Check authorization, untrusted input, credential disclosure, destructive behavior, and bounded work.
- Check local build and run workflows, changed environment variables, ports, networking, and required setup.
- Verify internal or gated features remain gated.
- Distinguish intended, well-contained breakage from accidental consequences.
- Calibrate priority carefully; do not inflate speculative or low-impact concerns.