Fix YAML parsing errors in agent description fields (#74)

This commit is contained in:
CodePoet
2026-01-10 00:40:33 +09:00
committed by GitHub
parent 60b06424e7
commit fe3f19f220
26 changed files with 26 additions and 26 deletions

View File

@@ -1,6 +1,6 @@
---
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>
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
---