code-change-verification
Run the mandatory verification stack when changes affect runtime code, tests, or build/test behavior in the OpenAI Agents Python repository.
Run the mandatory verification stack when changes affect runtime code, tests, or build/test behavior in the OpenAI Agents Python repository.
General Correctness rules, Rust patterns, comments, avoiding over-engineering. When writing code always take these into account
Perform security-focused differential code review on changesets, pull requests, and commits. Use when reviewing diffs for security implications, assessing whether code changes introduce vulnerabilities, or comparing before/after states of security-sensitive code.
Write and review secure modern Python code following current best practices. Use when auditing Python applications for security issues, implementing secure patterns with modern Python features (3.10+), reviewing Python web frameworks, or hardening Python deployments.
Verifies code implements exactly what documentation specifies for blockchain audits. Use when comparing code against whitepapers, finding gaps between specs and implementation, or performing compliance checks for protocol implementations.
Verifies code implements exactly what documentation specifies for blockchain audits. Use when comparing code against whitepapers, finding gaps between specs and implementation, or performing compliance checks for protocol implementations.
The agent patches the system under test (SUT) to overcome common fuzzing obstacles using conditional compilation. It bypasses checksum and hash verification, replaces non-deterministic PRNG seeding with fixed seeds, skips complex multi-stage validation, and provides safe default values to prevent false positives. The agent uses FUZZING_BUILD_MODE_UNSAFE_FOR_PRODUCTION in C/C++ and cfg!(fuzzing) in Rust to ensure patches apply only during fuzzing builds. It applies this technique when coverage reports reveal unreachable code behind checksums, cryptographic signatures, time-seeded random state, or expensive validation logic that blocks fuzzer exploration of deeper code paths in libFuzzer, AFL++, honggfuzz, cargo-fuzz, and LibAFL targets.
Review code changes in dotnet/runtime for correctness, performance, and consistency with project conventions. Use when reviewing PRs or code changes.
Audit serialization proxy correctness and round-trip safety
Interpret validation errors and guide fixing them. Use when encountering validation errors, validation warnings, false positives, operator structure issues, or need help understanding validation results. Also use when asking about validation profiles, error types, or the validation loop process.
Full audit of Agent Zero plugins in usr/plugins/. Reviews manifest validity, directory structure, code patterns (Store Gating, notifications, imports), security, and duplicate detection against the community index. Use when asked to review, audit, validate, or check an existing plugin before using or contributing it.
Review code for quality, bugs, and improvements. Use when user wants code review or quality assessment.
Code review specialist focused on patterns, bugs, security, and performance
Rust programming expert for ownership, lifetimes, async/await, traits, and unsafe code
Code review a pull request for bugs and CLAUDE.md compliance. MUST use when asked to review code.
Code review a pull request for bugs and CLAUDE.md compliance. MUST use when asked to review code.
Rust coding guidelines for the Windmill backend. MUST use when writing or modifying Rust code in the backend directory.
Svelte coding guidelines for the Windmill frontend. MUST use when writing or modifying code in the frontend directory.
MUST use when writing Deno/TypeScript scripts.