メニュー
Use for ecp command and workflow reference. Start here for command selection, help routing, and links into the detailed guides.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | ecp |
| description | Use for ecp command and workflow reference. Start here for command selection, help routing, and links into the detailed guides. |
This is the single entry point for the Codex-facing ecp skill set.
When you need to use ecp, do not guess from memory. First identify the task category, then open the matching guide.
These rules apply to every ecp task.
ecp --help is the top-level command map.
ecp admin --help is the admin subcommand map.
Do not treat ecp admin as a help command; it launches the interactive TUI by default.
If a task can be answered by the top-level help or a single subcommand help page, use that before reading any broader reference.
Command syntax, review workflows, and broader repository guidance should live in separate guides instead of one large doc.
| If you need... | Open guide |
|---|---|
| Command names, flags, output formats, or admin subcommands | guides/command-reference.md |
| Change review workflow for changed files | ../simplify/SKILL.md |
If you are unsure which command to use, start with
ecp --help, then open the matching guide.
These are support files, not entry points.
guides/ — detailed command and workflow references../simplify/SKILL.md — graph-aware review workflow built on top of ecpIf you find yourself reading every file under skill_sample/codex/ for one task, you skipped Layer 2.
Review changed code for bugs, reuse, quality, and efficiency, then fix any issues found. Dispatch is tiered by diff size — small diffs get a single-pass self-review (zero agents), only large or risky diffs fan out to parallel agents. Reviewers leverage ecp first (when the repo is indexed) for graph-aware context.
Symbol-level code analysis, blast-radius impact, cross-repo API contracts, AST-aware rename, route map. Defer to grep for string literals, config keys, vendored/generated code, fs layout.
Review changed code for reuse, quality, and efficiency, then fix any issues found. Each review agent leverages `ecp` first (when the repo is indexed) so it has graph-aware context — changed files, impact, blind spots, egress, shape drift, and resolver deltas — before reading raw diffs.
Personalized install + config wizard for egent-code-plexus. Walks the user from "no ecp installed" → "ecp ready + indexed + agent integrated (native else MCP) + next steps".
When you want to explore code structure — where a symbol is defined, who calls it, a refactor's blast radius, routes/contracts, or to trace how code connects — reach here before grep or an Explore agent. Verb by question: where→find, who-calls/blast-radius→impact, full-context→inspect, where-a-filename-is-read-vs-written→impact --literal, routes/contracts→those, trace-flow→processes, graph-question-with-no-verb (orphans, all-impls)→cypher. Grep only for non-code text: config values, log strings, fs layout.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when building web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.