Menú
Use when starting any conversation or answering any question about code in this repository - establishes that Cortex context must be consulted before answering, and dispatches to the right Cortex skill for research, impact, and review tasks
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Use when reviewing a changed file, diff, or pull request - retrieves repo-local pattern evidence with Cortex so review feedback follows this repository's conventions before generic best practices
Use when finalizing any code review, pull request, or completed change - runs the Cortex review gates so policy rules and pattern evidence are checked before sign-off
Use when planning a refactor, changing shared code, or making any modification whose blast radius is unclear - maps affected entities and traversal paths with Cortex before the first edit
Use when exploring how something works in this repository, locating an implementation, or answering "how/where does X" questions - retrieves cited Cortex context instead of grepping blindly or answering from memory
Basado en la clasificación ocupacional SOC
| name | using-cortex |
| description | Use when starting any conversation or answering any question about code in this repository - establishes that Cortex context must be consulted before answering, and dispatches to the right Cortex skill for research, impact, and review tasks |
Cortex maintains a local, ranked index of this repository (graph, embeddings, rules). Never answer a code question from memory when Cortex is available.
Before answering any question about this codebase, run:
cortex search "<query>" --json
Cite the entity ids and paths you used. If a command fails because there is
no .context/ directory or no index, say so and suggest cortex bootstrap
(first time) or cortex update (stale index) instead of guessing.
| Situation | Skill / command |
|---|---|
| "How does X work?", exploring code | repo-research skill |
| Planning a refactor or risky change | change-impact skill |
| Reviewing a file or diff | pattern-review skill |
| Finalizing a PR or full review | context-review skill |
| Architectural constraints | cortex rules --json |
| After significant changes | cortex update |
If Cortex MCP tools are connected, context.search, context.get_related,
context.get_rules, context.impact, and context.reload map to the CLI
commands above. Prefer whichever is available; the CLI needs no registration.