---
title: "Comment by Paul Pham on \"Codex Rules: Control Commands with prefix_rule\" | Hashnode"
description: "The default decision being allow is the one that would bite me. Copy a prefix_rule, forget the decision line, and it quietly allows the command. The match and n"
url: "https://hashnode.com/posts/codex-rules-control-commands-with-prefix-rule/6af7498220184c233a0d88a6/comment/6af790331dfc51e53e0f67f7"
---

[Discussion](https://hashnode.com/posts/codex-rules-control-commands-with-prefix-rule/6af7498220184c233a0d88a6)

Comment [Codex Rules: Control Commands with prefix\_rule](https://hashnode.com/posts/codex-rules-control-commands-with-prefix-rule/6af7498220184c233a0d88a6)

[Paul Pham](https://hashnode.com/@paulpham157)

[Nov 13](https://hashnode.com/posts/codex-rules-control-commands-with-prefix-rule/6af7498220184c233a0d88a6/comment/6af790331dfc51e53e0f67f7)

The default decision being allow is the one that would bite me. Copy a prefix\_rule, forget the decision line, and it quietly allows the command. The match and not\_match examples that get checked on load seem like a good habit.
