github-contribution-workflowlisted

# GitHub Contribution Workflow The `gh`-CLI contribution loop for an agent acting on a GitHub repo: branch → commit → PR → CI → merge, plus issues, GitHub-side file ops, repo secrets, and contribution-flow repo settings. Encodes conventions that keep an agent's contributions reviewable and consistent. Tool-agnostic in spirit; concrete commands are `gh` + `git`. ## Native mechanism Claude Code's [Hooks](https://code.claude.com/docs/en/hooks) can intercept and block a tool call before it runs — e.g. a `PreToolUse` hook matching `Bash` can deny a `git push --force` or a bare `rm -rf`. Hooks enforce a hard gate at the tool layer; the `--no-verify` rule and CLEAN-before-merge convention below are conventions this skill asks the agent to follow voluntarily where no hook exists to enforce them. ## When to invoke - Opening or merging a PR; opening or commenting on an issue. - Creating or editing a file *through GitHub* (API / web flow) rather than a local clone. - Setting a repo secret or configuring contribution-flow repo settings. - Checking CI status before a merge; bumping a submodule pin. - User says "open a PR / issue", "merge this", "set the secret", "configure the repo". ## Scope — what this does NOT own (route to sibling) - **Verifying the diff matches the commit's claims** before push/PR → `pr-diff-verification`. - **Security repo settings** (Secret Scanning, push protection, gitleaks, `.gitignore` baseline) → `apple-dev-skills:apple-public-repo-security`. - **Parall