Loading...

engram-branch-pr

Original：🇺🇸 English

Translated

Branch and PR workflow for Engram contributors. Trigger: When starting any change that will be proposed through GitHub.

2installs

Sourcegentleman-programming/engram

Added on2026-03-01

NPX Install

npx skill4agent add gentleman-programming/engram engram-branch-pr

Tags

Translated version includes tags in frontmatter

github-workflow pr-management branch-strategy code-review merge-checklist

SKILL.md Content

View Translation Comparison →

When to Use

Use this skill when:

Starting a new feature, fix, or refactor
Splitting work into multiple PRs
Preparing a PR for review and merge

Core Rules

Create a focused branch (
```
feat/*
```
,
```
fix/*
```
,
```
chore/*
```
).
Keep one logical scope per branch.
Push early and often to avoid large risky diffs.
Open PRs with intent, risk, and validation evidence.
Do not mix unrelated changes in the same PR.

PR Structure

Include:

Problem statement (why this change exists)
Solution summary (what changed)
Risk notes (what could break)
Validation (tests/commands executed)
Follow-ups (what is intentionally out of scope)

Merge Checklist

Branch name matches scope
Diff is focused and reviewable
Tests relevant to the change pass
No temporary files or local artifacts included
PR description explains why, not only what