[Feature Request] Improve Gerrit stack workflow support and cross-session memory management

Bug Description
Claude Code is unreliable at Gerrit stack workflows Across several sessions, Claude repeatedly broke a Gerrit relation chain of about 8 changes. It cost roughly a day of cleanup. What went wrong: GitHub habits applied to Gerrit: it added "make tox pass" fix commits on top of the stack instead of amending the commits that introduced the errors, so every change below them failed CI. Local branches treated as the truth: it built new patch sets on stale parents after server-side (UI) rebases, which split the chain ("Not current"). Commits handed over without the repo's full CI check: it ran partial checks and skipped pylint because it "wasn't installed", even though tox was available. A lesson saved to memory didn't carry over: it was stored per project directory, and a session started from a parent directory never loaded it. Suggestions: Stronger defaults for Gerrit: treat each commit as its own change, check patch-set tips before working, and put fixes in the commit that introduced the error. Memory and rules that apply across working directories within the same repo. Possibly a built-in Gerrit workflow skill, like the existing gerrit-code-review skill but for building and restacking.

Environment Info

• Platform: linux
• Terminal: vscode
• Version: 2.1.282
• Feedback ID: 26b10552-cc97-4fdd-a53c-612924ea9a45

Errors

[]