Feature: Major changes & updates as per 2025 config

.claude/commands/shellcheck-fix.md

@@ -0,0 +1,64 @@
+---
+argument-hint: <filename>
+description: "Comprehensive shellcheck analysis and fixing workflow. Usage: /shellcheck-fix <filename>"
+author: "Mohit Sakhuja"
+version: "2.0"
+---
+
+# Shellcheck Fix Command
+
+Comprehensive shellcheck analysis and fixing workflow that:
+
+1. Applies automatic fixes first
+2. Analyzes remaining issues
+3. Prioritizes issues by severity
+4. Creates an improvement plan
+5. Implements fixes with user approval
+
+## Instructions
+
+Perform comprehensive shellcheck analysis and fixing workflow for the shell script `$ARGUMENTS`.
+
+Execute the following steps in order:
+
+**Step 1: Apply automatic shellcheck fixes**
+
+!if [ ! -f "$ARGUMENTS" ]; then echo "❌ Error: File '$ARGUMENTS' not found"; exit 1; fi; echo "🔧 Applying automatic shellcheck fixes to $ARGUMENTS..."; shellcheck -f diff "$ARGUMENTS" > "$ARGUMENTS.patch" 2>/dev/null; if [ -s "$ARGUMENTS.patch" ]; then patch "$ARGUMENTS" < "$ARGUMENTS.patch" && echo "✅ Applied automatic fixes to $ARGUMENTS"; else echo "ℹ️  No automatic fixes available for $ARGUMENTS"; fi; rm -f "$ARGUMENTS.patch"
+
+**Step 2: Analyze remaining issues**
+
+Read the file contents and run shellcheck to identify any remaining issues:
+
+!echo "🔍 Running shellcheck analysis on $ARGUMENTS..."; shellcheck "$ARGUMENTS" 2>&1 || echo "Analysis complete - will categorize issues above"
+
+Now read the file: @$ARGUMENTS
+
+**Step 3: Prioritize and categorize issues**
+
+Based on the shellcheck output and file contents, categorize the remaining issues by severity:
+
+- **🔴 Critical**: Security vulnerabilities, potential data loss, script-breaking bugs
+- **🟡 Important**: Best practices violations, maintainability issues, portability concerns
+- **🟢 Minor**: Style preferences, minor optimizations, cosmetic improvements
+
+**Step 4: Create improvement plan**
+
+Think thoroughly about the remaining issues and create a prioritized plan that explains:
+
+- What each issue means and why it matters
+- The proposed fix for each issue
+- The complexity and risk of each change
+- Recommended order of implementation
+
+Present this plan to the user for approval.
+
+**Step 5: Implement approved fixes**
+
+After receiving user approval, implement the fixes systematically following these principles:
+
+- **Follow shell scripting best practices**: Use proper quoting, error handling, and POSIX compliance where applicable
+- **Prioritize maintainable solutions over quick fixes**: Choose readable, robust implementations that will be easy to understand and modify in the future
+- Work through one priority category at a time (Critical → Important → Minor)
+- Make incremental changes to maintain script functionality
+- Verify each fix doesn't introduce new issues
+- Provide clear explanations of changes made and why they improve the code

.claude/settings.json

@@ -0,0 +1,10 @@
+{
+    "permissions": {
+        "allow": [
+            "Bash(patch:*)",
+            "Bash(pre-commit:*)",
+            "Bash(shellcheck:*)"
+        ],
+        "deny": []
+    }
+}

.editorconfig

@@ -0,0 +1,35 @@
+# EditorConfig is awesome: https://EditorConfig.org
+
+# top-most EditorConfig file
+root = true
+
+# Base settings for all files
+[*]
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+indent_style = space
+indent_size = 4
+
+# Shell scripts (shfmt will use these settings)
+[*.{sh,bash,zsh}]
+indent_style = space
+indent_size = 4
+switch_case_indent = true
+
+# YAML files typically use 2 spaces
+[*.{yml,yaml}]
+indent_size = 2
+
+# Markdown files
+[*.md]
+trim_trailing_whitespace = false
+
+# Makefiles require tabs
+[Makefile]
+indent_style = tab
+
+# Go files require tabs
+[*.go]
+indent_style = tab

.markdownlint.yaml

