<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hooks on Devops Monk</title><link>https://blog.devops-monk.com/tags/hooks/</link><description>Recent content in Hooks on Devops Monk</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 26 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.devops-monk.com/tags/hooks/index.xml" rel="self" type="application/rss+xml"/><item><title>Claude Code Hooks, Commands, Skills, and Subagents: The Complete Guide</title><link>https://blog.devops-monk.com/2026/04/claude-code-hooks-subagents-piping/</link><pubDate>Sun, 26 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/04/claude-code-hooks-subagents-piping/</guid><description>Most teams use Claude Code reactively — they type a prompt, Claude responds, they type another. That is fine, but it leaves significant value on the table. Claude Code has four automation layers that let you turn it from a reactive assistant into an active workflow participant:
Layer What it does When to reach for it Hooks Shell or HTTP calls that fire on lifecycle events &amp;ldquo;This must happen every time, without exception&amp;rdquo; Custom Commands Reusable slash commands for repeatable prompts &amp;ldquo;I type the same prompt repeatedly&amp;rdquo; Skills Context-aware instructions Claude loads automatically &amp;ldquo;Claude should always do X when working on Y&amp;rdquo; Subagents Separate Claude instances for isolated, parallel work &amp;ldquo;This task is noisy and the main session only needs a summary&amp;rdquo; This post covers how to create each one and when to use them.</description></item></channel></rss>