access-control

File protection blocks edits to designated critical files like configuration and documentation. Define protected files in your configuration, and the Skill automatically prevents modifications, maintaining project integrity across your team.

Branch safety automatically prevents direct work on main and master branches. This enforces clean Git history by blocking edits and risky operations at the branch level, ensuring all changes go through proper workflow.

Command validation intercepts risky Bash operations and enforces playbook-based execution rules. The Skill applies HARD_BLOCK, BLOCK, and WARN levels based on command patterns, preventing commands that could break your project.

Access control combines file protection, branch constraints, and command validation into automated guardrails. State-driven configurations let you define blocking rules once, then apply them consistently to all team members' edits and operations.

Configuration is centralized and state-driven. Define protected files and branch rules once in your config, and the Skill applies them automatically to all Edit, Write, and Bash operations without per-file manual intervention.

Commands are evaluated against contract rules and configuration patterns. Dangerous operations—like destructive deletions or risky Git commands—trigger blocking or warnings based on your defined safety levels, protecting against accidental damage.