Menu
Use before proposing cursorAssistant setup, update, or repair — inspect lockfile and managed file drift.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use when running workspace tests, choosing a test command, or summarizing results before handoff to debugger.
Use when running workspace tests, choosing a test command, or summarizing results before handoff to debugger.
Use when: running pre-commit or pre-push CI-equivalent checks in any workspace — discovers workflow commands with Cursor tools, filters for local executability, scopes to staged changes, and runs checks cheapest-first.
Use when the user wants to install or customize cursorAssistant in the current project (GitHub install or configure).
Use when: running pre-commit or pre-push CI-equivalent checks in any workspace — discovers workflow commands with Cursor tools, filters for local executability, scopes to staged changes, and runs checks cheapest-first.
Use when: discovering package manifests, assessing dependency health, finding replacements, or confirming import usage before removal — discovery only; mutating installs are handled by the deps agent.
| name | lifecycleAudit |
| description | Use before proposing cursorAssistant setup, update, or repair — inspect lockfile and managed file drift. |
| disable-model-invocation | true |
| paths | [".cursor/**","AGENTS.md","cursorAssistant.py","template/setup/**"] |
Read-only check of cursorAssistant install state before mutating managed surfaces.
configure, setup, update, or repair on managed Cursor surfacesinstallState or lockfile integrity is unclearpython3 cursorAssistant.py inspect --workspace . --json
python3 cursorAssistant.py plan-setup --workspace . --json
installState | Meaning |
|---|---|
not-installed | No lockfile — run configure (preferred) or setup |
installed | All managed files match package hashes |
needs-update | Stale or missing files — run update |
needs-repair | Lockfile or install integrity issue — run repair |
.cursor/agents, .cursor/skills, .cursor/rules, or .cursor/mcp.json directly when setup/update/repair can apply the change.factory-restore only when the user explicitly wants a full managed-surface reset.inspect JSON reviewed (installState, stale/missing managed files)plan-setup run when proposing install or pack changes.cursor/ when lifecycle can apply the change