编码规范、框架、重构、代码审查（1.7万 个）
Update Codex's pinned `v8` / `rusty_v8` versions, validate the release-candidate path, and investigate failed V8 canary or artifact builds. Use when asked to bump V8, update `rusty_v8` artifacts, prepare or validate a V8 release candidate, check `v8-canary`, or diagnose why a V8 version update no longer builds.
中文简介正在准备中。当前显示原文说明。
Pushing GitHub Actions changes, resolving push rejection, requesting upload exceptions.
中文简介正在准备中。当前显示原文说明。
Run a GitHub issue digest for openai/codex by feature-area labels, all areas, and configurable time windows. Use when asked to summarize recent Codex bug reports or enhancement requests, especially for owner-specific labels such as tui, exec, app, or similar areas.
中文简介正在准备中。当前显示原文说明。
Diagnose GitHub bug reports in openai/codex. Use when given a GitHub issue URL from openai/codex and asked to decide next steps such as verifying against the repo, requesting more info, or explaining why it is not a bug; follow any additional user-provided instructions.
中文简介正在准备中。当前显示原文说明。
Run a final code review on a pull request
中文简介正在准备中。当前显示原文说明。
Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).
中文简介正在准备中。当前显示原文说明。
Change size guidance (800 lines)
中文简介正在准备中。当前显示原文说明。
Breaking changes
中文简介正在准备中。当前显示原文说明。
Update the title and body of one or more pull requests.
中文简介正在准备中。当前显示原文说明。
Build or modify backend APIs, services, jobs, persistence, and integrations while preserving contracts, authorization, data integrity, and failure behavior. Use for server-side features, database changes, background processing, backend defects, and service refactors; do not use for frontend-only or infrastructure-only work.
中文简介正在准备中。当前显示原文说明。
Maintain a review-first Markdown knowledge base for Codex practices with source provenance, engineering capture, citation-aware queries, explicit archive and promotion, and deterministic linting. Use when asked to capture a durable engineering lesson, ingest Codex research, query or archive what the repository knows, check wiki health, reconcile conflicting guidance, or promote verified knowledge.
中文简介正在准备中。当前显示原文说明。
Build or modify frontend interfaces using repository-native components while preserving accessibility, responsive behavior, state handling, and visual verification. Use for UI features, design implementation, forms, client-side defects, and frontend refactors; do not use for backend-only or infrastructure-only work.
中文简介正在准备中。当前显示原文说明。
Review code changes for correctness defects, regressions, security risks, data-integrity problems, concurrency hazards, and missing meaningful tests. Use for pull requests, branches, commits, patches, or working-tree reviews; do not use for implementation unless the user separately requests fixes.
中文简介正在准备中。当前显示原文说明。
Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.
中文简介正在准备中。当前显示原文说明。
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
中文简介正在准备中。当前显示原文说明。
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
中文简介正在准备中。当前显示原文说明。
Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` — or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.
中文简介正在准备中。当前显示原文说明。
Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.
中文简介正在准备中。当前显示原文说明。
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
中文简介正在准备中。当前显示原文说明。
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
中文简介正在准备中。当前显示原文说明。
4-phase root cause debugging: understand bugs before fixing.
中文简介正在准备中。当前显示原文说明。
Debug Node.js via --inspect + Chrome DevTools Protocol CLI.
中文简介正在准备中。当前显示原文说明。
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
中文简介正在准备中。当前显示原文说明。
Control Philips Hue lights, scenes, rooms via OpenHue CLI.
中文简介正在准备中。当前显示原文说明。