메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
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.
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 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.
SOC 직업 분류 기준
| name | gitea-browse |
| description | 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 skill to inspect in-cluster source control and conduct PR-level audit review.
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. Architect uses this same Gitea user for read-only design browsing. 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 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"
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 reviews <number> --repo <owner>/<repo> --login "$REVIEWER_GITEA_TEA_LOGIN_NAME"
Clone only for review inspection, keep the clone in a temporary directory, then discard it.
clone_root="$(mktemp -d "${TMPDIR:-/tmp}/gitea-review.XXXXXX")"
git clone "${REVIEWER_GITEA_BASE_URL%/}/<owner>/<repo>.git" "${clone_root}/<repo>"
cd "${clone_root}/<repo>"
git show <sha>:path/to/file.yaml
git show <sha>
git diff <expected-sha>..<actual-sha> -- path/to/file
git fetch origin pull/<number>/head:pr-<number>
git diff main..pr-<number>
rm -rf "${clone_root}"
tea pr review <number> --repo <owner>/<repo> --comment "Your review observation" --login "$REVIEWER_GITEA_TEA_LOGIN_NAME"
tea pr review <number> --repo <owner>/<repo> --approve --login "$REVIEWER_GITEA_TEA_LOGIN_NAME"
tea pr merge <number> --repo <owner>/<repo> --login "$REVIEWER_GITEA_TEA_LOGIN_NAME"
__GITEA_ADMIN_USERNAME__ is allowed to approve and merge on protected main; treat that authority as expected.--login "$REVIEWER_GITEA_TEA_LOGIN_NAME" for tea commands so the shared reviewer account is selected consistently.tea auth fails, a PR is out of scope, or a merge conflicts, stop and tell main exactly what failed.