Skip to main content
Run any Skill in Manus
with one click
GitHub repository

compartment

compartment contains 12 collected skills from compartmentdev, with repository-level occupation coverage and site-owned skill detail pages.

skills collected
12
Stars
84
updated
2026-05-25
Forks
5
Occupation coverage
2 occupation categories · 100% classified
repository explorer

Skills in this repository

audit-type-ownership
software-developers

Audit type ownership and boundary placement in the compartment repo: misplaced or duplicated types, query/service leaks, root export surface, and phased move plans.

2026-05-25
commit-a-change
software-developers

Prepare a compartment repo commit that matches commitlint type and scope rules and runs through Husky validation.

2026-05-25
compartment-runtime-hygiene
software-developers

Handle export, entrypoint, scaffolding, or deletion changes that can create dead runtime surface or Knip runtime drift in the compartment repo.

2026-05-25
compartment-smoke-test
software-quality-assurance-analysts-and-testers

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.

2026-05-25
develop-a-feature
software-developers

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.

2026-05-25
open-pr-and-monitor
software-developers

Open or reuse a repo PR, then monitor checks, merge readiness, and review feedback until the PR is done, blocked, or redirected.

2026-05-25
preflight-feature-review
software-developers

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.

2026-05-25
public-docs-maintenance
software-developers

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.

2026-05-25
review-a-change
software-quality-assurance-analysts-and-testers

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.

2026-05-25
review-reuse-and-dedup
software-quality-assurance-analysts-and-testers

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.

2026-05-25
ship-a-feature
software-developers

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.

2026-05-25
write-compartment-tests
software-quality-assurance-analysts-and-testers

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.

2026-05-25