terminal-path-verification

Terminal Path Verification

// Description: Best practices for verifying paths and locations before executing terminal commands // Recommended Globs: **/.{js,jsx,ts,tsx}, **/.sh

Overview

Always verify current directory and path structure before executing path-related commands to prevent errors and unintended operations.

Core Rules

1. Before any cd command:
   • Use pwd to verify current location
   • Use ls to verify target directory exists
2. Before file operations:
   • Use ls to verify file existence
   • Use ls -la for detailed file information when needed

Examples

✅ Good Practice

# Before changing directory
pwd  # Check current location
ls   # Verify directory structure
cd target_directory

# Before file operations
ls -la file_to_modify.txt  # Verify file exists and check permissions
vim file_to_modify.txt

❌ Bad Practice

# Directly changing directory without verification
cd some_directory  # Might not exist!

# File operations without verification
rm file.txt  # Dangerous without verification!

Implementation in Cursor

async function executeTerminalCommand(command: string) {
  // Always verify location before path-related commands
  if (command.startsWith('cd ')) {
    await verifyPath(command.split(' ')[1]);
  }

  // Always verify file existence before file operations
  if (isFileOperation(command)) {
    await verifyFileExistence(command);
  }
}

async function verifyPath(targetPath: string) {
  // Check current location
  console.log('Current location:');
  await runCommand('pwd');

  // List directory contents
  console.log('\nDirectory contents:');
  await runCommand('ls');

  // Verify target exists
  if (!(await pathExists(targetPath))) {
    throw new Error(`Target path does not exist: ${targetPath}`);
  }
}

Best Practices

• Always use pwd before changing directories
• Use ls to verify directory contents
• Use ls -la when file permissions are important
• Implement path verification in automated scripts
• Add error handling for non-existent paths