engram-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

The contribution policy transition is PRE-CUTOVER / NOT ACTIVE; the active rules below still apply.

1. Every PR MUST link an approved issue — no exceptions
2. Every PR MUST have exactly one type:* label
3. All required automated checks must pass before merge is possible
4. Blank PRs without issue linkage will be blocked by GitHub Actions
5. The PR targets the canonical repository, the branch lives in your fork — origin is your fork, upstream is the canonical repository. A push straight to the canonical repository is refused, either by permissions or by the ruleset with GH013; do not retry it or switch destinations silently
6. Applying the type:* label needs maintainer triage access on the canonical repository. When the API refuses, ask a maintainer instead of retrying