github-bot-interaction
GitHub Bot Interaction
Purpose
Use the configured GitHub App for remote GitHub mutations and the configured bot author identity for commits. Never use ambient personal GitHub credentials for remote writes.
Required Capabilities
Requires shell execution, git, openssl, python3, date, grep, and a GitHub CLI or API client that honors GH_TOKEN. Keychain fallback additionally requires macOS security and xxd.
Configuration
Explicit non-empty environment inputs take precedence: GH_BOT_APP_ID, GH_BOT_INSTALLATION_ID, and GH_BOT_PRIVATE_KEY_PATH configure token minting; GH_BOT_GIT_NAME and GH_BOT_GIT_EMAIL configure commit identity. GH_BOT_PRIVATE_KEY_PATH must point to the GitHub App PEM file; never place private-key contents in an environment variable, command, skill file, log, or commit.
Each unset value falls back to its existing ai-skills.gh-bot.{app-id,installation-id,private-key,git-name,git-email} Keychain service. GH_BOT_KEYCHAIN_ACCOUNT selects the fallback account; otherwise $USER is used. An unreadable explicit key path or missing token fallback blocks remote writes. Missing git name or email blocks only flows that create commits. Neither failure permits personal credentials.