managing-githublisted

# Manage GitHub Use one safety contract, then load only the operation reference required by the request. ## Keep the ownership boundary explicit This skill owns externally stored GitHub issues, pull requests, pull-request reviews, releases, and their readback. It does not own local implementation, development planning, technical code-review judgment, generic branch maintenance, GitHub Actions design, repository settings, permissions, rulesets, secrets, or organization administration. The agent responsible for the overall outcome retains every GitHub mutation. A specialist may return a local branch, diff, commit, issue draft, pull-request draft, release recommendation, and evidence; it does not file, edit, push, tag, publish, request review, or follow up unless it is itself the responsible agent and the request authorizes that exact action. ## Trigger from the workflow, not only the request wording Load this skill when the active work reaches a GitHub-hosted boundary, including when: - investigation finds a repository defect that may need an issue, duplicate search, comment, or closure decision; - verified development work is ready for the repository's required branch push or pull-request path; - an existing pull request needs stored-state inspection, template or readiness review, an authorized review submission or update, or check follow-up; - a versioned change reaches the repository's release, tag, notes, asset, or branch-reconciliation contract; or - another