Individual skill
evidence-review
Review a small code or documentation change and return only evidence-backed correctness findings. Use in the Codex How To local plugin lab; do not modify files or post remote comments.
examples/plugin-marketplace/plugins/engineering-review/skills/evidence-review/SKILL.md
Source commit 19a42f4c42019fa2ccefa3de6af56133b875b3e8
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 4, 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)
- 20
- Repository last updated
- Nov 6, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- codex Repository topic
- codex-cli Repository topic
- developer-tools Repository topic
- openai Repository topic
- agentic-workflows Repository topic
- code-review Repository topic
- coding-agents Repository topic
- devops Repository topic
- openai-codex Repository topic
- docs 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 · 635 bytes
Read excerpt
# Evidence Review
1. Read the requested diff and applicable repository guidance.
2. Trace each suspected problem to a concrete file, behavior, or broken contract.
3. Return actionable findings ordered by impact.
4. Include a precise location, failing scenario, evidence, and fix direction.
5. Omit style preferences and unsupported speculation.
6. State explicitly when no actionable finding is verified.