Gator Gate

Validate OpenShell GitHub issues and pull requests for project fit, then monitor valid PRs until they are ready for maintainer approval.

This skill is a gating workflow. It can start from any issue or PR state, inspect the current gator:* label, and continue the correct next action.

Skill Location

Codex and other agent harnesses should load this skill from the repository path scripts/agents/gator/skills/gator-gate/SKILL.md. After this branch is merged, the canonical GitHub location is https://github.com/NVIDIA/OpenShell/blob/main/scripts/agents/gator/skills/gator-gate/SKILL.md.

Prerequisites

• The gh CLI must be able to call GitHub APIs (gh api user --jq '.login')
• You must be in the OpenShell repository root
• GitHub write permissions are required to apply labels, comment, close issues/PRs, or post /ok to test

Do not use gh auth status as the authentication health check inside provider-backed sandboxes. Scoped provider tokens may be exposed as openshell:resolve:env:* placeholders and gh auth status probes endpoints outside the gator policy, causing false "token is invalid" reports even when allowed gh api and gh pr calls succeed. Use gh api user --jq '.login' and a repo-scoped probe instead.

Use REST-backed gh api for GitHub write actions inside gator sandboxes. Do not rely on gh issue edit, gh pr edit, or other high-level write commands when a REST path is available, because some of them use GraphQL mutations and gator policy allows GraphQL reads only. Do not fall back to curl for credentialed GitHub writes unless the active provider policy explicitly allows the curl binary for the same scoped endpoint. Preferred write shapes: