write-compartment-tests

Name: write-compartment-tests
Availability: InStock
Author: Compartment

Review and refactor compartment repository tests with harness ownership enforcement.

229|5|Updated May 25, 2026

Search Tags:#automation #refactor #review #tests #harness #test-support

Ready to run

npx skills add https://github.com/compartmentdev/compartment --skill write-compartment-tests

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-compartment-tests
Source: https://github.com/compartmentdev/compartment/tree/main/.codex/skills/write-compartment-tests
Command: npx skills add https://github.com/compartmentdev/compartment --skill write-compartment-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit and improve tests in the repository by enforcing fast, ownership-aligned review workflows.

Core Features & Use Cases

Fast review passes with a dedicated fast subagent when policy allows.
Clear ownership and harness prep across packages; guardrails against test-mirror code.
Cross-package fixture auditing and test boundary enforcement.

Quick Start

Start a fast test-review pass on the repository’s tests using this skill.

Frequently Asked Questions about write-compartment-tests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate test review and refactor workflows to prevent implementation-mirror tests?▼

Automate test review and refactor workflows by running fast subagent passes that enforce test quality, audit fixtures, and prohibit implementation-mirror tests. This coordinates ownership-aligned harness selection across packages while preserving cross-package boundaries.

What is the best way to enforce cross-package boundaries during a repository test audit?▼

Enforce cross-package boundaries during a test audit by applying ownership-aligned workflows that audit fixtures and select appropriate test harnesses. This ensures tests remain isolated and ownership is clearly distributed across the affected packages.

How do I safely remove or modify existing tests without breaking repository behavior?▼

Safely modify or remove tests by using a fast subagent review pass that enforces test quality and fixture audits. This protects existing behavior by verifying harness ownership and preventing tests that mirror implementation details.

Does this test review process work when adding new tests across multiple packages?▼

Yes, this test review process works when adding, modifying, or removing tests across multiple packages. It coordinates fast subagent passes when policy allows, enforcing cross-package boundaries and clear harness ownership throughout the workflow.

Why should I avoid implementation-mirror tests when refactoring test harnesses?▼

Avoid implementation-mirror tests when refactoring harnesses because they couple test assertions to internal code structure rather than behavior. Enforcing this prohibition during fixture audits protects against brittle tests that break during harmless internal changes.

When should I not use a fast subagent pass for test reviews?▼

You should not use a fast subagent pass for test reviews when repository policy does not allow it. The workflow only coordinates fast passes under permitted conditions, reverting to standard review enforcement to maintain test quality and boundary integrity.