Class 7 · 7.2

Sessions, checkpoints & Git: aap ke workflow ka management

Project ke zariye aage aur pichhe jane ke teen overlapping raaste — aur yeh shuru mein taqriban har kisi ko confuse karta hai. Yahan exact pata chalta hai ke sessions, checkpoints aur Git kaise alag hain, aur unhein kaise combine karna hai.

🎯 Goal: apni jagah kabhi mat khoein⏱ Read: 10 min🧭 Type: concepts

Claude Code aap ko project mein aage badhne ka ek behtareen flexible rasta deta hai — shayad ziada hi flexible. "Wahan wapas jane ke jahan mein tha" ke kai overlapping tarike hain, aur yeh beginners ko muddle kar sakta hai. Yeh page unhein suljhatta hai: har ek kya hai, woh aapas mein kaise fit hote hain, aur ek aisa workflow jo aap waqai apna sakte hain.

01Teen tools, teen kaam

Yeh alag alag levels par rehte hain aur alag alag sawalon ke jawabat dete hain. Is tasweer ko apne zehen mein rakhein aur confusion khatam ho jaye gi.

Sessions conversation ko track karti hain; checkpoints prompt-by-prompt steps ko track karte hain (aur code revert kar sakte hain); Git code ko track karta hai. Alag alag kaamon ke liye alag alag tools.

02Sessions — poori conversation resume karna

Session Claude ke sath aap ki conversation ki mukammal state hai: context, history, jo aap kar rahe the. Aap kisi bhi point par session ko name de sakte hain jo us state ko record karta hai, aur baad mein ise dubara conversation shuru karne ke liye resume kar sakte hain.

Resume karna conversation restore karta hai, code nahi

Yeh bohot ahem point hai. Jab aap kisi session ko resume karte hain to aap ko context aur conversation milte hain jaise woh the — aap ki files ya repo ki state nahi. Sessions sirf us baare mein hain jo aap aur Claude baat kar rahe the, is se zyada kuch nahi.

Claude Code

# Claude ke andar — current session ko name dein
/rename snarky-claude

# baad mein, shell se — kisi bhi pichhle session ko resume karein
claude --resume        # named sessions ki list se choose karein
claude                   # ya jahan last chhora tha wahan se continue karein

Demo mein hum ne Claude se "witty aur snarky" hone ko kaha, session ko snarky-claude name diya, quit kiya, aur baad mein claude --resume ke sath wapas live laye — aur bilkul iski snarky personality wapas aa gayi, kyun ke poori conversation state iske sath wapas agayi thi.

03Checkpoints — step by step rewind karna

Ek hi session ke andar, aap ka bheja hua har prompt ek checkpoint hai — waqt mein ek step. Rewinding un steps ke zariye pichhe jata hai. Aur yahan powerful hissa hai: har step par aap conversation, code, dono, ya kisi ko nahi restore karne ka choose kar sakte hain.

Catch: Claude ko sirf un changes ka pata hota hai jo is ne khud kiye

Code rewind karna un edits ke liye kaam karta hai jo Claude ne direct kiye. Lekin agar, us prompt ke dauran, Claude ne koi script chalayi jis ne files change kein — ya aap ne kein — Claude har step par aap ke disk ki copy nahi rakhta, is liye woh unhein revert nahi kar sakta. Hamesha conscious rahein ke rewind kya undo karega aur kya nahi.

04Git — bulletproof snapshot

Dono ke sath bilkul alag Git hai: aap ke code ko snapshot karne aur kisi bhi point par wapas aane ka sahi, long-term tarika. Iska conversation se koi lena dena nahi hai — aur aap jitni baar chahein commit kar sakte hain, yahan tak ke ek hi chat ke andar kai baar. Git woh safety net hai jo doosre do prvide nahi karte.

terminal

git add .
git commit -m "before the risky refactor"
# ...Claude ko kaam karne dein, phir agar zaroorat ho:
git restore .            # uncommitted changes ko chhor dein
git checkout <commit>     # kisi achhe snapshot par wapas aayein

05Aap ko konsa use karna chahiye? Ek working philosophy

Imandarana jawab: jo aap ke kaam karne ke tarike par fit ho — yeh tools aap ke workflow ke mutabiq dhalte hain, ulta nahi. Yahan ek aazmuda tarika hai jise aap copy ya ignore kar sakte hain.

Primary

Git, hamesha

Saath saath meaningful messages ke sath commit karte rahein, taake koi bhi point recoverable ho.

Occasional

Checkpoints

Us cheez ke liye rewind karein jo abhi kharab hui ho aur jise foran undo karna aasan ho.

Rarely

Sessions

Hafta purani conversations ko resume karna confusing ho sakta hai — context mein kya hai track karna mushkil hota hai.

Markdown files aap ki real memory ke taur par

Yeh "very 2025" hai, lekin CLAUDE.md, plan.md aur doosri files mein progress track karna is baat ki crystal-clear, human-readable tasweer deta hai ke project kahan khada hai. Bohot se log sessions ke sath bhi kamyab hote hain — lekin files hafta purani chat mein yeh yaad karne ke liye pichhe scroll karne se behtar hain ke kya kaha gaya tha.

✓ Aham baatein

Sessions = coarse; poori conversation/context ko resume karein (code ko nahi). /rename se name dein, claude --resume se restore karein.
Checkpoints = fine; har prompt ek step hai, aur rewind conversation aur/ya code restore kar sakta hai.
Rewind sirf un changes ko undo karta hai jo Claude ne direct kiye — scripts ke zariye touch ki hui files ko nahi.
Git = bulletproof; code ka snapshot leta hai, conversation se alag. Baar baar commit karein.
Koi ek single "right" tool nahi hai — jo aap ko suit kare pick karein. Ek strong default: Git heavily + Markdown files progress track karne ke liye.