Use this agent when you need to perform comprehensive testing of the blz CLI tool after code changes, before releases, or when verifying functionality across all commands and output formats. This agent should be invoked proactively after:\n\n \nContext: User has just completed implementing a new CLI command or…
Use this agent when you need to verify that documentation in /docs accurately reflects the current behavior and capabilities of the blz CLI tool. This agent should be used:\n\n- After implementing new CLI features or commands\n- After modifying existing command behavior or flags\n- Before cutting a new release to…
Use this agent when:\n\n1. Adding new sources with index-only content: After running blz add --dry-run and seeing "contentType": "index" ( \nContext: User is adding Supabase to the registry and discovers it's an index file.\n\nuser: "I want to add Supabase to the registry"\nassistant: "Let me add that source and…
Use this agent when you need expert Rust development, code review, architecture decisions, or optimization work. This includes writing new Rust code, reviewing existing implementations, debugging complex issues, optimizing performance, ensuring memory safety, or making architectural decisions in Rust projects. The…