open-pull-requestlisted

# Open Pull Request This skill governs how Claude pushes a branch and opens a pull request. **Pushing a feature branch and opening a PR never need permission — do both as soon as a branch has a commit, and open the PR as a _draft_ if the work is not review-ready.** A branch and a (draft) PR harm nothing: they touch no shared history and request no review, while leaving committed work unpushed risks losing it to a crashed session. See `git-conventions` → "Branch and PR freedom" for the underlying rule. The one hard prohibition is upstream: **never push to `master`/`main` without explicit consent** (`git-conventions`). Most contributors cannot; on an admin account it is your guardrail to hold. So the pre-flight below gates on _quality_ (lint, tests, a clean tree), not on _permission_. When a check fails you fix it, not ask to skip it. And "not review-ready" is never a reason to withhold a PR — it is the reason to open a **draft** one, which has no rules (force-push, redirect, or delete it freely). Every PR in this repo follows the same contract: Conventional-Commits title, structured body, correct base, and no manual reviewer/assignee assignment (workflows handle that). --- ## Phase 1: Pre-Flight Checks Before any push or PR creation, verify all of the following. If any check fails, stop and surface the problem to the user instead of pushing. ### 1.1 You are on a feature branch ```bash git rev-parse --abbrev-ref HEAD ``` Must return something like `feat/dao/revoke-key