cordis-styling-nitpickinglisted
Install: claude install-skill SOYL-AI/soyl-skills-hub
# Cordis Ownership and Lifecycle Audit
This is a focused semantic review of Cordis ownership and lifecycle. Start a repository audit from exported plugin entrypoints (`apply` or a concrete default export invoked by Cordis), then trace module initialization, registered services, listeners, effects, disposers, and transitive calls reachable from those roots. Exclude unrelated helpers, build tools, CLI paths, and tests as finding targets. Read tests and vendored Cordis to establish behavior; report a generated defect against its owning source. Do not report defects in vendored code under this skill.
## Sources of truth
- [Repository conventions](../../../AGENTS.md): Cordis ownership requirements.
- [Lifecycle and effects](../../../docs/cordis-tutorial/02-lifecycle-and-effects.md): effect acquisition and disposal.
- [Services](../../../docs/cordis-tutorial/03-services.md): dependency tracking and service availability.
- [Defensive patterns](../../../docs/defensive-patterns/general.md): quiescent teardown and required completion listeners.
## Review workflow
1. Locate mutable owners, registrations, resource acquisition, and work admission reachable from the requested plugin roots. For large scopes, use independent directory scans, then consolidate findings involving the same consumer and resource.
2. Trace ownership through the actual context: in a traceable service method, `this.ctx` is the caller's context. Identify who owns each effect and the disposer that releases it.
3.