refine-boundaries

Yes, you can enforce testing and git workflow guidelines by adding Boundaries rules under specific topic sections. The skill accepts inline placement within topics like Code Style or Git Workflow, categorizing behaviors as Always, Ask, or Never for agents to follow.

This rule management approach preserves existing project rules by strictly applying additive-only updates. It never rewrites or deletes current boundaries, ensuring your accumulated policy set grows safely over time while maintaining all previously established guidelines.

You can use CLAUDE.md for accumulating boundary guidelines if AGENTS.md is absent. The skill features auto source detection that prefers AGENTS.md first, then falls back to CLAUDE.md, with an optional track override for custom file targeting.

The best way to prevent high-risk actions is to define Never do rules within your project instruction files. This mechanism establishes explicit boundaries that restrict agents from executing dangerous operations across code style, testing, and git workflows.

Boundaries and rule management work by progressively accumulating policy guidelines in instruction files so future agents reference a growing, additive rule set. Instead of rewriting rules, it appends new behavioral constraints per invocation under relevant sections.