mirror of
https://github.com/hanzoai/datastore.git
synced 2026-10-30 14:48:37 +00:00
George LarionovandClaude Opus 4.8
21ecc2c20b
Fixing GH_CONFIG_DIR only inside fetch_ci_report.js left the skill's own gh lookups (issue/pr view/list) broken on runners with a poisoned GH_CONFIG_DIR. Add .claude/tools/gh-ro.sh: it drops GH_CONFIG_DIR and refuses any non-read-only subcommand, so a single allow-list entry is safe (it cannot create/close/edit/merge/comment or reach gh api). Route every gh read in the skill through it and allow Bash(.claude/tools/gh-ro.sh:*). Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
25 lines
1.0 KiB
Bash
Executable File
25 lines
1.0 KiB
Bash
Executable File
#!/usr/bin/env bash
|
|
# Read-only `gh` wrapper for the investigate-ci skill.
|
|
#
|
|
# Two jobs:
|
|
# 1. Drop GH_CONFIG_DIR before invoking gh. Some agent/CI runners set it to a
|
|
# poisoned config dir (no/expired auth) that makes every `gh` call fail,
|
|
# while the default config (~/.config/gh) authenticates fine. This mirrors
|
|
# how patch-release-check reaches the CLI (env -u GH_CONFIG_DIR gh).
|
|
# 2. Enforce read-only. Only a fixed allowlist of non-mutating subcommands is
|
|
# permitted, so a single `Bash(.claude/tools/gh-ro.sh:*)` allow in
|
|
# settings.investigate.json cannot be used to create/close/edit/merge/
|
|
# comment, or to reach the write-capable `gh api`. Anything else exits 2.
|
|
set -euo pipefail
|
|
|
|
case "${1:-} ${2:-}" in
|
|
"pr view"|"pr list"|"pr diff"|"pr checks"|"issue view"|"issue list") ;;
|
|
*)
|
|
echo "gh-ro.sh: refusing non-read-only invocation: gh ${*:-}" >&2
|
|
echo "gh-ro.sh: allowed: pr {view,list,diff,checks}, issue {view,list}" >&2
|
|
exit 2
|
|
;;
|
|
esac
|
|
|
|
exec env -u GH_CONFIG_DIR gh "$@"
|