I'll create a log analyzer with these components:

**Architecture:**
- Main function with argument parsing (getopts pattern)
- 4 analysis functions: analyze_ips(), analyze_status_codes(), etc.
- Logging functions for INFO/DEBUG/ERROR output
- Cleanup trap for signal handling

**Tool Selection:**
- awk for status code analysis (single-pass counting, as recommended in
  docs/text-processing-guide.md)
- grep for date filtering (simple pattern matching)
- sort | uniq -c for frequency counting

**Customization Points:**
- LOG_FORMAT variable for different nginx configurations
- TOP_N constant for number of results to show

Shall I proceed with this design?

bash scripts/generate_script_template.sh standard output-script.sh

#!/usr/bin/env bash
#

2. **Strict mode (recommended for all scripts):**
```bash
set -euo pipefail
IFS=$'\n\t'

undefined

4. **Signal handlers for cleanup:**
```bash

undefined

undefined

undefined

undefined

undefined

undefined

undefined

undefined

undefined

undefined

# Validate prerequisites
check_command "grep"
check_command "awk"

# Validate inputs
[[ -n "${INPUT_FILE:-}" ]] || die "Input file not specified. Use -f option."
validate_file "${INPUT_FILE}"

log_info "Starting processing..."

# Main logic here
# ...

log_info "Processing completed successfully"

undefined

#######################################

2. **Inline comments** for complex logic
3. **Usage examples** in the header or usage function

Steps:
1. Generate the bash script
2. Invoke devops-skills:bash-script-validator skill with the script file
3. Review validation results
4. Fix any issues identified (syntax, security, best practices, portability)
5. Re-validate until all checks pass
6. Provide summary of generated script and validation status

undefined

undefined

undefined

undefined

undefined

undefined

undefined

undefined

undefined

2. **Validate all inputs:**
```bash

3. **Avoid eval with user input:**
```bash

4. **Use $() instead of backticks:**
```bash

undefined

undefined

2. **Avoid useless use of cat (UUOC):**
```bash

3. **Process in a single pass when possible:**
```bash

undefined

undefined

2. **Test with sh:**
```bash
sh -n script.sh  # Syntax check

#!/usr/bin/env bash
set -euo pipefail

usage() {
    cat << EOF
Usage: ${0##*/} [OPTIONS] FILE

Process FILE and output results.

Options:
    -h        Show this help
    -v        Verbose output
    -o FILE   Output file (default: stdout)
EOF
}

main() {
    local verbose=false
    local output_file=""
    local input_file=""

    while getopts ":hvo:" opt; do
        case ${opt} in
            h) usage; exit 0 ;;
            v) verbose=true ;;
            o) output_file="${OPTARG}" ;;
            *) echo "Invalid option: -${OPTARG}" >&2; usage; exit 1 ;;
        esac
    done
    shift $((OPTIND - 1))

    input_file="${1:-}"
    [[ -n "${input_file}" ]] || { echo "Error: FILE required" >&2; usage; exit 1; }
    [[ -f "${input_file}" ]] || { echo "Error: File not found: ${input_file}" >&2; exit 1; }

    # Process file
    if [[ -n "${output_file}" ]]; then
        process_file "${input_file}" > "${output_file}"
    else
        process_file "${input_file}"
    fi
}

process_file() {
    local file="$1"
    # Processing logic here
    cat "${file}"
}

main "$@"

#!/usr/bin/env bash
set -euo pipefail

echo "Error Summary:"
echo "=============="

# Extract errors and count by type
grep "ERROR" "${log_file}" \
    | sed 's/.*ERROR: //' \
    | sed 's/ -.*//' \
    | sort \
    | uniq -c \
    | sort -rn \
    | awk '{printf "  %-30s %d\n", $2, $1}'

echo ""
echo "Total errors: $(grep -c "ERROR" "${log_file}")"

process_log "$1"

undefined

#!/usr/bin/env bash
set -euo pipefail

# Processing logic
sed 's/old/new/g' "${file}" > "${output}"
echo "Processed: ${file} -> ${output}"

# Find all files and process in parallel
find "${input_dir}" -type f -name "*.txt" -print0 \
    | xargs -0 -P "${max_jobs}" -I {} bash -c 'process_file "$@"' _ {}

undefined

bash scripts/generate_script_template.sh standard [SCRIPT_NAME]

Example:
  bash scripts/generate_script_template.sh standard myscript.sh

Steps:
1. Generate the bash script following the workflow above
2. Invoke devops-skills:bash-script-validator skill with the script file
3. Review validation results (syntax, ShellCheck, security, performance)
4. Fix any issues identified
5. Re-validate until all checks pass
6. Provide summary of generated script and validation status

undefined

./script.sh --help
./script.sh -v input.log
./script.sh -o report.txt input.log

This summary ensures users understand what was generated and how to use it.