gentleman-programming/engram/branch-pr
Claude Code and agent skill by gentleman-programming/engram
- community
Checking that the SKILL.md file is still in the repository.
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
Install
npx vskill@latest install gentleman-programming/engram/branch-prSKILL.md
The same SKILL.md was published earlier as gentleman-programming/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.
- Every PR MUST link an approved issue — no exceptions
- Every PR MUST have exactly one `type:*` label
- All required automated checks must pass before merge is possible
- Blank PRs without issue linkage will be blocked by GitHub Actions
- The PR targets the canonical repository, the branch lives in your fork —
originis your fork,upstreamis the canonical repository. A push straight to the canonical repository is refused, either by permissions or by the ruleset withGH013; do not retry it or switch destinations silently - Applying the `type:*` label needs maintainer triage access on the canonical repository. When the API refuses, ask a maintainer instead of retrying
Workflow
Branch Naming (enforced by GitHub ruleset)
Branch names are validated by a GitHub ruleset. Pushes that don't match will be rejected.
Pattern: ^(feat|fix|chore|docs|style|refactor|perf|test|build|ci|revert)\/[a-z0-9._-]+$
| Type | Branch pattern | Example | |
|---|---|---|---|
| Feature | feat/<description> | feat/json-export-command | |
| Bug fix | fix/<description> | fix/duplicate-observation-insert | |
| Chore | chore/<description> | chore/bump-bubbletea-v0.26 | |
| Docs | docs/<description> | docs/api-reference-update | |
| Style | style/<description> | style/fix-tui-alignment | |
| Refactor | refactor/<description> | refactor/extract-query-sanitizer | |
| Performance | perf/<description> | perf/optimize-fts5-queries | |
| Test | test/<description> | test/add-sync-coverage | |
| Build | build/<description> | build/update-go-toolchain | |
| CI | ci/<description> | ci/split-e2e-job | |
| Revert | revert/<description> | revert/broken-migration |
Rules:
- Description MUST be lowercase
- Only
a-z,0-9,.,_,-allowed in description - No uppercase, no spaces, no special characters
PR Body Format
Use the canonical PR template as the source for body shape; do not duplicate its structure here. Describe the problem and result, record honest verification, and include risks and mitigations only when applicable.
Every PR body MUST contain a closing reference to an approved, assigned issue:
Valid keywords: Closes #N, Fixes #N, Resolves #N (case insensitive). Every linked issue MUST have status:approved and a real assignee. Approval means a maintainer accepted proportional evidence: scope/checks for trivial changes; current-remote-main SHA, reproduction, root cause, and regression tests for bugs; approved design, non-goals, and independent review for high-risk changes. Evidence can live in the issue; no separate design document is required by default.
Existing PRs must comply before merge, without waiting for backlog-wide migration. Re-run native validation after issue approval/assignment changes; do not rely on stale green checks.
Add exactly one canonical type:* PR label; no duplicate type checkbox is required in the body. All required automated checks must pass before merge; report other applicable checks honestly as described below.
Record actual verification commands/steps and observed outcomes, not assumed passes. For behavior changes, include focused regression and affected package tests. For docs-only changes, mark local Go tests N/A — documentation-only; no Go behavior changed and list the documentation checks actually run. Targeted coverage can help find missed branches; no total module coverage or per-PR numeric gate applies. Without a PR (or before pushing), and for high-risk changes, run additional applicable local checks. Identify checks not run and missing CI evidence; GitHub CI full unit/E2E/lint and applicable platform results remain pending until they run. Local success is not a hosted CI pass.
For high-risk changes, link the approved design, non-goals, and independent review evidence required by CONTRIBUTING. Omit the risk section for low-risk changes.
Automated Checks
The six required contexts are listed in CONTRIBUTING.md; all six must pass before merge. Lint, transient-artifact checks, Windows Setup Test, and Cloud Sync Wrapper Tests (Windows) run for PRs but not merge groups, and are not among the six required contexts. Report their actual outcomes without treating pending checks as passed.
| Check | Job name | What it verifies | |
|---|---|---|---|
| PR Validation | Check Issue Reference | Body contains Closes/Fixes/Resolves #N | |
| PR Validation | Check Issue Has status:approved | Every linked issue is approved and assigned | |
| PR Label Policy | Check PR Has type:* Label | PR has exactly one type:* label | |
| Transient Artifact Check | Check PR Has No Transient Artifacts | PR files comply with the Transient Artifact Policy | |
| CI | Unit Tests | go test ./... passes | |
| CI | E2E Tests | go test -tags e2e ./internal/server/... passes | |
| CI | Plugin Tests | npm test passes in plugin/pi | |
| CI | Lint | golangci-lint reports no new findings in Go changes | |
| CI | Windows Setup Test | Windows setup preserves absolute paths and MCP job-object parent-lifetime tests pass | |
| CI | Cloud Sync Wrapper Tests (Windows) | Cloud sync wrapper and missing-PowerShell-Engram tests pass on Windows |
Conventional Commits (enforced by GitHub ruleset)
Commit messages are validated by a GitHub ruleset. Commits that don't match will be rejected.
Pattern: ^(build|chore|ci|docs|feat|fix|perf|refactor|revert|style|test)(\([a-z0-9\._-]+\))?!?: .+
Format:
Allowed types
| Type | Purpose | PR label | |
|---|---|---|---|
feat | New feature | type:feature | |
fix | Bug fix | type:bug | |
docs | Documentation only | type:docs | |
refactor | Code refactoring | type:refactor | |
chore | Maintenance, deps | type:chore | |
style | Formatting, whitespace | type:chore | |
perf | Performance improvement | type:refactor | |
test | Adding/fixing tests | type:chore | |
build | Build system changes | type:chore | |
ci | CI/CD changes | type:chore | |
revert | Revert previous commit | (match original type) | |
feat! / fix! | Breaking change | type:breaking-change |
Rules
- Type MUST be one of the listed values
- Scope is optional, lowercase, allows
a-z,0-9,.,_,- !before:marks a breaking change- Description MUST start after
:(colon + space)
Examples
Invalid examples (will be rejected)
Commands
The --head <owner>:<branch> form supports user-owned forks only; GitHub CLI does not support an organization as <owner>. For an organization-owned fork, use GitHub's web pull-request flow and explicitly select the canonical base repository and branch, the fork, and the head branch before submitting.
Forks, Remotes, and Publication
A pull request targets the canonical repository. A fork is where the branch lives, not where the pull request opens.
| Remote | Points at | Holds | |
|---|---|---|---|
origin | your fork | your branches | |
upstream | the canonical repository | the canonical main |
This is the start of the file. Read the full SKILL.md on GitHub.
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/branch-pr/SKILL.md
Popularity
- Repository stars
- 4,550
- Repository forks
- 523
- 7-day trend score
- 42
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/gentleman-programming/engram/branch-pr)