Driver
Rex (code reviewer) only fires on PRs in the framework repo because the auto-code-review.sh PostToolUse hook is wired in the ops repo's .claude/settings.json. Managed project repos (yumyum, apexyard-admin) and the portfolio repo don't have the hooks, so PRs skip Rex entirely with no reminder. In a single session, 15 PRs were merged without Rex review — self-discipline failed without mechanical enforcement.
Scope
Make the auto-code-review.sh hook fire on gh pr create regardless of which repo the PR targets. The hook already resolves the ops root via the walker — it just needs to match PR-create commands that target any repo, not just the ops repo.
Two changes:
-
Update auto-code-review.sh — the hook currently fires on PostToolUse for Bash matching gh pr create *. It already works for any repo (it reads the PR URL from stdout). The issue is that the hook only exists in the ops repo's settings.json, so when CWD is inside a managed project workspace, the walker finds the portfolio root (which has no hooks) instead of the ops root.
-
Fix the hook walker for managed project workspaces — the root walker (r=$PWD; while ... onboarding.yaml ...) needs to also check the ops repo when CWD is inside workspace/<name>/. Either:
- Walk up past the portfolio root to find the ops repo (if they're siblings)
- Or use
APEXYARD_OPS_ROOT env var (already set in .mcp.json) as a fallback
Acceptance Criteria
Root cause: hooks only fire when the walker finds the ops root. Managed project workspaces resolve to the portfolio root instead, which has no hooks.
Driver
Rex (code reviewer) only fires on PRs in the framework repo because the
auto-code-review.shPostToolUse hook is wired in the ops repo's.claude/settings.json. Managed project repos (yumyum, apexyard-admin) and the portfolio repo don't have the hooks, so PRs skip Rex entirely with no reminder. In a single session, 15 PRs were merged without Rex review — self-discipline failed without mechanical enforcement.Scope
Make the
auto-code-review.shhook fire ongh pr createregardless of which repo the PR targets. The hook already resolves the ops root via the walker — it just needs to match PR-create commands that target any repo, not just the ops repo.Two changes:
Update
auto-code-review.sh— the hook currently fires on PostToolUse for Bash matchinggh pr create *. It already works for any repo (it reads the PR URL from stdout). The issue is that the hook only exists in the ops repo's settings.json, so when CWD is inside a managed project workspace, the walker finds the portfolio root (which has no hooks) instead of the ops root.Fix the hook walker for managed project workspaces — the root walker (
r=$PWD; while ... onboarding.yaml ...) needs to also check the ops repo when CWD is insideworkspace/<name>/. Either:APEXYARD_OPS_ROOTenv var (already set in .mcp.json) as a fallbackAcceptance Criteria
gh pr createin any managed project workspace triggers Rex review remindergh pr createin the portfolio repo triggers Rex review remindergh pr createin the ops repo still works as beforeRoot cause: hooks only fire when the walker finds the ops root. Managed project workspaces resolve to the portfolio root instead, which has no hooks.