bash

Standardize Bash command syntax with strict quoting and atomic execution.

Updated Oct 15, 2021
One-click install
npx skills add https://github.com/toqoz/config --skill bash-toqoz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bash
Source: https://github.com/toqoz/config/tree/main/home/agents/skills/bash
Command: npx skills add https://github.com/toqoz/config --skill bash-toqoz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents common shell errors, silent failures, and security risks caused by improper handling of special characters in file paths and incorrect command chaining.

Core Features & Use Cases

  • Path Sanitization: Enforces the use of single quotes for file paths containing shell-special characters like brackets, parentheses, and dollar signs to prevent glob expansion or variable interpolation.
  • Command Execution Safety: Provides guidelines for atomic command execution to ensure agent permission systems can accurately evaluate and approve individual operations.
  • Use Case: When working with modern web frameworks like Next.js or Remix that use special characters in file paths, this skill ensures your file operations succeed without accidental shell interpretation.

Quick Start

Apply the bash skill guidelines to ensure all file paths in your current command are properly quoted and commands are executed independently.

Frequently Asked Questions about bash

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent shell interpretation errors when using bash commands with file paths containing special characters?

To prevent shell interpretation errors in bash commands, use single quotes around file paths containing special characters like brackets or parentheses to stop glob expansion and variable interpolation. This ensures safe execution and prevents silent failures during file system operations.

Why does my bash command fail silently when chaining multiple file system operations together?

Bash command chaining fails silently due to incorrect command sequencing. Enforcing atomic command execution logic ensures each operation is evaluated independently, allowing agent permission systems to accurately approve individual operations and prevent silent failures.

What is the best way to write safe bash commands for modern web frameworks like Next.js or Remix?

The best way to write safe bash commands for frameworks like Next.js or Remix is to standardize syntax and execution patterns. This involves applying strict quoting rules for path sanitization and using atomic execution for multi-step command sequences.

Does using single quotes in bash command lines prevent security risks from variable interpolation?

Yes, using single quotes in bash command lines prevents security risks from variable interpolation. Path sanitization through strict quoting blocks shell-special characters from being interpreted, ensuring robust and error-free command construction.

When do I need to apply strict quoting rules for CLI tool interactions in the shell?

You need to apply strict quoting rules for CLI tool interactions whenever file paths contain shell-special characters. This prevents glob expansion and permission issues during multi-step command sequences, ensuring robust command construction.