Loading...
Loading...
Found 1,194 Skills
Code review — both giving and receiving feedback. Verifying observed behavior over performative agreement. Use when reviewing a PR, requesting review on completed work, or processing review feedback you received.
Guidance for receiving and responding to code review feedback. Use when addressing PR review comments, incorporating reviewer suggestions, or managing review discussions.
Perform code optimization for .vue, .js, .css, .scss, .less files in Vue2 projects. By default, optimize git changed files, or execute according to the user-specified scope. Unify code structure, BEM styles, semantic naming and key comments to improve readability and collaboration efficiency. Do not generate new components or modify business logic. Trigger scenarios: Users request code optimization, code structure standardization, unified naming, Vue2 component optimization, and code style organization.
Modern PHP application development guidance for PHP 8.3+, Symfony, Composer, PHPUnit/Pest, PHPStan, Psalm, PSR standards, Doctrine, DTOs, value objects, dependency injection, migrations, middleware, and REST or GraphQL APIs. Use when Codex needs to build, refactor, test, statically analyze, or review PHP code and framework integrations.
Use when about to submit work, before committing or pushing, to run verification commands and confirm the work actually passes before claiming completion
Performs a structured code review on the current diff or specified files. Checks for correctness, security vulnerabilities, test coverage, code style, and adherence to the project's architecture patterns. Invoked when the user asks for a review, code check, pr review, or quality assessment.
Run a read-only, fresh-context branch-diff code review and report findings. Use when running /review-code, before finishing issue work, or when a local review gate should inspect committed, staged, unstaged, and untracked changes without mutating code or GitHub state.
Perform thorough code reviews following Google's 5-step methodology. Use when reviewing pull requests, change lists, or any code changes to ensure quality, correctness, and maintainability.
Apply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach it, resist nil-check guards that silence crashes.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when a subtask is ready to implement and has a subtask JSON file with acceptance criteria and deliverables.
Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the rule as a lint, metadata flag, runtime check, or script instead of more text.