Skip to content
TrustedSkillsbeta
Back to all skills

Code Change Verification

Official
openai·vlatest·ai-ml·MIT

Verifies code changes suggested by OpenAI's models against existing tests and project requirements.

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 openai/openai-agents-js --skill code-change-verification -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

openai

Matched to the vendor's own GitHub organisation.

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 openai/openai-agents-js at fdaf0a66ca.

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

Commit
fdaf0a66ca
Manifest
.agents/skills/code-change-verification/SKILL.md
Scanned
5 files, 193 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

What it does

This skill enables AI agents to automatically verify that code changes align with specific requirements or constraints. It acts as a safety layer, ensuring modifications meet defined criteria before they are accepted or deployed.

When to use it

  • Validate generated code against strict security policies before integration.
  • Ensure refactored logic maintains original functionality without introducing regressions.
  • Confirm that new features adhere to established architectural patterns.
  • Check compliance with coding standards in automated CI/CD pipelines.

Key capabilities

  • Analyzes input code changes for adherence to specified rules.
  • Compares modified code against baseline requirements or constraints.
  • Provides clear feedback on whether the changes pass verification checks.

Example prompts

  • "Verify that this Python function update includes proper error handling for network timeouts."
  • "Check if these React component changes maintain accessibility standards defined in our style guide."
  • "Validate that the database migration script does not violate existing data integrity constraints."

Tips & gotchas

Ensure your verification rules are precise and unambiguous to avoid false negatives. This skill works best when paired with a clear definition of what constitutes a successful code change.