Skip to content

Fix YAML syntax errors in all agent files by quoting descriptions#20

Open
galezra wants to merge 1 commit into
diet103:mainfrom
galezra:fix/yaml-syntax-all-agents
Open

Fix YAML syntax errors in all agent files by quoting descriptions#20
galezra wants to merge 1 commit into
diet103:mainfrom
galezra:fix/yaml-syntax-all-agents

Conversation

@galezra

@galezra galezra commented Nov 12, 2025

Copy link
Copy Markdown

Fix YAML syntax errors in agent description fields

Problem

Agent files were experiencing YAML parsing errors due to unescaped colons in the description field. The error message was:

Error in user YAML: (<unknown>): mapping values are not allowed in this context at line 2 column [various positions]

This occurred because the description fields contained example dialogues with user: and assistant: labels, which YAML interpreted as mapping key-value pairs rather than string content.

Solution

Wrapped all description field values in double quotes to properly escape the content and treat it as a single string value. This allows YAML to correctly parse the colons within the descriptions as part of the string content rather than as mapping separators.

Changes

Fixed YAML syntax in the following agent files:

  • refactor-planner.md
  • web-research-specialist.md
  • documentation-architect.md
  • frontend-error-fixer.md
  • auth-route-tester.md
  • code-architecture-reviewer.md
  • code-refactor-master.md
  • auth-route-debugger.md
  • plan-reviewer.md (fixed earlier)

Technical Details

Changed from:

description: Use this agent when... user: "example" assistant: "example"

To:

description: "Use this agent when... user: \"example\" assistant: \"example\""

The quotes ensure YAML treats the entire description as a string literal, and internal quotes are properly escaped with \n for newlines.

Testing

All agent files now parse correctly without YAML syntax errors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant