bash-basics
Production-grade Bash fundamentals - syntax, variables, control flow, functions
What this skill does
# Bash Basics Skill
> Master the fundamentals of Bash shell scripting with production-ready patterns
## Learning Objectives
After completing this skill, you will be able to:
- [ ] Write syntactically correct Bash scripts
- [ ] Use variables with proper quoting and expansion
- [ ] Implement control flow structures (if, case, loops)
- [ ] Design reusable functions with error handling
- [ ] Apply the strict mode (`set -euo pipefail`)
## Prerequisites
- Basic command line familiarity
- Text editor (vim, nano, or IDE)
- Linux/macOS/WSL environment
- Bash 4.0+ installed
## Core Concepts
### 1. Script Structure
```bash
#!/usr/bin/env bash
# Script: example.sh
# Purpose: Demonstrate basic structure
# Usage: ./example.sh [options]
set -euo pipefail # Strict mode
IFS=$'\n\t' # Safe IFS
# Constants
readonly VERSION="1.0.0"
# Main logic
main() {
echo "Hello, World!"
}
main "$@"
```
### 2. Variables
```bash
# Declaration
name="value" # String
declare -i count=0 # Integer
declare -r CONST="immutable" # Readonly
declare -a array=("a" "b" "c") # Array
declare -A map=([key]="val") # Associative array
# Expansion
echo "${name}" # Basic
echo "${name:-default}" # Default if unset
echo "${name:?error msg}" # Error if unset
echo "${#name}" # Length
echo "${name^^}" # Uppercase
echo "${name,,}" # Lowercase
```
### 3. Control Structures
```bash
# Conditionals
if [[ -f "$file" ]]; then
echo "File exists"
elif [[ -d "$file" ]]; then
echo "Directory exists"
else
echo "Not found"
fi
# Case statements
case "$option" in
start) do_start ;;
stop) do_stop ;;
*) echo "Unknown" ;;
esac
# Loops
for item in "${array[@]}"; do
echo "$item"
done
while read -r line; do
process "$line"
done < file.txt
```
### 4. Functions
```bash
function greet() {
local name="${1:?Name required}"
echo "Hello, $name!"
}
# With return values
function add() {
local a="${1:-0}"
local b="${2:-0}"
echo $((a + b))
}
result=$(add 5 3)
```
## Common Patterns
### Error Handling Pattern
```bash
die() {
printf 'ERROR: %s\n' "$1" >&2
exit "${2:-1}"
}
try_command() {
if ! "$@"; then
die "Command failed: $*"
fi
}
```
### Argument Parsing Pattern
```bash
while [[ $# -gt 0 ]]; do
case "$1" in
-h|--help) usage; exit 0 ;;
-v|--verbose) VERBOSE=true; shift ;;
--) shift; break ;;
-*) die "Unknown option: $1" ;;
*) break ;;
esac
done
```
## Anti-Patterns
| Don't | Do | Why |
|-------|-----|-----|
| `for f in $(ls)` | `for f in *` | Parsing ls breaks on spaces |
| `` result=`cmd` `` | `result=$(cmd)` | Backticks don't nest |
| `[ $var = x ]` | `[[ "$var" = x ]]` | Unquoted vars break |
| `cd dir; cmd` | `(cd dir && cmd)` | cd can fail silently |
## Practice Exercises
1. **Hello Script**: Write a script that greets by name
2. **File Counter**: Count files in a directory by extension
3. **Backup Script**: Create timestamped backups
4. **Config Parser**: Parse key=value config files
## Troubleshooting
### Common Errors
| Error | Cause | Fix |
|-------|-------|-----|
| `unbound variable` | Using undefined var | Use `${var:-}` |
| `syntax error` | Missing quotes | Check bracket matching |
| `command not found` | PATH issue | Use full path |
| `permission denied` | Not executable | `chmod +x script` |
### Debug Techniques
```bash
# Enable trace
set -x
# Verbose PS4
export PS4='+(${BASH_SOURCE}:${LINENO}): '
# Shellcheck
shellcheck script.sh
```
## Resources
- [Bash Manual](https://www.gnu.org/software/bash/manual/)
- [ShellCheck](https://www.shellcheck.net/)
- [Google Shell Style Guide](https://google.github.io/styleguide/shellguide.html)
- [Bash Pitfalls](https://mywiki.wooledge.org/BashPitfalls)
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.