chore(agents): drop caveman mode and conventional-commit skill refs
CI / check (push) Has been cancelled
CI / check (push) Has been cancelled
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
This commit is contained in:
@@ -45,15 +45,6 @@ Always use these skills when working with this repository:
|
|||||||
|
|
||||||
Do NOT skip deliberative thinking. Surface reasoning through sequentialthinking before acting.
|
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
|
### Blueprint Framework
|
||||||
|
|
||||||
This project uses `numtide/blueprint` which:
|
This project uses `numtide/blueprint` which:
|
||||||
@@ -322,7 +313,7 @@ nix build .#<package-name>
|
|||||||
|
|
||||||
Every completed job or feature must be committed to the git repository.
|
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:
|
This ensures:
|
||||||
- Clean git history with proper commit message formatting
|
- Clean git history with proper commit message formatting
|
||||||
|
|||||||
Reference in New Issue
Block a user