GitHub Organization Scope

Ensures all gh CLI and GitHub interactions are scoped to the user's organization. Activates before any gh command or GitHub PR, issue, or notification interaction.

HARD RULE — no size or surface exemption. Every gh write fires this skill: gh pr create, gh pr edit, gh pr comment, gh issue comment, gh api POST/PATCH/DELETE, gh pr review, reply posts, thread resolutions. "It's just a comment" / "it's one-line" / "the user asked for it inline" are not bypass criteria. Read-only gh calls (view, diff, search, api GET) still honor Step 1–2 scoping but skip Step 4 (no body to footer).

Step 0: Select stored vs environment credentials

• GH_TOKEN, then GITHUB_TOKEN, take precedence over stored credentials. Never print or inspect token values.
• User explicitly confirms stored/keyring authentication → preserve the login-shell environment, but remove both token variables at every final gh command boundary. Skip gh auth status and credential refresh: