메뉴
Run only the prior-art and convention lens from the improve workflow on a target file, directory, or glob, producing read-only findings based on mature implementations and local sibling patterns.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Review-first aggressive code simplification for a target file, directory, or glob, producing numbered findings and applying only user-selected changes.
Ask the other coding agent (Claude ↔ Codex) to review the relevant changes
Split a multi-finding worktree into per-finding commits via non-interactive `git add -p`. Use when an `/improve` or `/review` pass has edited several distinct findings into the worktree together and they need to land as separate commits. Refuses to run on secret-rendering templates.
Run only the first-principles analysis lens from the improve workflow on a target file, directory, or glob, producing read-only findings without applying edits.
Run only the security and threat-model lens from the improve workflow on a target file, directory, or glob, producing read-only adversarial findings.
Run only the radical-simplification lens from the improve workflow on a target file, directory, or glob, producing read-only findings about subtractive or restructuring improvements.
| name | improve-prior-art |
| description | Run only the prior-art and convention lens from the improve workflow on a target file, directory, or glob, producing read-only findings based on mature implementations and local sibling patterns. |
Read ../improve/references/target-and-agent-contract.md first.
When called directly, resolve the target and build the context brief from the shared contract. When called by $improve, use the provided target paths, usage scenarios, target summary, test-file flag, and optional <user_note>.
Stay read-only. Return findings using the unified return contract.
Identify how the same problem is solved elsewhere and report specific patterns this target should adopt.
Find 1-3 mature, well-regarded implementations of the same job. These may be open-source tools, standard library modules, or established patterns in the language or ecosystem. Read enough to understand the shape of the solution, not just its existence.
If the target sits inside a larger repository, also scan sibling code that solves similar problems. Flag inconsistencies in style, error handling, configuration, or interfaces that the target should plausibly match.
Report specific patterns or idioms:
For each finding, cite the prior art with a file path or URL and explain why it fits this target. Skip generic "follow conventions" advice.
Stay in this lane: concrete patterns from peer projects or local siblings. Do not threat-model, simplify, or enumerate upstream flags as the main argument.
