Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides command-line instructions for multiple platforms, but Windows-specific tools and patterns (Cmd, PowerShell) are often presented alongside or before Linux equivalents. In several places, Windows command examples are given with dedicated tabs (Cmd, PowerShell), and Windows-specific instructions (such as .venv activation) are detailed. The use of 'command prompt' language and explicit Windows tabs, as well as the inclusion of PowerShell and Cmd examples for Azure CLI and Functions Core Tools, indicate a Windows-first and PowerShell-heavy bias. Linux/macOS instructions are present but sometimes less detailed or appear after Windows options.
Recommendations
- Ensure Linux/macOS instructions are always presented first or equally alongside Windows instructions.
- Provide bash/zsh examples as the primary shell instructions, with Windows alternatives clearly marked as secondary.
- Avoid using 'command prompt' as a generic term; use 'terminal' or specify platform.
- Where possible, consolidate instructions to use cross-platform commands (e.g., bash) and only provide platform-specific alternatives when necessary.
- Review all examples to ensure Linux users have clear, complete, and tested instructions for every step.
- Consider adding WSL (Windows Subsystem for Linux) guidance for Windows users who prefer a Linux-like environment.
Create Pull Request