refactor(skills): EN thin wrappers + shared common, discovery section

This commit is contained in:
admin committed 2026-09-01 00:24:21 +00:00
1 parent 66048fd74c
commit 3289804909
4 files changed
+30 -102

No files matched your search

+6 -37
View File
@@ -1,45 +1,14 @@
---
name: codex-review
description: Code review by Codex — branch, commit, uncommitted changes, or arbitrary files. Use when user says «ревью у кодекса», «пусть codex посмотрит ветку/коммит/файл», "codex review", "second reviewer".
description: Code review via Codex — branch, commit, uncommitted, or files. Use when user says "codex review", "review this branch/commit".
---
# Review via Codex
Spawn the `codex` subagent. The scope sets the mode:
Spawn the `codex` subagent. Scope via `review scope:` (see `../references/common.md` for transport).
- branch vs base: `review scope: --base main`
- single commit: `review scope: --commit <sha>`
- uncommitted: `review scope: --uncommitted`
- arbitrary files / abstract scope: WITHOUT `review scope:` — a plain task
"review files X, Y and their dependents".
- `review scope: --base main` | `--commit <sha>` | `--uncommitted` | (no scope = plain task "review files X, Y")
- Include `cwd:` and `=== TASK FOR CODEX ===`.
- Focus/format inside block: `file:line — 🔴|🟡|🔵 — problem — fix`.
## Subagent prompt — required parts
- First line — framing for the wrapper: "You are a wrapper around the codex
CLI: do not solve the task yourself, launch codex and return its answer +
thread_id".
- `cwd: <absolute repo path>` (review works from cwd)
- `review scope: ...` (if applicable)
- Focus and format — in a block between markers `=== TASK FOR CODEX ===` and
`=== END TASK ===`:
- Focus, if any: security / performance / correctness / everything.
- Findings format: `file:line — 🔴|🟡|🔵 — problem — suggested fix`, no
praise, no code retelling.
## Example
```
You are a wrapper around the codex CLI: do not solve the task yourself, launch codex and return its answer + thread_id.
cwd: /abs/path/to/repo
review scope: --base main
=== TASK FOR CODEX ===
Focus: correctness and security.
Findings format: file:line — 🔴|🟡|🔵 — problem — fix. No praise.
=== END TASK ===
```
## After
- Hand the findings to the user / process per the task.
- Contested finding → SendMessage to the same session: ask to justify or
show a repro. Don't silently accept or reject.
Contested finding → SendMessage to same session, don't silently accept.