GitHub pull requests

Own the GitHub delivery record, not the implementation, code-review verdict, issue tracker, or release. Read the repository's policy before acting and keep every mutation within the authority granted by the task.

Authority boundary

Loading this skill grants no permission to commit, push, open a PR, publish a comment, submit a review, merge, or change repository settings.

• Reads are safe when they stay within the user's repository and task.
• A request to file, open, or deliver work through a PR normally authorizes pushing the named work branch and creating or updating that PR, subject to repository rules.
• Commit, push, PR creation, draft-state changes, review submission, comments, and merge are separate permissions. Follow the repository's ownership split rather than assuming one actor owns them all.
• Require fresh explicit authority for force-push, retarget, close or reopen, auto-merge, merge, branch deletion when it is not automatic, tags, releases, package publication, and repository settings.
• Never broaden a PR task into a release or deployment.