Coding standards, frameworks, refactoring, and code review (16.9K skills)
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.
The English summary is being prepared. Showing the original description.
Pushing GitHub Actions changes, resolving push rejection, requesting upload exceptions.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Run a final code review on a pull request
The English summary is being prepared. Showing the original description.
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).
The English summary is being prepared. Showing the original description.
Change size guidance (800 lines)
The English summary is being prepared. Showing the original description.
Breaking changes
The English summary is being prepared. Showing the original description.
Update the title and body of one or more pull requests.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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".
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
The English summary is being prepared. Showing the original description.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
The English summary is being prepared. Showing the original description.
4-phase root cause debugging: understand bugs before fixing.
The English summary is being prepared. Showing the original description.
Debug Node.js via --inspect + Chrome DevTools Protocol CLI.
The English summary is being prepared. Showing the original description.
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
The English summary is being prepared. Showing the original description.
Control Philips Hue lights, scenes, rooms via OpenHue CLI.
The English summary is being prepared. Showing the original description.