Gentle AI Branch PR

When to Use

Use this skill when:

• Creating a pull request for any change
• Preparing a branch for submission
• Helping a contributor open a PR

---

Critical Rules

1. Every PR MUST link an approved issue, no exceptions
2. Every PR MUST have exactly one type:* label
3. REQUIRED CI must pass according to target policy before merge; CodeRabbit is optional unless required by that policy
4. Blank PRs without issue linkage will be blocked by GitHub Actions

---

Target and Authorization

• Inspect origin locally (git remote get-url origin) and establish one unambiguous target host and owner/repo. Do not infer the target from the cwd or assume main. Stop if ambiguous.
• Obtain explicit remote destination, operation and credential/session authorization before any target-host reads, including gh auth status or repository metadata. Do not inspect or reuse an ambient SSH agent. Permission for a read does not authorize a write; confirm each remote operation is within the grant.
• Once authorized, reuse fresh target-bound issue, default branch, type labels and checks evidence from this session instead of repeating discovery. Refresh stale or mismatched evidence; do not substitute another host's data. Resolve the base from the authorized target's default branch or a human-selected base.
• Do not automatically commit, push, open a PR or merge. Prepare and report a candidate; perform each action only with its own authorization. Local preparation is not permission for remote delivery.

Workflow