Skip to content

Conversation

@mjkaye
Copy link

@mjkaye mjkaye commented Oct 1, 2025

This change updates the tools configuration in subagents documentation from comma-separated strings to YAML list format and standardizes tool names to PascalCase.

TLDR

This corrects the tool selection format used in the subagents documentation. The previously used tool selection format is incorrect and leads to invalid subagents which cannot be spawned.

Dive Deeper

When I followed the documentation, using the comma-separated tool list with snake_case, I ended up with a subagent which couldn't be spawned. It cost me a lot of time to realize that the documentation was at fault and I should be using YAML lists with PascalCase. This change will prevent others from experiencing the same issue.

Reviewer Test Plan

Confirm the issue

Use this example from the original document version:

---
name: testing-expert
description: Writes comprehensive unit tests, integration tests, and handles test automation with best practices
tools: read_file, write_file, read_many_files, run_shell_command
---
 
You are a testing specialist focused on creating high-quality, maintainable tests.
 
Your expertise includes:
 
- Unit testing with appropriate mocking and isolation
- Integration testing for component interactions
- Test-driven development practices
- Edge case identification and comprehensive coverage
- Performance and load testing when appropriate
 
For each testing task:
 
1. Analyze the code structure and dependencies
2. Identify key functionality, edge cases, and error conditions
3. Create comprehensive test suites with descriptive names
4. Include proper setup/teardown and meaningful assertions
5. Add comments explaining complex test scenarios
6. Ensure tests are maintainable and follow DRY principles
 
Always follow testing best practices for the detected language and framework.
Focus on both positive and negative test cases.
  1. Save it as a subagent in your .qwen/agents/ directory
  2. Run qwen-code
  3. Run the /agents manage command
  4. Confirm that the newly created subagent is not listed.

Confirm the fix

Use the same example but from the corrected document version:

---
name: testing-expert
description: Writes comprehensive unit tests, integration tests, and handles test automation with best practices
tools:
 - ReadFile
 - WriteFile
 - ReadManyFiles
 - RunShellCommand
---

You are a testing specialist focused on creating high-quality, maintainable tests.

Your expertise includes:

- Unit testing with appropriate mocking and isolation
- Integration testing for component interactions
- Test-driven development practices
- Edge case identification and comprehensive coverage
- Performance and load testing when appropriate

For each testing task:

1. Analyze the code structure and dependencies
2. Identify key functionality, edge cases, and error conditions
3. Create comprehensive test suites with descriptive names
4. Include proper setup/teardown and meaningful assertions
5. Add comments explaining complex test scenarios
6. Ensure tests are maintainable and follow DRY principles

Always follow testing best practices for the detected language and framework.
Focus on both positive and negative test cases.
  1. Save it as a subagent in your .qwen/agents/ directory
  2. Run qwen-code
  3. Run the /agents manage command
  4. Confirm that the newly created subagent is now listed.

Testing Matrix

This is a documentation change so these tests are not relevant.

This change updates the tools configuration in subagents documentation from comma-separated strings to YAML list format and standardizes tool names to PascalCase.

The previously used tool selection format is incorrect and leads to invalid subagents which cannot be spawned.
@mjkaye mjkaye changed the title docs(subagents): convert tools to YAML list and PascalCase fix: docs(subagents): convert tools to YAML list and PascalCase Oct 1, 2025
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