Repository navigation
Conversation
The mctl-docs agent's primary signal is sibling-repo git history. In cluster runs, only mctl-gitops is cloned; previously the skill recorded "no signal: <repo> path missing" for every other repo, which made the agent useless in production. Teach scan-sibling-commits to detect missing local clones and fall back to api.github.com/repos/mctlhq/<repo>/commits via WebFetch/curl, authenticated with the GITHUB_TOKEN env (already passed through by options.py via os.environ; the cluster wiring lands in the parallel mctl-gitops PR). Authenticated rate limit is 5000/h vs 60/h public, so 7 repos × 1 list-call per run is comfortable headroom. CLAUDE.md gains a short note pointing operators at the fallback path and explaining the silent degradation when the token is absent.
…kill codex P2 — per_page=50 capped at 50 commits/repo, dropping older ones. Now max 5 pages x 100 commits with Link: rel="next" follow + sanity cap note in output when hit.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1f11782f49
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| - `proposals/` — оформленные предложения. Slug = `<area>-<short-desc>`, например `mcp-identity-tools` или `openclaw-skill-quotas`. | ||
| - За пределы своей папки не выходи. Чужие сервисы — НЕ редактируешь, только читаешь git log. | ||
| - **Не клонируй ничего**. Если соседний репо отсутствует по пути из `SIBLING_REPOS_PATH` — задокументируй это в inbox как "no signal: <repo> path missing" и продолжай со следующим. | ||
| - **Не клонируй ничего**. В кластере sibling-клоны отсутствуют (clone-gitops step клонирует только `mctl-gitops`); в этом случае skill `scan-sibling-commits` автоматически fall back на GitHub REST API через `WebFetch`/`curl`. Для этого нужен env `GITHUB_TOKEN` (fine-grained PAT, Contents:read на `mctlhq/*`). Если токен пустой — public API rate-limit (60/h) почти гарантированно убьёт run, и skill пометит "no signal: <repo> rate-limited" в inbox. С токеном лимит 5000/h — комфортно для 7 репо. Подробности: `agents/mctl-docs/.claude/skills/scan-sibling-commits/SKILL.md`. |
There was a problem hiding this comment.
This new guidance says cluster runs clone only mctl-gitops and rely on GitHub API fallback, but the earlier “Соседние репо для мониторинга” section in the same file still states that clone-gitops clones all repos. That contradiction makes the runbook ambiguous and can cause the researcher to choose the wrong data source (expecting local clones instead of API mode), which directly affects whether sibling commits are actually scanned in cluster environments.
Useful? React with 👍 / 👎.
|
Закрываю: fallback уже в скилле на
Обе правки из ревью Codex учтены: |
Add GitHub API fallback in scan-sibling-commits skill when local sibling clones are not available.
Fixes from codex P2: paginate GitHub commits API (per_page=50 was capped at 50 commits/repo);
now follows Link: rel="next" pagination up to 5 pages × 100 commits.