@@ -0,0 +1,15 @@
+# markdownlint configuration
+# See https://github.com/markdownlint/markdownlint/blob/main/docs/RULES.md
+
+# Disable line length rule for documentation
+MD013: false
+
+# Allow duplicate headers (common in documentation)
+MD024:
+  siblings_only: true
+
+# Allow raw HTML (useful for complex formatting)
+MD033: false
+
+# Allow emphasis used instead of a header
+MD036: false

.pre-commit-config.yaml

@@ -0,0 +1,70 @@
+# See https://pre-commit.com for more information
+# See https://pre-commit.com/hooks.html for more hooks
+repos:
+  # Built-in hooks for universal validation
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v6.0.0
+    hooks:
+      - id: trailing-whitespace
+        exclude: '\.patch$'
+      - id: end-of-file-fixer
+        exclude: '\.patch$'
+      - id: check-merge-conflict
+      - id: check-added-large-files
+        args: ["--maxkb=1000"]
+      - id: detect-private-key
+      - id: check-json
+        files: \.json$
+      - id: check-yaml
+        files: \.ya?ml$
+      - id: pretty-format-json
+        args: ["--autofix", "--indent=4"]
+        exclude: ^macos/iterm/
+
+  # Shell script linting and formatting
+  - repo: https://github.com/koalaman/shellcheck-precommit
+    rev: v0.11.0
+    hooks:
+      - id: shellcheck # Already runs in docker.
+        args: [--severity=style]
+
+  # Shell script formatting
+  - repo: https://github.com/scop/pre-commit-shfmt
+    rev: v3.12.0-2
+    hooks:
+      - id: shfmt-docker
+        # We need to provide these arguments separately from settings in `.editorconfig` simply because we require the
+        # `simplify` flag. There's no way to specify this flag with `.editorconfig`.
+        # If we provide ONLY that particular flag here, then `shfmt` ignores the rest of the config. Hence, we need to
+        # provide all flags individually.
+        args: [--write, --simplify, --indent, "4", --case-indent]
+
+  # YAML formatting (2 spaces as per .editorconfig)
+  - repo: https://github.com/google/yamlfmt
+    rev: v0.13.0
+    hooks:
+      - id: yamlfmt
+        args: ["-formatter", "indent=2,retain_line_breaks=true"]
+
+  # Lua formatting (uses .stylua.toml configuration)
+  - repo: https://github.com/JohnnyMorganz/StyLua
+    rev: v2.2.0
+    hooks:
+      - id: stylua-system
+
+  # Markdown linting
+  - repo: https://github.com/igorshubovych/markdownlint-cli
+    rev: v0.45.0
+    hooks:
+      - id: markdownlint-docker
+        args: ["--fix"]
+
+exclude: |
+  (?x)^(
+    macos/themes/.*\.itermcolors|
+    macos/themes/.*\.terminal|
+    macos/iterm/.*\.plist|
+    macos/utils/terminfo/.*\.terminfo|
+    macos/utils/automator/.*\.workflow/.*|
+    \.git/.*
+  )$

.shellcheckrc

@@ -0,0 +1,24 @@
+# vim: ft=conf
+# ShellCheck configuration file
+# See https://github.com/koalaman/shellcheck/wiki/Ignore for explanations
+
+# Disable specific warnings that are often false positives or overly strict
+disable=SC1091  # Not following sourced files (often external files)
+disable=SC2034  # Variable appears unused (may be used in sourced files)
+disable=SC2059  # Don't use variables in printf format strings (sometimes intentional)
+disable=SC2086  # Double quote to prevent globbing and word splitting (sometimes intentional)
+disable=SC2154  # Variable is referenced but not assigned (may be from environment)
+disable=SC2155  # Declare and assign separately to avoid masking return values (sometimes intentional or acceptable)
+disable=SC2312  # Invoke the command separately to avoid masking its return value (sometimes intentional or acceptable)
+
+# Enable all optional checks
+enable=all
+
+# Detect shell
+shell=auto
+
+# Set severity level (error, warning, info, style)
+severity=style
+
+# External sources to follow (add paths to commonly sourced files)
+source-path=SCRIPTDIR

.vscode/extensions.json

@@ -0,0 +1,6 @@
+{
+    "recommendations": [
+        "timonwong.shellcheck",
+        "editorconfig.editorconfig"
+    ]
+}