Enforce architectural rule compliance for code changes during pre-merge reviews.
npx skills add https://github.com/mytechsonamy/VibeFlow --skill arch-guardrails
Please help me install this Agent Skill. Skill: arch-guardrails Source: https://github.com/mytechsonamy/VibeFlow/tree/main/skills/arch-guardrails Command: npx skills add https://github.com/mytechsonamy/VibeFlow --skill arch-guardrails
Validates proposed changes against architectural rules — layering, allowed dependencies, forbidden imports, naming conventions. Use before merging or when reviewing a refactor that touches cross-module boundaries. Blocks work that violates ADR-recorded constraints.
Run the arch-guardrails check on the proposed changes to identify and report any ADR violations before merging.
High-intent search queries and answers about installing and using this skill.
You can enforce architecture rules before merging by validating proposed code changes against predefined layering constraints, allowed dependencies, and forbidden imports to detect cross-module boundary violations and block non-compliant work.
To check for forbidden imports and naming pattern violations during a refactor, run static checks against architectural constraints to identify layering violations and naming mismatches across module boundaries, ensuring ADR compliance.
The best way to validate code changes against ADR-recorded constraints is by running pre-merge architectural checks that enforce layering rules, detect forbidden imports, and block work that violates documented architectural decisions.
You configure dependency constraints and layering rules in an arch-rules YAML file within a project artifacts directory or via a JSON configuration file, which the system reads to evaluate code changes during pre-merge reviews.
Yes, architectural compliance checks are applicable during refactor assessments across cross-module boundaries, detecting layering violations, forbidden imports, and naming mismatches to ensure changes adhere to established constraints.
LiorCohenDefine component types, settings schemas, and validation rules for fullstack-typescript tech packs.
beomeodevValidate requirements against EARS patterns and detect forbidden phrases.
saitocoCoordinate acceptance criteria verification and multi-perspective reviews on GitHub pull requests.
Chang-Shih-YungAggregate type checker, linter, and test results into a 0-10 composite score.
