القائمة
Deep-dive into complex code using Codex CLI. Traces call chains, maps dependencies, and explains how code works. Use when asked to understand, unwind, or explain tangled or unfamiliar code.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Transcribe audio files to text using mlx_whisper on Apple Silicon. Use when the user has an audio file (MP3, WAV, AAC, OGG, etc.) they want transcribed.
Run consistent, findings-first code reviews with Codex CLI for any target: uncommitted/dirty working tree, current branch vs base branch, specific commit SHA, or pull request. Use when asked to review bugs, risks, regressions, and test gaps with actionable file/line findings.
Use Codex CLI to diagnose and fix a bug, error, or failing test. Use when you want a second opinion on a bug or when Claude's fix isn't working.
Use Codex CLI to refactor a module, file, or code pattern. Use when you want an independent take on how to restructure complex or tangled code.
| name | explain |
| description | Deep-dive into complex code using Codex CLI. Traces call chains, maps dependencies, and explains how code works. Use when asked to understand, unwind, or explain tangled or unfamiliar code. |
Use Codex CLI to do a thorough, read-only deep-dive into code and report back a clear explanation.
From the user's request, construct a focused prompt for Codex. The prompt should ask Codex to:
Include the target (file path, function name, module, or concept) in the prompt.
codex --sandbox read-only -a never exec "$PROMPT"
Do not use | tee unless the output is likely to be very large.
Structure the explanation as:
Keep it concrete. Reference specific files and lines, not abstract descriptions.