chore: claude final touches

2026-03-17 18:11:23 +03:00
parent 4b90925c2a
commit 0299949553
21 changed files with 1915 additions and 101 deletions
@@ -0,0 +1,61 @@
+---
+name: codex
+description: "Use the `codex exec` CLI to consult an OpenAI-powered codebase oracle. Trigger this skill whenever Claude Code would benefit from a second opinion on the current codebase — architecture questions, debugging strategies, implementation alternatives, understanding unfamiliar code patterns, or when the user explicitly asks to 'ask codex', 'check with codex', 'consult codex', or 'codex exec'. Also trigger when Claude is uncertain about a complex codebase decision, needs to understand legacy code, or wants to validate an approach before executing. The codex command scans the current codebase and sends context + the question to an OpenAI model, returning an independent analysis."
+---
+
+# Codex — Codebase Oracle via OpenAI
+
+`codex` is a CLI tool that scans the current project and answers questions about it using an OpenAI model. Claude Code can shell out to it for a second perspective.
+
+## Usage
+
+```bash
+codex exec "<your question here>"
+```
+
+The command automatically:
+1. Scans the current working directory for codebase context
+2. Sends the question + context to an OpenAI model
+3. Returns the answer to stdout
+
+## When to use codex
+
+- **Architecture decisions** — "What pattern is this codebase using for state management?"
+- **Debugging help** — "Why might the auth middleware be failing silently?"
+- **Code understanding** — "Explain the data flow in the payments module"
+- **Implementation review** — "What's the best way to add caching to this service?"
+- **Second opinion** — When you want to validate your approach before making changes
+- **Legacy code** — When encountering unfamiliar patterns or undocumented code
+- **User asks directly** — Any time the user says "ask codex" or "check with codex"
+
+## How to call it
+
+Run it as a bash command. The question should be specific and self-contained — codex already has codebase context, so focus the question on what you need to know.
+
+```bash
+# Ask about architecture
+codex exec "What design patterns are used in the src/services directory?"
+
+# Ask for debugging help
+codex exec "The /api/users endpoint returns 500 when called with a missing email field. What could cause this based on the route handler and validation logic?"
+
+# Ask for implementation guidance
+codex exec "What's the best way to add rate limiting to the existing Express middleware chain?"
+```
+
+## Reading the response
+
+The answer comes back as plain text on stdout. Read it, weigh it against your own analysis, and use the best parts. Codex is a consultant, not an authority — if its suggestion conflicts with what you know about the codebase, trust your direct analysis of the code.
+
+## Tips for good questions
+
+- Be specific: "Why does UserService.create() call normalize() twice?" beats "What's wrong with user creation?"
+- Include symptoms when debugging: mention error messages, failing tests, unexpected behavior
+- Scope it: ask about a specific module or file path rather than the entire codebase at once
+- One question at a time: don't bundle multiple unrelated questions into a single exec call
+
+## Requirements
+
+- The `codex` CLI must be installed and on PATH
+- An OpenAI API key must be configured (codex handles this internally)
+- Run from within a project directory so codex can scan the codebase