cui-diagnostic-patterns

Diagnostic patterns eliminate prompts by replacing Bash-based file operations with non-prompting tools: Glob for file discovery, Read for existence checks and content access, and Grep for searching. This enforces automated workflows across agents and diagnostic commands without user intervention.

Use Glob for discovery and pattern matching, Read for checking file existence and retrieving content, and Grep for content search. Reserve Bash only for true shell execution needs like Git and build commands. This pattern ensures consistent error handling and non-prompting behavior in validation and analysis workflows.

Diagnostic patterns define consistent error handling across Glob, Read, and Grep operations with standardized results parsing and integration into your workflow. This prevents failures from interrupting automated diagnostics and ensures reliable structure validation across agents and commands.

Yes. These non-prompting patterns apply directly to diagnostic, validation, and analysis workflows. They govern file discovery, existence checks, content searches, and structure validation—standardizing tool usage across agents, commands, and skills for repeatable, uninterrupted automation.

Bash prompts halt automation and require user intervention, breaking unattended workflows. Non-prompting tool patterns (Glob, Read, Grep) enable continuous diagnostic operations without interruption while maintaining consistent error handling and predictable results parsing.