Imported from PerishLab/ectropy (
skills/ectropy/SKILL.md). Install upstream withnpx skills add PerishLab/ectropy --skill ectropy. Copyright stays with the author.
Ectropy
Ectropy refuses structural entropy it can detect honestly. Every finding is an
error and exit zero means exactly clean. Outside a repository carrying
ectropy.toml this brief is silent.
Objects
- A law is one named refusal over one mechanically visible projection.
- A finding is one law refusing at one location; no warning or debt mode.
- A module root is the path a nesting limit is measured from.
- A boundary is a narrow justified path where a named law does not apply.
- A term is one registered compound atom in one language namespace.
- An adapter carries one language dialect, never framework identity.
Laws
Sixteen named laws each refuse one detectable shape. Query the catalog instead
of copying it: ectropy law lists every name with what it refuses, and
ectropy law NAME reads one. ban, coverage, and grant admit no boundary
exemption; the catalog says so per law.
Actions
ectropy [ROOT]
ectropy law [NAME]
ectropy shape [ROOT]
ectropy vocabulary [ROOT]
ectropy cookbook [ENTRY]
ectropy skill --helpOperating laws
- KISS stands above the laws and is never a finding or suppression label. A short expression is not simple while it carries an unnamed combination space, table, object, parameter structure, or translation.
- Prefer a smaller unit, a name, a test, a term, or a document over prose embedded beside code.
- Unparsed syntax is an error: Ectropy cannot claim a clean result for terrain it did not understand.
- Exit 0 is
clean, 1 carries findings, 2 is operational. The sixteen laws, configuration schema, deterministic order and digests, and structure and vocabulary inspection are mechanized; boundary truthfulness, whether a term is real product vocabulary, and parser breadth beyond current adapters are not. - Repository shape, dependency policy, release law, and landing procedure belong to Plumb. Never claim them as Ectropy checks.
- Report false findings, coverage gaps, and unclear law as issues at https://git.perish.top/PerishFire/ectropy.
Use PATHS.md for routine flows and SCENARIOS.md only when one of its bounded cases applies.