proompteng/lab

pr-process

Prepare, publish, inspect, and merge pull requests in this repository. Use when creating or updating a PR, checking merge readiness, or merging an approved change.

First seen Jan 24, 2026

Installation

$ npx skills add proompteng/lab --skill pr-process

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from proompteng/lab · top by installs.

npx skills add proompteng/lab

Browse all from proompteng/lab

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Also listed on

Alternate registries and mirrors of this skill.

Repository health

Stars 8
License LICENSE
Default branch main
Open issues 10
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,460 B
  • docs SUMMARY.md 181 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 67 installs

SKILL.md

Pull Request Process

Use this as the repository's single workflow for pull requests. Use github-issue for issue-only work.

Workflow

  1. Establish the exact local branch, HEAD, current PR, and base branch. Treat UI state as a lead, not proof.
  2. Prepare a Conventional Commit and matching PR title. Fill .github/PULLREQUESTTEMPLATE.md with only the actual change, validation, risks, and rollout impact.
  3. Run focused local validation before publishing. Stage only owned paths.
  4. Check the remote PR's exact head, required checks, review threads, conflicts, and merge state. Fix failures in the owning layer and recheck the resulting head.
  5. Create, push, update, resolve, or merge externally only when the user requested that mutation. Bind squash merges to the verified head with --match-head-commit, and do not delete branches from shared worktrees.
  6. Report the verified head, PR state, validation evidence, and any remaining blocker.

Resources

  • Read [references/pr-process.md](references/pr-process.md) for concrete PR commands.
  • Use scripts/pr-create.sh only when the user asked to create a PR. It refuses to submit an unchanged template.
  • Use [assets/pr-checklist.md](assets/pr-checklist.md) for a compact readiness audit.