<?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://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://devops-monk.com/tags/hooks/index.xml" rel="self" type="application/rss+xml"/><item><title>Claude Code Hooks, Subagents, and Piping: Advanced Automation for Teams</title><link>https://devops-monk.com/2026/04/claude-code-hooks-subagents-piping/</link><pubDate>Sun, 26 Apr 2026 00:00:00 +0000</pubDate><guid>https://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. Hooks, subagents, and piping let you build Claude into your workflow so that it works with your tools rather than alongside them.
Hooks: Making Claude Anticipatory A hook is a shell command, script, or HTTP call that fires automatically when Claude Code reaches a specific lifecycle point.</description></item></channel></rss>