Hook for powershell under windows

[superjojo79]

Hi,

I've converted the shell hooks to powershell to allow code-review to work directly under windows. How to propose them to the repo (I'm new to contrib).

Here is an exemple (common script + pre-commit) in attachment

crg-hook-common.txt
crg-pre-commit.txt

I've converted the others too. Let me know if it interests you.

Kind regards

[tirth8205]

Yes please — open the PR! Pointers so it lands smoothly:

• The hook commands are generated in code_review_graph/skills.py (generate_hooks_config for Claude Code, generate_codex_hooks_config for Codex); a PowerShell variant gated on sys.platform == "win32" (or a --shell option) belongs there rather than in static files.
• Keep the two invariants the bash versions have: drain stdin first and fail open (the PowerShell equivalents of cat >/dev/null || true; and || true) — large PostToolUse payloads otherwise break pipes (Codex PostToolUse hook should drain stdin to avoid Broken pipe (os error 32) on large tool outputs #493).
• Tests go in tests/test_skills.py — recent hook-robustness work (PR feat: custom languages, PR-review GitHub Action, honest benchmarks, FAQ, community infra + verified Windows/hygiene fixes #541) added a TestShippedHooksFiles class you can mirror, and also switched hook installs to git rev-parse --git-path hooks, so build on current main.

Since you mentioned being new to contributing: fork → branch → PR against main, and the PR template will walk you through the checklist (uv run pytest, uv run ruff check). Happy to review.

[superjojo79]

Hi, I'll do my best to follow instructions. I will need a little time. Regards. Le mer. 10 juin 2026 à 20:05, Tirth Kanani ***@***.***> a écrit :

…

Yes please — open the PR! Pointers so it lands smoothly: - The hook commands are generated in code_review_graph/skills.py ( generate_hooks_config for Claude Code, generate_codex_hooks_config for Codex); a PowerShell variant gated on sys.platform == "win32" (or a --shell option) belongs there rather than in static files. - Keep the two invariants the bash versions have: drain stdin first and fail open (the PowerShell equivalents of cat >/dev/null || true; and || true) — large PostToolUse payloads otherwise break pipes (#493 <#493>). - Tests go in tests/test_skills.py — recent hook-robustness work (PR #541 <#541>) added a TestShippedHooksFiles class you can mirror, and also switched hook installs to git rev-parse --git-path hooks, so build on current main. Since you mentioned being new to contributing: fork → branch → PR against main, and the PR template will walk you through the checklist (uv run pytest, uv run ruff check). Happy to review. — Reply to this email directly, view it on GitHub <#501?email_source=notifications&email_token=ASMKDTKKDDIQ6CO3HUDXGIT47GPOJA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZSGU2DIMZZUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-17254439>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASMKDTJD647BATBBJJKGP7T47GPOJAVCNFSNUABJKJSXA33TNF2G64TZHMYTCNRXG44DQMZUGE5UI2LTMN2XG43JN5XDWMJQGA4TOOBWG2QXMAQ> . You are receiving this because you authored the thread.Message ID: ***@***.*** .com>