Menu
Organize tests by isolation requirements, adhering to PTY conventions and subprocess isolation patterns.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Run comprehensive Rust code quality checks including compilation, linting, documentation, and tests. Use after completing code changes and before creating commits.
Enforce the "Clean Imports over Inline Absolute Paths" rule by removing inline crate:: prefixes and adding proper use statements.
Rules and guidelines for creating well-formatted commit messages, including 72-char limits, scope prefixes, and trailer blocks for tasks, PR closing, and attribution.
Zero-allocation string building strategies. Use when formatting strings, generating ANSI codes, or writing hot loops to avoid heap allocations and Formatter state machine overhead.
Run clippy linting, enforce comment punctuation rules, format code with cargo fmt, and verify module organization patterns. Use after code changes and before creating commits.
Standard for writing structured tracing logs behind debug flags.
| name | organize-tests |
| description | Organize tests by isolation requirements, adhering to PTY conventions and subprocess isolation patterns. |
// Copyright (c) 2025 R3BL LLC. Licensed under Apache License, Version 2.0.
Organize tests by isolation requirements, adhering to PTY conventions and subprocess isolation patterns.
Choose the correct directory based on why the test needs isolation. This maintains low cognitive load for future developers.
See Taxonomy for directory details.
PTY tests are complex and prone to deadlocks (especially on macOS). Strict adherence to naming, documentation, and resource management is mandatory.
See PTY Conventions for details.
Tests that pollute global mock state (e.g., static Mutexes) must be isolated into a single subprocess and run sequentially.
See Examples for macro usage.
Always ensure test modules are visible for both tests and documentation using #[cfg(any(test, doc))].
#[cfg(any(test, doc))]
pub mod unit_tests;
#[cfg(any(test, doc))]
pub mod process_isolated_tests;
#[cfg(any(test, doc))]
pub mod my_module_integration_tests;
organize-modules: Use for general module structure and re-exports.write-documentation: Use for formatting "Run with:" blocks and intra-doc links.