Extend Caveman guidelines to commit and review skills

Before this commit, even when Caveman Mode was active, specialized workflows like code reviews and git commits still used default formatting rules, creating verbose git message logs and multi-line comments that defeated the token compression objectives of Caveman Mode.

We modified git-commit.md and code-review.md system skill instructions to add dedicated Caveman Mode overrides. When the mode is active, the model is instructed to generate conventional commits without filler words, keeping sentences extremely telegraphic, and to write code review comments as ultra-terse, single-line messages.

An ideal solution would include a configuration parameter for formatting templates so that developers can customize review symbols and define custom message templates for commits.

Author: Test

cmd/gptcode/caveman.go

@@ -54,7 +54,7 @@ var cavemanCompressCmd = &cobra.Command{
 	Long: `Reads the target file and uses the LLM to rewrite its natural language prose
 in a highly compressed Caveman format. Saves a backup of the original file
 as <filename>.original.<ext>. Code blocks, URLs, and file paths are preserved byte-for-byte.`,
-	Args:  cobra.ExactArgs(1),
+	Args: cobra.ExactArgs(1),
 	RunE: func(cmd *cobra.Command, args []string) error {
 		path := args[0]
 		data, err := os.ReadFile(path)

internal/prompt/skills/code-review.md

@@ -69,4 +69,15 @@ Rules for comments:
 # Code Review
 
 [Comments numbered [1], [2], etc.]
+```
+
+## Caveman Mode Override
+
+If Caveman Mode is active (enabled in defaults/config):
+- Make comments telegraphic, dropping filler, hedging, and articles.
+- Keep comments to a single line where possible.
+- Format: `[line]: 🔴 bug/warning: [issue]. [fix].`
+- Example: `L42: 🔴 bug: user null. Add guard.`
+- Example: `L84: ⚠️ warning: load all records into memory. 10k+ records will OOM. Use pagination.`
+
 

internal/prompt/skills/git-commit.md

@@ -65,3 +65,13 @@ git commit -m $'paragraph 1\n\nparagraph 2\n- bullet point\n- bullet point'
 ```
 
 Once you commit, let me know what the commit title was.
+
+## Caveman Mode Override
+
+If Caveman Mode is active (enabled in defaults/config):
+- Keep conventional structure but drop all filler, hedging, and articles.
+- Keep sentences telegraphic and extremely short. Focus strictly on "why" over "what".
+- Example P1: "Agent output verbose. Bloat context window. Increase cost."
+- Example P2: "Impl filter engine in filter.go. Compress test, install, git output. Add Tee cache for failed commands. Save savings statistics to disk."
+- Example P3: "Ideal: user configure custom filter rules via config file."
+