Engram PR Workflow
Enforces an issue-first pull request workflow for the Engram repository, requiring every PR to link an approved issue and follow strict formatting rules.
The skill is a PR creation workflow, no sensitive data or high privilege, no malicious behavior. But it relies on GitHub Actions and rulesets for enforcement, and the file lacks explicit description of permissions, user confirmation, and data-flow transparency. Deductions: insufficient permission/confirmation details and transparency.
The instructions are self-consistent, but execution depends on external GitHub Actions and rulesets; static review cannot verify actual execution. Error handling is thin, e.g., what to do when issue lacks approved label. Deductions: static limitations and weak failure feedback.
Clear trigger (creating PR) and audience, but non-fit boundaries (e.g., non-GitHub) are not stated. Environment fit: no Chinese language support or network reachability mention; GitHub may be inaccessible in mainland China. Deductions: unclear boundaries and network concerns.
Documentation is well-structured with sections, but missing install notes, parameter history, FAQ, known limitations, and maintenance/update path. Deductions: hidden assumptions (repo already has template and rulesets), incomplete governance.
Describes the workflow but no evidence of actual successful PR creation, no output examples or alternative comparison. Static review max is 7, but given lack of direct usability evidence, score 5.
CI workflow and test commands exist, but no evidence they cover this skill's key paths. No changelog or releases for the skill. Deductions: insufficient corroborating evidence.
- This skill heavily depends on GitHub Actions and rulesets; it may not work outside GitHub or without those rules configured.
- The doc assumes the repo already has a PR template and automated checks; verify they exist before use.
- GitHub services may be inaccessible in mainland China, affecting suitability for users there.
What does this skill do, and when should you use it?
This skill defines a rigorous PR creation process for the Engram repository. All changes must link to an approved issue with a 'status:approved' label. It enforces strict branch naming conventions, a specific PR body format, type labels, and five mandatory automated checks. The skill also mandates Conventional Commits commit message format, with non-conforming commits rejected by GitHub rulesets. The entire workflow is enforced via GitHub Actions, blocking PRs that do not comply.
Guides the creation of PRs that meet Engram's repository requirements: verifies the linked issue is approved, names branches according to patterns like feat/* or fix/*, runs unit and e2e tests locally, fills in the PR body using the template (including linked issue, exactly one type label, changes table, test plan), adds a type:* label to the PR, and ensures all five automated checks pass. It also enforces Conventional Commits format, with branch and commit message validation handled by GitHub rulesets.
- When a developer prepares a feature branch for submission as a PR in the Engram repo, the skill ensures the branch name follows the feat/<description> pattern.
- When a developer needs to submit a bug fix, the skill guides them through creating a fix/ branch and linking an approved issue.
- When a first-time contributor submits code to Engram, the skill helps them avoid rejection due to incorrect branch naming or missing type:* labels.
- When a maintainer wants to ensure all PRs follow a consistent specification, this skill serves as a team-wide PR creation manual.
What are this skill's strengths and limitations?
- Strict automated checks ensure traceability of every change to an approved issue.
- Enforced branch naming and commit formats keep the repository clean.
- Clear PR template and checklist improve collaboration efficiency.
- Consistency enforced via GitHub Actions and rulesets.
- Heavily tailored to the Engram repo; reuse requires adapting issue labels and check names.
- Strict requirements may feel heavy for trivial changes or hotfixes.
- No support for non-GitHub platforms mentioned.
- Undocumented how to use the skill outside the repo; external users must adapt.
How do you install this skill?
This skill is part of the Engram repository, located under skills/branch-pr/ (actual file: skills/branch-pr/SKILL.md). To use it in another project, copy this SKILL.md to the project's .claude/skills/ directory or reference the repo with Claude Code. Exact installation steps are undocumented but follow the standard Agent Skills folder structure.
How do you use this skill?
When ready to create a PR, include a trigger prompt like 'create a pull request for this change'. The skill will guide you through checking issue approval, branching, local tests, PR body template, and label addition. Steps: verify issue has 'status:approved', create a branch (e.g., feat/my-feature), implement changes, run go test ./... and go test -tags e2e ./internal/server/..., push, use gh pr create with proper title and body, then add a label with gh pr edit.