{"version":"2.1.229","anchor":"a-built-in-commit-command-off-unless-a-server-gate-turns-it-","canonical_anchor":"a-built-in-commit-command-off-unless-a-server-gate-turns-it-","heading":"A built-in \/commit command, off unless a server gate turns it on","tier":"soon","area":"Slash Commands","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/a-built-in-commit-command-off-unless-a-server-gate-turns-it-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### A built-in \/commit command, off unless a server gate turns it on\n\nA built-in commit command with a strict git workflow exists but is off unless a server enables it.\n\n**What**\n\nA command named \"commit\" is registered that gathers git status, the diff against HEAD, the branch and the last 10 commits, then follows a fixed workflow: never amend after a failed pre-commit hook, never use `--no-verify`, prefer naming files over `git add -A`, and never push unless asked. Its tool access is limited to git add, status and commit. It appears only when the `tengu_cinder_relay` gate resolves true; the value compiled into the build is false, so whether it shows up is decided by server config.\n\n**Details**\n\n- It is separate from the existing commit-push-PR flow.\n\n**Evidence**\n\n`Create a git commit. Use whenever you are about to create a commit`, `tengu_cinder_relay`\n\n- Area: Slash Commands\n- Names: `\/commit`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}