con un clic
compartment
compartment contiene 12 skills recopiladas de compartmentdev, con cobertura ocupacional por repositorio y páginas de detalle dentro del sitio.
Skills en este repositorio
Audit type ownership and boundary placement in the compartment repo: misplaced or duplicated types, query/service leaks, root export surface, and phased move plans.
Prepare a compartment repo commit that matches commitlint type and scope rules and runs through Husky validation.
Handle export, entrypoint, scaffolding, or deletion changes that can create dead runtime surface or Knip runtime drift in the compartment repo.
Run or delegate a browser-first smoke test of the local compartment through browser-use as a real user: boot or reuse the local stack, install or log in, deploy the repo smoke fixtures, verify CLI status/logs, and exercise protected app login/logout flows.
Implement repo changes by starting with a required preflight subagent, then editing the smallest owning surface on one canonical path and running only diff-triggered checks.
Open or reuse a repo PR, then monitor checks, merge readiness, and review feedback until the PR is done, blocked, or redirected.
Run a required subagent preflight before implementation and return a short coding brief: where to edit, what to avoid, what lint or runtime traps matter, and what to validate.
Maintain the public Starlight docs site for material changes to shipped Compartment workflows, using generated reference where possible and concise task- and decision-focused guides elsewhere.
Use when the user invokes $review-a-change or asks for a compartment repo code review; always use the delegated subagent review path by splitting review into separate parallel passes for contracts, architecture, runtime surface, validation, and changed slices, then report findings first with file and line references.
Use when reviewing compartment repo changes for existing helper reuse, extractable pure utilities, duplicated logic, repeated constants, hardcoded values, or repeated variable derivations that should be simplified in the owning package or packages/utils.
Carry an approved repo change from request to terminal PR outcome by orchestrating preflight, implementation, review, smoke, commit, and PR monitoring through the repo subagent stages without duplicating those skills.
Review, write, or refactor compartment repo tests by starting with a fast independent test-review pass, protecting behavior, using the right package-owned harness, and refusing implementation-mirror tests.