القائمة
Run only the upstream-features lens from the improve workflow on a target file, directory, or glob, producing read-only findings about useful built-in capabilities the target is not using.
التثبيت باستخدام 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 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.
Run only the security and threat-model lens from the improve workflow on a target file, directory, or glob, producing read-only adversarial findings.
| name | improve-upstream |
| description | Run only the upstream-features lens from the improve workflow on a target file, directory, or glob, producing read-only findings about useful built-in capabilities the target is not using. |
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 useful capabilities in tools, libraries, and config formats the target already invokes or depends on but does not use.
First enumerate every external program, library, and configuration file format the target invokes or depends on. For each command, read its man page with man <cmd>. For each config file format, read the format man page, such as man 5 sshd_config. Use --help or -h only as a supplement. If no man page exists, do focused research in official documentation.
Report only features that would simplify, harden, or extend this specific target in a concrete way:
For each finding, include the feature, why it helps this target, and a concise citation such as a man page section or official URL.
Stay in this lane: add capabilities of already-used or built-in tools. Do not propose broad restructuring, threat-modeling, or peer-project conventions.
