「codex review」の検索結果

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

日本語の概要は準備中です。原文の説明を表示しています。

Use when changing an existing ChatGPT pet or Codex pet sprite sheet with Scenario: fixing a broken row, frame, jump or edge, regenerating one animation state, adding the sixteen look directions to a 1536x1872 v1 sheet, giving the pet a new outfit, color or accessory, renaming it in its pet.json, or checking a pet sheet and previewing it as an animated GIF.

日本語の概要は準備中です。原文の説明を表示しています。

Modern, interactive alternative to `/do` — clarify intent up front, then take a task end-to-end with a serial AI review gauntlet (lens debate (lowy ⇄ hickey) → codex debate → simplify → code-police, each editing the branch in turn) → CI → evidence. ONLY invoke when the user explicitly types `/be` or `$be`; never auto-select from a natural-language request.

日本語の概要は準備中です。原文の説明を表示しています。

Use when Codex is building or iterating on a web game (HTML/JS) and needs a reliable development + testing loop: implement small changes, run a Playwright-based test script with short input bursts and intentional pauses, inspect screenshots/text, and review console errors with render_game_to_text.

日本語の概要は準備中です。原文の説明を表示しています。

Score a repository's agentic legibility from repo-visible evidence only. Use when Codex needs to audit how easy a codebase is for coding agents to discover, bootstrap, validate, and navigate, especially for harness-engineering reviews, developer-experience audits, repo cleanup, or before/after comparisons after improving docs, tooling, or architectural constraints.

日本語の概要は準備中です。原文の説明を表示しています。

Design, evaluate, implement, or review image and video generation connectors for Timeline Studio. Use when adding a provider plugin, extracting the generation plugin host or registry, or checking a connector against Timeline Studio's authentication, output, localization, and My assets contract. Do not use for ordinary video editing or Codex plugin packaging.

日本語の概要は準備中です。原文の説明を表示しています。

Local SEO analysis covering Google Business Profile optimization, NAP consistency, citation health, review signals, local schema markup, location page quality, multi-location SEO, and industry-specific recommendations. Detects business type (brick-and-mortar, SAB, hybrid) and industry vertical (restaurant, healthcare, legal, home services, real estate, automotive). Use when user says "local SEO", "Google Business Profile", "GBP", "map pack", "local pack", "citations", "NAP consistency", "local rankings", "service area", "multi-location", or "local search".

日本語の概要は準備中です。原文の説明を表示しています。

Deep single-page SEO analysis covering on-page elements, content quality, technical meta tags, schema, images, and performance. Use when user says "analyze this page", "check page SEO", "single URL", "check this page", "page analysis", or provides a single URL for review.

日本語の概要は準備中です。原文の説明を表示しています。

Full website SEO audit with parallel subagent delegation. Crawls up to 500 pages, detects business type, delegates to up to 15 specialists (8 always + 7 conditional), generates health score. Use when user says audit, full SEO check, SEO best-practice review, analyze my site, website health check, or find SEO issues.

日本語の概要は準備中です。原文の説明を表示しています。

Audit and improve the prompt surface of Avibe Agents across backends (Claude, Codex/GPT, OpenCode) — global and project rules, Agent system prompts, Skills, delegation briefs, and Task and Watch messages — using real run evidence. Use when an Agent misbehaves (stalls, over-asks, over-reaches, ignores or over-applies a rule), after a model or backend change, or when the user asks to review, clean up, or tighten prompts.

日本語の概要は準備中です。原文の説明を表示しています。

Deliver implementation PRs across Avibe, avibe-backend, avibe-docs, avault, and vault-sandbox. Required for branch and scope discipline, Codex review, CI, circuit breaking, and user-facing close-out, regardless of agent backend.

日本語の概要は準備中です。原文の説明を表示しています。

Generate or refresh a STRIDE-based threat model for the current repository using Bug Hunter-native artifacts. Use whenever the repository has no threat model yet, the architecture changed materially, a security review needs fresh trust-boundary context, or the user explicitly asks for a threat model.

日本語の概要は準備中です。原文の説明を表示しています。

