Skip to content
TrustedSkillsbeta
Back to all skills

Codex Review

Checked
davila7·vlatest·frontend·MIT

Reviews frontend code for style, best practices, potential bugs, and accessibility issues using Codex expertise.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add davila7/claude-code-templates --skill codex-review -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

davila7

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned davila7/claude-code-templates at 79182c51fb.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
79182c51fb
Manifest
cli-tool/components/skills/development/codex-review/SKILL.md
Scanned
1 file, 36 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

The codex-review skill enables AI agents to perform comprehensive code reviews by analyzing files against a specific set of rules defined in a .codexrc configuration file. It automatically detects issues, suggests improvements, and ensures adherence to project-specific standards before merging or deploying changes.

When to use it

  • Before committing large batches of code to ensure compliance with team conventions.
  • During pull request workflows to validate logic and style automatically.
  • When integrating new developers into a project to enforce consistent coding patterns immediately.
  • For continuous integration pipelines to block builds that fail custom linting rules.

Key capabilities

  • Parses .codexrc files to load custom rule sets for specific projects.
  • Analyzes codebases for structural errors, style violations, and best practice deviations.
  • Generates actionable feedback reports highlighting specific lines needing attention.
  • Supports iterative review cycles by re-checking modified files after fixes are applied.

Example prompts

  • "Run a full codex review on the src/components directory using our standard .codexrc rules."
  • "Review this pull request's changes and list any violations found against the project configuration."
  • "Fix the issues identified in the last codex review and regenerate the report."

Tips & gotchas

Ensure a valid .codexrc file exists in your repository root; without it, the skill defaults to generic checks that may miss project-specific nuances. For best results, keep rule definitions concise to avoid false positives during automated scans.