◆ Vibe EngineeringSMIT · AI Agentic Engineering English
Class 12 · 12.5

Hooks: Claude Code ko events par react karwana

Aksar aap ko hooks ki zaroorat nahi hoti, lekin jab aap sochte hain, “kaash yeh har dafa khud ho jaye,” to jawab hooks hain. Ralph loops andar se isi tarah kaam karte hain, aur hamare reviewer ko khud chalne wali cheez bana dete hain.

🎯 Maqsad: event par automation⏱ Parhein: 13 min🪝 Qisam: hands-on

Hook ek event (Claude Code ke andar hone wali koi baat) ko ek action (woh kaam jo aap khud chalwana chahte hain) se jorta hai. Yeh sab yaad karne ki zaroorat nahi — bas bunyadi baat samjhein aur zaroorat par sahi jagah dhoondhna jaan lein.

01Hook kya hota hai

Kisi khaas surat-e-haal mein — jaise Claude shell command chalane wala ho ya apna kaam abhi khatam kare — aap chahte hain ke baghair pooche koi kaam yaqini taur par ho. Woh surat-e-haal event hai; aur jo cheez yaqini taur par hoti hai woh hook hai.

EVENTe.g. “Claude stopped” HOOKin settings.json ACTIONcommand / prompt / agent
Ralph loops isi tarah bante hain: “stop” event par hook naya prompt bhejta hai — “lagta hai aap kaam mukammal nahi kar paye, dobara koshish karein” — aur loop chalta rehta hai.

02Kin events ko pakra ja sakta hai

/hooks menu kholein aur poori list dekhein. Zehan mein rakhne ke liye useful misaal:

EventKab chalta hai…
PreToolUse / PostToolUseClaude ke tool chalane se bilkul pehle / baad (misal ke taur par shell command).
UserPromptSubmitJab aap prompt submit karte hain.
NotificationJab Claude aap ki tawajjo chahta hai (misal ke taur par permission maangna).
StopJab Claude apna kaam khatam karta hai — hum isi ko use karenge.
SubagentStop, PreCompact, SessionStart/EndSub-agent ke khatam hone, compact se pehle, aur session ki boundaries par…
Do mashhoor istemal

(1) PreToolUse par jab yeh seedha python chalane wala ho to pakrein aur is ke bajaye uv run par zor dein — is bhoolne wali aadat ko theek karne ke liye. (2) Notification par phone ko ping karein taake aap kaam chalta chhor kar door ja saken aur yeh khamoshi se aap ka intezar na karta rahe.

03Hook ke teen kaam

Event chalne par hook teen qisam ke actions mein se ek chalata hai:

command

Shell command chalana

Sab se zyada bharosemand. Qabil-e-peshgoi aur mazboot — yahin se shuru karein.

prompt

Claude ko hidayat bhejna

Kaam ka hai, lekin thora pecheeda — permission ki pabandiyan hoti hain (misal ke taur par yeh seedha file nahi likh sakta).

agent

Sub-agent shuru karna

Kaam ko main context se bahar rakhta hai, lekin mazboot banane ke liye tajurbe ki zaroorat hoti hai.

04Apne kaam ka review karne wala stop-hook banayein

Hooks .claude/settings.json mein hote hain (ya /hooks menu se). Jab bhi Claude khatam karega hum automatic code review chalwayenge — command ke taur par apne dost codex exec ko use karke.

.claude/settings.json
{
  "hooks": {
    "Stop": [
      { "hooks": [
        { "type": "command",
          "command": "codex exec \"review changes since the last commit, write results to planning/review.md\"" }
      ] }
    ]
  }
}
claude
> please make a concise README.md for the project

# Claude writes the README, then finishes → the Stop event fires →
# the hook launches codex in the background → codex writes review.md.
# Claude doesn’t even know the review happened. 
“command” kyun behtar hai

command action sirf shell command chalata hai — bilkul mazboot. prompt aur agent actions mein permission ki aisi bareekiyan hain jinhein theek karne ke liye chhed-chaad karni parti hai. Jo baat shell command ki shakal mein keh sakte hon, usi tarah karein.

05Hooks kab (aur kab nahi) use karein

Hooks sirf zaroorat par use karein

Hooks complexity barhate hain — zyada moving parts aur khamoshi se fail hone ke zyada mauqe. Inhein har jagah na lagayein. Tab tak intezar karein jab tak aap ko waqai baar baar wali “har dafa yeh karo” zaroorat mehsoos na ho. Phir docs dekhein (/hooks ya “Claude Code hooks” search karein), ek hook banayein aur aage barhein.

Ab aap ko naqsha pata hai: ek event hook ko trigger karta hai, jo command (sab se bharosemand), prompt, ya agent chalata hai. Zaroorat par raasta dhoondhne ke liye itna kaafi hai — aur agla qadam bhi tayyar hai: in sab ko shareable plugin mein bundle karna.

✓ Ahm baatein

  • Hook ek event (misal ke taur par Stop) ko aise action se jorta hai jo khud chal jata hai.
  • Events mein tool use, notifications, prompt submit aur session boundaries shamil hain — /hooks dekhein.
  • Actions command (sab se bharosemand), prompt, ya agent hote hain.
  • Hooks .claude/settings.json mein hote hain; Stop hook review khud chala sakta hai — Ralph loops bhi isi tarah bante hain.
  • Inhein kam istemal karein — sirf tab jab waqai “har dafa yeh karo” wali zaroorat ho.