Menu
Use when receiving human, automated, GitHub, CodeRabbit, or other review feedback before changing code.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use when preparing local changes, a branch, pull request, merge request, or merge-to-main for final review before publishing, opening a PR, merging, or claiming readiness.
Use when implementing any feature, bugfix, behavior change, or refactor before writing production code.
Use when the user asks to shape fuzzy planning, product/design/engineering tradeoffs, scope/spec/ticket plans, or says "challenge this/help me think"; delegate to an advisor subagent. Good for rough ideas, second opinions, load-bearing decisions, or scope cuts. Skip scoped implementation, narrow bugs, reviews, and "just build" requests.
Use when setting up a project-local eval harness for prompts, agents, judges, RAG, tools, or other LLM behavior, especially when the default should be free/OSS promptfoo with repo-owned artifacts.
Use when a pull request or merge request needs to be driven to merge — watching CI, responding to review feedback, and merging once green and approved, across GitHub, Forgejo, or GitLab.
Use when the user wants repository task tracking, shared agent task state, cross-worktree coordination, tiber setup/install/scaffold guidance, or task create/list/show/prioritize/validate/close workflows. Plugin install and session start are non-mutating; setup integration starts with dry-run previews.
| name | receiving-code-review |
| description | Use when receiving human, automated, GitHub, CodeRabbit, or other review feedback before changing code. |
Review feedback is technical input. Verify it against the codebase, then either implement the correct change or push back with evidence.
| Situation | Response |
|---|---|
| Correct and clear | Make the change and report the concrete fix |
| Ambiguous | Ask the specific clarification before editing |
| Incorrect | Explain the code evidence and propose the safer alternative |
| Conflicts with prior user direction | Stop and ask the user |
| Can't verify cheaply | State what evidence is missing and ask whether to investigate |
For GitHub inline comments, reply in the review thread when responding on the forge. Avoid top-level comments for line-specific review threads.