Surgical code fixer for Bug Hunter. Implements minimal, precise fixes for verified bugs. Uses doc-lookup (Context Hub + Context7) to verify correct API usage in patches. Respects fix strategy classifications (safe-autofix vs manual-review vs larger-refactor).

日本語の概要は準備中です。原文の説明を表示しています。

Adversarial code reviewer for Bug Hunter. Rigorously challenges each reported bug to determine if it's real or a false positive. Uses doc-lookup (Context Hub + Context7) to verify framework claims before disproval. The immune system that kills false positives.

日本語の概要は準備中です。原文の説明を表示しています。

Sets up how you and your team build and work with AI agents, and produces an Agent Workflow Charter (agent lanes, plan-mode loop, autonomy ladder with promotion criteria, rules file, review policy, security rules, rollout plan). Use when you ask 'how should we work with Claude Code / Codex / Cursor', 'how many agents should I run', 'should the agent be autonomous', 'plan mode', 'CLAUDE.md', 'AI-native team', 'roll out AI to my team', or 'my agent keeps screwing up'. Draws on 110 Lenny's Podcast guests incl. Claire Vo, Boris Cherny and Aishwarya Naresh Reganti.

日本語の概要は準備中です。原文の説明を表示しています。

Summarize, organize, and normalize messy research materials into an IEEE-ready writing brief before manuscript drafting. Use when Codex needs to process a folder or collection of experiment logs, code files, AI chat exports, idea notes, literature summaries, related-work notes, copied introduction excerpts, Zotero-derived paper summaries, tables, figures, or scattered Markdown/text records and convert them into structured inputs for ieee-writing, ieee-experiment, ieee-citation, ieee-reviewer, or ieee-response.

日本語の概要は準備中です。原文の説明を表示しています。

Create game-ready fixed-cell pixel-art character spritesheets from text concepts, reference images, or existing character art. Use when Codex needs to design, generate, clean up, validate, and package 2D game characters with native 32x32, 64x64, or 128x128 cells; 4-way or 8-way directions; idle, walk/run, jump, attack, archer, caster, or other animation strips; transparent GIF/WebP previews; and per-direction targeted regeneration.

日本語の概要は準備中です。原文の説明を表示しています。

Secure AI coding agents (Claude Code, Cursor, Codex, Copilot) with permission boundaries, secret protection, code review gates, and safe sandbox configurations for team environments.

日本語の概要は準備中です。原文の説明を表示しています。

Carry out a released charter to a proven result: plan only as much as the work needs, do the work through the project's own workers, prove every success check with a recorded real run, get one independent review, and close honestly. Invoke explicitly as `$deliver <charter>` (Codex) or `/deliver <charter>` (Claude, Cursor), or the way your agent invokes a skill, or when a dispatch names you the executor of a charter.

日本語の概要は準備中です。原文の説明を表示しています。

Learn daily from this machine's Claude Code, Codex, Hermes, OpenClaw and Cursor sessions. Review skill changes and lessons with accept/reject/tbd; recall lessons at session start.

日本語の概要は準備中です。原文の説明を表示しています。

Use when reviewing what was learned after debugging, workaround discovery, or trial-and-error investigation, and capture it as a dated journal entry under ~/.codex/journal

日本語の概要は準備中です。原文の説明を表示しています。

Apply Andrej Karpathy-inspired coding-agent guidelines in Codex. Use when writing, reviewing, debugging, or refactoring code to surface assumptions, avoid overengineering, keep edits surgical, and define verifiable success criteria.

日本語の概要は準備中です。原文の説明を表示しています。

Delegate bounded tasks to Grok Build from a supervising agent such as Codex. Use when the user asks Grok to investigate, review, implement, or provide another perspective, or when a distinct coding agent would materially help. Includes a background ACP client for progress, follow-up prompts, permissions, and cancellation.

日本語の概要は準備中です。原文の説明を表示しています。

Implement or refactor Formax tool transcript UI using the Tool UI Blocks (C-lite) pattern (ToolUiBlocks renderer + blocks presenters) to avoid touching many tool presenter files; use when adjusting ⏺/⎿ spacing, indent rules, or migrating additional tools to blocks presenters with targeted Ink/Vitest tests and Codex review before commit.

日本語の概要は準備中です。原文の説明を表示しています。