// Extend or audit Codex support in the EstateWise repository. Use when changing .codex config, .codex/rules, .agents/skills, AGENTS.md layering, multi-agent roles, project guidance discovery, or Codex-specific documentation and workflows.
| name | estatewise-codex-support |
| description | Extend or audit Codex support in the EstateWise repository. Use when changing .codex config, .codex/rules, .agents/skills, AGENTS.md layering, multi-agent roles, project guidance discovery, or Codex-specific documentation and workflows. |
Use this skill when the task is about Codex itself in this repository rather than product code.
AGENTS.mdAGENTS.md files under repo subdirectories.agents/skills/.codex/config.toml.codex/agents/*.toml.codex/rules/*.rulesRead references/codex-extension-checklist.md when the change spans more than one of these surfaces.
AGENTS.md repository-wide and stable.AGENTS.md files close to the owning package.agents/openai.yaml for UI metadata and invocation policy rather than bloating SKILL.md.references/.For each new or updated skill:
name and description only.agents/openai.yaml with:
interface.display_nameinterface.short_descriptioninterface.default_promptpolicy.allow_implicit_invocationreferences/ only when the extra material is genuinely needed later.When adding nested AGENTS.md files:
When adding .codex/rules/*.rules:
prompt for risky command families with legitimate uses.forbidden only when the alternative is clear and the project truly never wants the command.match and not_match examples to catch mistakes.bash -lc.After editing Codex support files:
AGENTS.md, skill, config, and rules files for conflicts.git diff --check.Update these when Codex support changes:
.agents/README.md.codex/README.mdREADME.md only if repository-wide contributor workflow materially changedWork on EstateWise MCP, agentic-ai, web-grounding, token flows, and A2A integrations. Use when changing tool behavior, orchestration, runtime flags, MCP wrappers, HTTP/A2A endpoints, or AI integration paths.
Audit producer-consumer alignment in EstateWise when REST, tRPC, MCP, gRPC, A2A, or shared payloads may have changed. Use when one package's change could silently break another package, tool, or doc set.
Execute production-safe code changes in the EstateWise monorepo. Use when implementing or fixing behavior in backend, frontend, MCP, agentic-ai, gRPC, deployment-control, tests, or repo docs. Do not use for pure brainstorming, skill installation, or work outside this repository.
Run or debug the EstateWise local environment. Use when setting up services, choosing the smallest service combination, checking local endpoints, or troubleshooting environment/config issues. Do not use for routine code implementation unless local run/debugging is the main task.
Work on EstateWise deployment-control, Docker, Kubernetes, Helm, Terraform, Jenkins, and cloud deployment assets. Use for infrastructure and operational workflow changes, not ordinary application feature work.
Review EstateWise changes for correctness, regressions, security issues, contract mismatches, operational risk, and missing tests. Use for PR review, diff review, bug hunts, and branch-vs-main analysis. Do not use for implementation tasks unless the user asks for fixes after findings are reported.