arch-guardrails

Enforce architectural rule compliance for code changes during pre-merge reviews.

1|Updated Apr 12, 2026

Search Tags:#architecture #adr #code-review #guardrails #dependency-management #layering

Ready to run

npx skills add https://github.com/mytechsonamy/VibeFlow --skill arch-guardrails

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Core Features & Use Cases

Static checks against architectural constraints defined in .vibeflow/artifacts/arch-rules.yaml (or vibeflow.config.json → archRulesPath).
Detect layering violations, forbidden imports, and naming pattern violations; report and block non-compliant changes.
Applies during pre-merge reviews or across refactors affecting cross-module boundaries, ensuring ADR compliance.

Quick Start

Run the arch-guardrails check on the proposed changes to identify and report any ADR violations before merging.

Frequently Asked Questions about arch-guardrails

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce architecture rules and layering constraints before merging code?▼

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.

How do I check for forbidden imports and naming pattern violations during a refactor?▼

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.

What is the best way to validate code changes against ADR-recorded constraints?▼

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.

Where do I configure dependency constraints and layering rules for code review?▼

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.

Can I use architectural compliance checks for cross-module boundary refactors?▼

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.