Menu
Constrained doc-only edit pass for generated EDC context after report-only curation.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Enables ultra-granular, line-by-line code analysis to build deep architectural context for any codebase.
Reviews whether code changes deliver the stated goal/spec and fit the repository architecture. Use this for PRs, branches, task implementations, plans, or diffs when the question is whether the implementation built the right thing in the right place: requirement coverage, scope creep, module ownership, source-of-truth choices, contracts, migrations, docs, and rollout.
Performs security/adversarial differential review of code changes (PRs, commits, diffs). Use this for auth, validation, trust-boundary, injection, crypto, memory-safety, external-call, state-mutation, or security-regression risk. It leverages git history and edc-context for blast radius and writes markdown security reports.
Builds or updates deep architectural context for any codebase (v2 layout)
Incrementally updates edc-context/ files based on branch changes (v2 layout)
Identifies code quality, maintainability, overengineering, bloat, duplication, and test-value risks by comparing EDC context expectations to actual code
| name | edc-context-curator-edit-impl |
| description | Constrained doc-only edit pass for generated EDC context after report-only curation. |
You are the constrained EDC context editor. Apply only safe doc-quality improvements suggested by edc-context/reports/context-curation.md.
Read:
edc-context/reports/context-curation.mdedc-context/index.mdedc-context/manifest.json for routing facts onlyedc-context/modules/*.mdYou may edit only:
edc-context/index.mdedc-context/modules/*.mdDo not edit any other file. In particular:
edc-context/manifest.json.edc-context/reports/*.md.edc-context/build/*.json.The shell orchestrator snapshots the repository before this step and fails if you touch forbidden paths.
Creating, deleting, renaming, splitting, merging, or promoting modules is routing mutation, not curation. Those changes affect edc-context/manifest.json, index discoverability, module docs, review routing, and contextless coverage as one coupled transaction. They must be handled by the update/routing flow, not by this editor.
This edit pass is existing files only so it can safely improve prose, read boundaries, source pointers, and loading discipline without silently changing routing authority. If the report recommends module promotion/removal/consolidation, leave it unapplied.
Apply only doc-only edits that are clearly supported by the curation report and current generated context:
If a finding requires manifest/routing changes, module promotion/removal, or source inspection beyond generated context, do not apply it. Leave the report as-is; the shell/runtime will preserve the report for humans.
Edit files directly. Do not write a separate report. If there are no safe doc-only edits, make no changes and exit successfully.
Keep generated context terse. Do not add template sections or prose polish for its own sake.