メニュー
Browse in-cluster Gitea repos, issues, pull requests, commits, chart values, GitOps definitions, and sandbox image sources for read-only design context with the `__REVIEWER_GITEA_USERNAME__` Gitea user shared with auditor.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use for Gitea, GitOps, registry, and every non-trivial implementation task that should be delegated to Codex instead of being coded inline.
Use for non-trivial implementation work. Delegate the coding or large-repo analysis to Codex CLI, then record usage before handing back results.
Review in-cluster Gitea repos and pull requests by reading files, inspecting diffs, checking comments, posting review feedback, and approving with the `__REVIEWER_GITEA_USERNAME__` Gitea user shared with architect; merge only with explicit instruction.
Use this to turn recent Qdrant memories and changed Nextcloud docs into clean Memgraph links, Qdrant graph-link annotations, and an updated grooming checkpoint.
Use when routing work to a standing specialist or reviewing a specialist return.
Use when operating Nextcloud as the shared coordination layer for desk state, calendars, todos, tables, sharing, or coordination status.
| name | gitea-browse |
| description | Browse in-cluster Gitea repos, issues, pull requests, commits, chart values, GitOps definitions, and sandbox image sources for read-only design context with the `__REVIEWER_GITEA_USERNAME__` Gitea user shared with auditor. |
Use this skill to inspect in-cluster source control before design work.
cluster-gitops - GitOps deployment definitions, platform-stack charts, values, and cluster handoff materialopenclaw-sandbox-images - Dockerfiles and image build configs for agent sandbox runtimesUse the preconfigured git and tea access for the __REVIEWER_GITEA_USERNAME__ Gitea user. Auditor uses this same Gitea user for review work. Coder uses the separate __CODER_GITEA_USERNAME__ Gitea user for implementation and repo management.
tea repo view __CODER_GITEA_USERNAME__/cluster-gitops --login "$REVIEWER_GITEA_TEA_LOGIN_NAME"
tea repo view __CODER_GITEA_USERNAME__/openclaw-sandbox-images --login "$REVIEWER_GITEA_TEA_LOGIN_NAME"
tea issue list --repo <owner>/<repo> --state open --login "$REVIEWER_GITEA_TEA_LOGIN_NAME"
tea issue view <number> --repo <owner>/<repo> --login "$REVIEWER_GITEA_TEA_LOGIN_NAME"
tea pr list --repo <owner>/<repo> --state open --login "$REVIEWER_GITEA_TEA_LOGIN_NAME"
tea pr view <number> --repo <owner>/<repo> --login "$REVIEWER_GITEA_TEA_LOGIN_NAME"
Clone only for inspection, keep the clone in a temporary directory, then discard it.
clone_root="$(mktemp -d "${TMPDIR:-/tmp}/gitea-browse.XXXXXX")"
git clone "${REVIEWER_GITEA_BASE_URL%/}/<owner>/<repo>.git" "${clone_root}/<repo>"
cd "${clone_root}/<repo>"
git ls-tree -r HEAD --name-only
git show HEAD:path/to/file.yaml
git show <sha>:path/to/file.yaml
git log --oneline -20
git log --oneline -- path/to/file.yaml
git show <sha> --stat
rm -rf "${clone_root}"
__GITEA_ADMIN_USERNAME__ remains the final authority for approvals and merges on protected main.--login "$REVIEWER_GITEA_TEA_LOGIN_NAME" for tea commands so the shared reviewer account is selected consistently.tea auth fails or a critical repo is missing, stop and tell main exactly what failed.