Scan codebases for architectural rule violations using .sentrux/rules.toml.
npx skills add https://github.com/Pyl-Tech/stream-coding --skill sentrux
Please help me install this Agent Skill. Skill: sentrux Source: https://github.com/Pyl-Tech/stream-coding/tree/main/.agents/skills/sentrux Command: npx skills add https://github.com/Pyl-Tech/stream-coding --skill sentrux
Sentrux solves the problem of architectural drift by quantifying and enforcing structural quality rules so that code remains layered, bounded, and maintainable over time.
.sentrux/rules.toml to detect violations as a pass/fail gate.gate to compare current structural health against a saved baseline to prevent gradual degradation.Activate the skill by adding a project-specific .sentrux/rules.toml, then run sentrux gate . to enforce the constraints and detect architectural regressions against the baseline.
High-intent search queries and answers about installing and using this skill.
You can enforce architectural boundaries by defining layer and dependency direction constraints in a `.sentrux/rules.toml` file, then running structural checks to catch foundational vs presentation layering violations and dependency drift.
Architectural regression detection compares current codebase health metrics against a saved baseline to prevent gradual degradation. It checks if structural quality scores have dropped due to cyclical structures or excessive complexity introduced by new changes.
You can check code quality gates by running structural analysis commands that scan your codebase against defined thresholds. This pass/fail gate detects cyclical structures, excessive complexity, and dependency direction violations to ensure maintainability.
Yes, structural analysis quantifies codebase modularity and acyclicity by generating a 0–10000 architectural health score. This score is derived from metrics including modularity, acyclicity, depth, equality, and redundancy.
Yes, you need to add a project-specific `.sentrux/rules.toml` file to define your structural constraints. Once configured, you run the gate command to enforce the rules and detect architectural regressions against a baseline.
You should run architectural structural checks during the STRATEGY, BUILD, and VERIFY stages. This ensures that new services or modules do not introduce layered-dependency drift or violate dependency boundaries before integration.
multiplex-aiDefines modular Clean Architecture layers and dependency rules for Android and Kotlin Multiplatform projects.
darelabs-techAggregate DARE-compliant module quality metrics and compare against historical baselines.
hafley66Explain tree-sitter's parsing model and node classification for CST vs AST debugging.
NolanPicEnforce global validation standards across code files and repositories.