Loading…
Enforces functional-core purity rules: PURE-1 (no side effects in core/ modules — no I/O, no clock, no RNG, no logging), PURE-2 (no ambient/global state reads in core), PURE-3 (mock-required-to-test signal — if a function needs a mock to test, it isn't pure and belongs in shell). Loaded by the conductor for write and review operations when core-layer code is in scope. Layer detection follows the conductor's Section 14.
purity-check is an agent skill entry in ChatHome Skills, sourced from GitHub Skill Search and scored 58/100. # Purity Check — Functional Core Enforcement The functional core / impure shell pattern is the single biggest lever for keeping AI-generated code testable and r. As an agent skill, it packages a reusable instruction set that AI coding agents such as Codex and Claude Code can load to perform this task without hand-written glue code. ChatHome Skills discovered this entry through its daily ingest of official registries and GitHub discovery queries, and re-verifies repository facts, freshness signals, and install metadata on every run. The quality score weighs official-registry presence, a working install command, license clarity, GitHub star trajectory, and repository freshness — the full formula is on the Sources page. The install command above is ready to copy. Review the last-pushed date and repository status before adding purity-check to a production agent workflow; the snapshot facts below are point-in-time values from the most recent ingest.
codex skill install mikecubed/agent-orchestrationReview the upstream source before running this command.
Scan coverage: Install metadata and the indexed document body.
Automated signals from install metadata and a bounded skill body — not a full code security audit and not a recursive source or dependency review.
# Purity Check — Functional Core Enforcement The functional core / impure shell pattern is the single biggest lever for keeping AI-generated code testable and reasonable. Pure func