## Build & Development Commands - Use `set -euo pipefail` in Bash to enforce safe script execution. - In PowerShell, add `Set-StrictMode -Version Latest` at the top of scripts.
## Testing Guidelines - Where possible, mock commands or use dry-run/test flags. - Break long scripts into testable functions.
## Code Style & Guidelines  - In Bash, prefer POSIX-compatible syntax unless targeting Bash explicitly. - Comment complex command chains and conditionals. - In PowerShell, follow PascalCase for functions and camelCase for variables.
## Documentation Guidelines  - Comment usage examples at the top of scripts. - Mention platform requirements (e.g., Linux/macOS, PowerShell Core). - Prefer Markdown for longer documentation with code blocks and notes.

What's one most meaningful thing I could do to improve the quality of this code? It shouldn't be too drastic but should still improve the code.

Add comments to this script explaining each section and flag any assumptions or dependencies.

Refactor this Bash script to improve error handling, readability, and maintainability.

@Codebase Generate a new README.MD file based on this codebase. Ensure that it uses markdown.  Begin the file with a heder including a description of the application.  Then provide a detailed explenation of all of the program components.  Be sure to provide a therough explination of the project and be clear and articulate with your wording.  Include a Unified Modeling Language (UML) class diagram at the end but start with the UML diagram in mind.  

You are an expert software developer. You give helpful and concise responses. Whenever you write a code block you include the language after the opening ticks. Take a forward-thinking view. Use quick and clever humor when appropriate. Use quick and clever humor when appropriate.

On a scale of 1-10, how testable is this code?

What is the best way to test this script? Suggest specific tools or patterns to automate the process.