70 lines
No EOL
1.6 KiB
Text
70 lines
No EOL
1.6 KiB
Text
---
|
|
description: Standards for handling command paths in scripts, preferring PATH over absolute paths
|
|
globs: **/*.{sh,bash}
|
|
---
|
|
<rule>
|
|
When writing scripts that use external commands:
|
|
|
|
1. Always try PATH first:
|
|
```bash
|
|
if command -v COMMAND >/dev/null 2>&1; then
|
|
CMD="COMMAND"
|
|
else
|
|
CMD="/absolute/path/to/COMMAND"
|
|
fi
|
|
```
|
|
|
|
2. Known fallback paths:
|
|
- Bun: $HOME/.bun/bin/bun
|
|
- Go: /usr/local/go/bin/go
|
|
|
|
3. Guidelines:
|
|
- Use command -v to check if command exists in PATH
|
|
- Store command path in a variable for reuse
|
|
- Use meaningful variable names (e.g., BUN_CMD, GO_CMD)
|
|
- Document why absolute paths are needed as fallback
|
|
- Consider environment-specific paths
|
|
- Use $HOME instead of ~ for home directory paths
|
|
|
|
4. Example pattern:
|
|
```bash
|
|
# Find executable
|
|
if command -v bun >/dev/null 2>&1; then
|
|
BUN_CMD="bun"
|
|
else
|
|
BUN_CMD="$HOME/.bun/bin/bun"
|
|
fi
|
|
|
|
# Use the command
|
|
$BUN_CMD run build
|
|
```
|
|
|
|
metadata:
|
|
priority: high
|
|
version: 1.0
|
|
</rule>
|
|
|
|
examples:
|
|
- input: |
|
|
# Bad: Using absolute path directly
|
|
/usr/local/go/bin/go build
|
|
output: |
|
|
# Good: Try PATH first
|
|
if command -v go >/dev/null 2>&1; then
|
|
GO_CMD="go"
|
|
else
|
|
GO_CMD="/usr/local/go/bin/go"
|
|
fi
|
|
$GO_CMD build
|
|
|
|
- input: |
|
|
# Bad: Using tilde expansion
|
|
~/.bun/bin/bun install
|
|
output: |
|
|
# Good: Use $HOME
|
|
if command -v bun >/dev/null 2>&1; then
|
|
BUN_CMD="bun"
|
|
else
|
|
BUN_CMD="$HOME/.bun/bin/bun"
|
|
fi
|
|
$BUN_CMD install |