19.9K skills · sorted by relevance
Switch Codex from Weave Router back to its default provider without logging out or deleting the router configuration. The change applies the next time Codex starts and can be reversed with `$router-on`.
Contribute a verified bug fix for LazyCodex, lazycodex-ai, omo-codex, bundled Codex skills, or upstream Codex CLI bugs. Opens a fork PR only for upstream openai/codex; LazyCodex-owned defects become a verified-fix issue on code-yeongyu/lazycodex (never a PR — that repo is a generated distribution mirror). Use when the user asks to fix a bug, contribute a bug fix, contribute to fix bug, open a PR for a bug, or debug and PR a LazyCodex/Codex defect.
The English summary is being prepared. Showing the original description.
[omh] Outdated code index or codemap: refresh local code intelligence, summarize repo structure, and prepare task-scoped codegraph handoff context without overclaiming execution. Use when the user says: codegraph-refresh, codegraph refresh, refresh codegraph, update codegraph, codegraph stale, stale codegraph, codegraph handoff, codegraph summary.
The English summary is being prepared. Showing the original description.
SUPERSEDED by /claudex-loop (formerly /crucible; adds a Phase 0 research/recon pass + rebuilt interview) — prefer that skill unless you explicitly want this one. Two-act plan hardening. ACT 1 (you ↔ Claude) — Claude interviews you relentlessly about a plan or design, one question at a time, recommending an answer for each and exploring the codebase when it can answer itself, until every branch of the decision tree is resolved. ACT 2 (Claude ↔ Codex) — Claude writes the locked plan to PLAN.md and OpenAI Codex adversarially reviews it in a read-only sandbox (VERDICT:APPROVED/REVISE), Claude revises and re-submits to the SAME Codex session until APPROVED or a MAX_ROUNDS cap, then you sign off before any code. Use when the user says "/grill-me-codex", "grill me then have codex review", "grill me and stress-test the plan", "interview me about this plan then get a second model on it", or is about to build something high-stakes (auth, schema, concurrency, migrations, payments) and wants both alignment AND a cross-model sanity check before implementation. Builds on Matt Pocock's grill-me (MIT). For the docs-aware variant use /grill-with-docs-codex; if you already have a plan and want only the Codex review use /codex-review. NOT for reviewing already-written code (use /codex:review) and NOT for trivial changes.
The English summary is being prepared. Showing the original description.
Configures CI/CD pipelines using AWS CodePipeline, CodeBuild, CodeDeploy, CodeConnections, and CodeArtifact. Covers CodePipeline V2 (triggers, variables, execution modes, cross-account), buildspec.yml (caching, VPC, Docker), CodeDeploy strategies (blue/green, canary, linear), CodeArtifact (private package registries, auth tokens, cross-account), and source connections (GitHub, GitLab, Bitbucket). Applies when CodePipeline, CodeBuild, CodeDeploy, CodeConnections, CodeArtifact, buildspec.yml, appspec.yml, or CI/CD pipeline orchestration is referenced. Does NOT cover: ECS Fargate services or task definitions (use aws-containers), CDK Pipelines or cdk deploy (use aws-cdk), sam deploy (use aws-serverless), Amplify deployments (use aws-amplify), or GitHub Actions/GitLab CI.
The English summary is being prepared. Showing the original description.
Safely change and test untested codebases using Feathers' "Working Effectively with Legacy Code". Use when the user mentions "legacy code", "no tests", "untested codebase", "how do I test this", "seams", "characterization tests", "golden master", "sprout method", "afraid to change this code", "monster method", "dependency breaking", or "inherited a messy codebase". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout/wrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.
The English summary is being prepared. Showing the original description.
codex exec review を基本に、必要なら codex exec を使ってコード変更のレビューを依頼し、指摘事項を報告する。通常 / 厳しめ (--strict) / 敵対的 (--adversarial、実装を壊しにいく red team) の 3 モードを持つ。「codexでレビューして」「codex-review」「/codex-review」「敵対的にレビューして」で発火。Codex 単体での単独レビュー用途。複数エージェント並行レビューは cross-review、差分ではなくコードベース全体の監査は audit を使う。
The English summary is being prepared. Showing the original description.
Create an SVG usage card from local Claude Code, Codex, Gemini CLI, and OpenCode logs. It summarizes token counts, equivalent API cost, consecutive activity days, and each agent's share for inclusion in a README or documentation.
Create icon assets for iOS and macOS projects using SF Symbols or Iconify API. Match existing colors and sizes, then generate PNG files at three resolutions with the metadata needed for Xcode asset catalogs.
Analyze Claude Code and Codex usage logs to identify spending drivers, including cache usage, model choices, reasoning, and long sessions. Receive evidence-backed recommendations and hypothetical savings estimates to help decide which changes to try.
Coordinates a named team of Codex workers with concrete responsibilities and shared progress records. It selects available collaboration tools, manages communication and separate working copies when needed, and handles integration, team archival, and cleanup after the work ends.
Delegate a clearly scoped repository task to Kimi Code without opening its interactive interface. The skill reads structured execution events, extracts the final response, and checks for errors, with separate handling for read-only work and authorized changes.
Create a Power Apps Code App starter project with React and TypeScript. Set up development tools, authentication, connector examples, and deployment scripts, with documentation covering local development and Power Platform configuration.
Get answers about Qwen Code usage, features, configuration, and troubleshooting from its official documentation. The skill also helps inspect and edit user or project settings files when configuration changes are requested.
Set up zvec-grep (zg) for use with Qwen Code. Check existing installation and settings, explain the integration changes, and request approval before installing the package and registering it with Qwen Code.
Read provider usage, limits, credits, and installation or configuration health through CodexBar. Returns JSON for enabled providers or a selected provider, while hiding secrets and leaving configuration and authentication unchanged.
Check active PUA agents and teams from Codex CLI using an alias for the Claude Code status command. Review process IDs and record lifetimes when available, alongside stale records.
Find available Codex skills in a curated list and install them by name or GitHub path. Supports multiple skills in one run, custom destinations, and private repositories using available credentials.
Compare the installed Claude Code version with release notes and recent bug reports to decide whether to stay, update, or use a specific version. Recommendations account for reported problems, relevant fixes, and how Claude Code was installed.
Connect static analysis results and human audit notes to a Trailmark code graph. Group findings by severity and compare them with input flow, impact, and privilege boundaries to prioritize investigation and understand findings in their code context.
Scans code for security vulnerabilities with CodeQL by tracing data across functions. Builds and checks analysis databases, models project-specific APIs, and saves findings in SARIF, a structured results format, with broad or focused scan options.
Get independent code reviews of uncommitted changes, branch differences, or individual commits using Codex or Antigravity. Receive findings with severity, locations, impact, and suggested corrections, and compare where the two reviewers agree or differ.
Create an isolated development container configured for Claude Code and the project's languages. Generate container files, editor settings, dependency setup commands, and persistent storage for Python, Node/TypeScript, Rust, and Go projects.
Create an OpenCode plugin for iPolloWork with custom tools and hooks, which run code at specific events. The skill builds the TypeScript file and adds it to the configuration so it can load after a session restart.