cross-review-policy
About
This skill enforces that all code generated by Claude Code or Google Gemini must be reviewed by OpenAI Codex before being presented to the user. It implements an automated review workflow with a maximum of three iteration cycles for feedback and fixes. Use this skill to ensure AI-generated code passes through a mandatory cross-model quality gate.
Quick Install
Claude Code
Recommendednpx skills add majiayu000/claude-skill-registry -a claude-code/plugin add https://github.com/majiayu000/claude-skill-registrygit clone https://github.com/majiayu000/claude-skill-registry.git ~/.claude/skills/cross-review-policyCopy and paste this command in Claude Code to install this skill
GitHub Repository
Related Skills
legal-sanity-review
OtherThis mandatory workflow scans code for legal risks like client names or proprietary references before cross-review. It blocks the review cycle if violations are found, requiring fixes first. Use it as a pre-gate for PR creation, code porting, or any cross-review trigger.
brainstorming
OtherThe brainstorming skill transforms initial ideas into detailed specifications through iterative questioning and collaborative dialogue. It helps developers explore design options, evaluate trade-offs, and create shared understanding before implementation. This prevents rework by systematically refining concepts into actionable plans.
repo-cleanup-structure-section-updates
OtherThis skill handles repository structure documentation updates after cleanup operations. It automatically updates directory trees, removes references to deleted folders, and documents architectural changes like `.claude/` folders and consolidated scripts. Use it to maintain accurate structure sections in README files following repository reorganization.
repo-cleanup-progress-tracking-commands
OtherThis sub-skill provides shell commands for tracking file counts during repository cleanup operations, specifically for hidden folders like `.claude` and `.agent-os`. It includes verification scripts to ensure no files are lost after merging changes. Use it when consolidating or reorganizing project directories to monitor progress and validate results.
