codex-review
Review Code and Generate Changelogs
Code reviews can miss regressions, risky refactors, and release notes. This skill guides Codex, Claude, and Claude Code through review and CHANGELOG workflows.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "codex-review" from https://skillstore.io/skills/sickn33-codex-review.md and its manifest at https://skillstore.io/api/skills/sickn33-codex-review/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "codex-review". Review my staged changes before commit.
Expected outcome:
A prioritized review with defects, risks, missing tests, and a short commit readiness summary.
Using "codex-review". Review this refactor and update release notes.
Expected outcome:
A refactor-focused review with behavior risks and a CHANGELOG entry recommendation.
Using "codex-review". Check this branch before release.
Expected outcome:
A maintainer review covering merge risk, validation status, and release note completeness.
Security Audit
SafeStatic findings were reviewed in context. The flagged shell execution markers are Markdown code fences around an installation command, and the hardcoded URL is a GitHub documentation link. No semantic security issues or prompt injection attempts were found.
Risk Factors
โ๏ธ External commands (2)
๐ Network access (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-codex-review/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-codex-review?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-codex-review?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-codex-review/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-codex-review.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
sickn33. (2026). codex-review security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-codex-review/audits/4BibTeX citation
@techreport{sickn33-sickn33-codex-review-2026,
author = {sickn33},
title = {codex-review security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/sickn33-codex-review/audits/4},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "codex-review security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/sickn33-codex-review/audits/4"
identifiers:
- type: other
value: "skillstore:sickn33-codex-review:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Pre-Commit Review
Run a structured review before committing changes to catch defects and missing release notes.
Refactor Validation
Check broad refactoring work for behavior changes, incomplete updates, and documentation gaps.
Release Note Preparation
Review changes and prepare CHANGELOG entries that match the project workflow.
Try These Prompts
Use codex-review to review my current changes before I commit them.
Use codex-review to review my changes and suggest the needed CHANGELOG update.
Use codex-review to inspect this refactor for behavior changes, missed call sites, and test gaps.
Use codex-review to perform a maintainer-level review of this branch, including risk, tests, and CHANGELOG impact.
Best Practices
- Keep CHANGELOG.md in the project root.
- Use conventional commit messages for clearer change summaries.
- Provide the full diff and relevant tests for better review quality.
Avoid
- Running review with incomplete or hidden diffs.
- Accepting CHANGELOG suggestions without checking project release rules.
- Using the skill as a replacement for required human approval.