From 4b9f1ed865678b06494c815b463015fb91ddc54b Mon Sep 17 00:00:00 2001 From: Alexander Miroshnichenko Date: Mon, 2 Nov 2026 02:05:18 +0300 Subject: [PATCH] chore(agents): drop caveman mode and conventional-commit skill refs The agent instructions told agents to run two skills that are no longer part of the workflow: - remove the "Communication: Caveman Mode" section, so replies are no longer required to be compressed through the caveman skill - replace the `conventional-commit` skill instruction with a plain requirement to follow Conventional Commits concisely --- AGENTS.md | 11 +---------- 1 file changed, 1 insertion(+), 10 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 60bd09b..9c3a643 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -45,15 +45,6 @@ Always use these skills when working with this repository: Do NOT skip deliberative thinking. Surface reasoning through sequentialthinking before acting. -### Communication: Caveman Mode - -Use **caveman** skill for all user-facing communication. Responses should be: -- Ultra-compressed — cut token waste, keep technical substance -- Direct — no filler, no hedging, no "I'd recommend" -- Action-oriented — state what was done and what's next - -Trigger: `skill: "caveman"` before responding to the user. - ### Blueprint Framework This project uses `numtide/blueprint` which: @@ -322,7 +313,7 @@ nix build .# Every completed job or feature must be committed to the git repository. -When preparing git commits, always use the `conventional-commit` skill to create proper commit messages following conventional commit conventions. +When preparing git commits, always following conventional commit conventions and keep it concise. This ensures: - Clean git history with proper commit message formatting