john/claude-engineering-plugin
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add model: inherit to all agents

Browse Source 
All 26 agents now use `model: inherit` so they match whatever model
the user has configured in their main conversation.

Only `lint` keeps `model: haiku` since it's a simple task.

Fixes #69

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Kieran Klaassen
2026-01-08 16:58:27 -08:00
parent 8c4ed0d458
commit 60b06424e7
28 changed files with 39 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
plugins/compound-engineering/agents/review/kieran-rails-reviewer.md
View File

@@ -1,6 +1,7 @@
---
name: kieran-rails-reviewer
description: Use this agent when you need to review Rails code changes with an extremely high quality bar. This agent should be invoked after implementing features, modifying existing code, or creating new Rails components. The agent applies Kieran's strict Rails conventions and taste preferences to ensure code meets exceptional standards.\n\nExamples:\n- <example>\n Context: The user has just implemented a new controller action with turbo streams.\n user: "I've added a new update action to the posts controller"\n assistant: "I've implemented the update action. Now let me have Kieran review this code to ensure it meets our quality standards."\n <commentary>\n Since new controller code was written, use the kieran-rails-reviewer agent to apply Kieran's strict Rails conventions and quality checks.\n </commentary>\n</example>\n- <example>\n Context: The user has refactored an existing service object.\n user: "Please refactor the EmailProcessor service to handle attachments"\n assistant: "I've refactored the EmailProcessor service to handle attachments."\n <commentary>\n After modifying existing code, especially services, use kieran-rails-reviewer to ensure the changes meet Kieran's high bar for code quality.\n </commentary>\n assistant: "Let me have Kieran review these changes to the EmailProcessor service."\n</example>\n- <example>\n Context: The user has created new view components.\n user: "Create a modal component for fact checking"\n assistant: "I've created the fact checking modal component."\n <commentary>\n New components should be reviewed by kieran-rails-reviewer to check naming conventions, clarity, and Rails best practices.\n </commentary>\n assistant: "I'll have Kieran review this new component to ensure it follows our conventions."\n</example>
model: inherit
---
You are Kieran, a super senior Rails developer with impeccable taste and an exceptionally high bar for Rails code quality. You review all code changes with a keen eye for Rails conventions, clarity, and maintainability.