bash-linux
Master Bash and Linux Terminal Commands
Generate correct bash commands and scripts without memorization. Claude Code provides accurate patterns for file operations, process management, text processing, and error handling in Linux and macOS environments.
Download the skill ZIP
Upload in Claude
Go to Settings → Capabilities → Skills → Upload skill
Toggle on and start using
Test it
Using "bash-linux". How do I find all Python files and count them?
Expected outcome:
- To find all Python files recursively:
- find . -name '*.py' -type f
- To count them:
- find . -name '*.py' -type f | wc -l
Using "bash-linux". Show me a script that backs up a directory
Expected outcome:
- Here's a backup script with error handling:
- ```bash
- #!/bin/bash
- set -euo pipefail
- SOURCE="$1"
- BACKUP_DIR="$2"
- TIMESTAMP=$(date +%Y%m%d_%H%M%S)
- tar -czf "$BACKUP_DIR/backup_$TIMESTAMP.tar.gz" "$SOURCE"
- echo "Backup completed: backup_$TIMESTAMP.tar.gz"
- ```
- Usage: ./backup.sh /path/to/source /path/to/backup/dir
Using "bash-linux". How do I check if a command succeeded?
Expected outcome:
- You can check exit status with $?:
- ```bash
- if command; then
- echo "Success"
- else
- echo "Failed with exit code $?"
- fi
- # Or use && for chaining
- command && echo "Success" || echo "Failed"
- ```
Security Audit
SafeStatic scanner detected 92 patterns flagged as potential security issues. After manual review, all findings are confirmed FALSE POSITIVES. The skill file is educational documentation containing bash command examples in markdown code blocks and tables. Backticks and command syntax are part of markdown formatting for documentation purposes, not executable code. No malicious intent detected, no security risks identified.
Quality Score
What You Can Build
Developer workflow automation
Software developers use this skill to automate repetitive tasks like file batch processing, log monitoring, and build pipelines. Reduces time spent searching for correct command syntax.
System administration scripting
DevOps engineers and sysadmins reference these patterns to write reliable bash scripts with proper error handling. Helps create maintainable automation scripts for server management.
Learning bash fundamentals
New users transitioning from Windows to Linux or macOS learn correct command patterns and understand bash scripting best practices. Provides quick reference without searching multiple documentation sources.
Try These Prompts
How do I find all JavaScript files modified in the last 7 days?
Show me the command to find and kill a process using port 3000
Create a bash script template that handles errors properly and includes cleanup on exit
How do I extract the second column from a CSV file and count unique values?
Best Practices
- Always quote variables to prevent word splitting and glob expansion: use "$VAR" instead of $VAR
- Use set -euo pipefail at the start of scripts to catch errors early and fail on undefined variables
- Test destructive commands with echo first: replace rm with echo rm to see what would be deleted
- Prefer [[ over [ for conditionals as it's safer and more portable in modern bash scripts
Avoid
- Don't parse ls output - use find or glob patterns instead as ls output is not designed for parsing
- Avoid eval on user input - it allows arbitrary code execution and is a major security vulnerability
- Don't use cd in scripts without error checking - use absolute paths or subshells (cd ... || exit)
- Avoid looping over ls output - use shell globbing (for file in *.txt) instead for reliable file iteration