Review A Contributor PR
Review a fork PR, review an external contributor PR, check provenance (DCO) and ee/...
Install
npx skills add different-ai/openwork --skill review-a-contributor-pr -g -a claude-code -y- Repository
- different-ai/openwork24.4k
- Category
- Testing
- Updated
- 3d ago
- License
- See repository
- Context cost
- Mediumabout 2,838 tokens
- Runs scripts
- No, instructions only
What it does
Review a fork PR, review an external contributor PR, check provenance (DCO) and ee/ CLA, run /test, carry a fork commit into a same-repo branch, is this PR safe to merge. Checklist for pull requests from forks before a human approves or merges them.
Skill: review-a-contributor-pr
Use for every PR whose head is not in different-ai/openwork
(isCrossRepository: true). Fork PRs get no automatic clearance: warden.yml
skips them (head.repo.full_name == github.repository, no secrets on fork
heads) and warden-clearance.yml refuses them. As at GitLab, contributing
means accepting the DCO, or the Individual or Corporate CLA for ee/
(CONTRIBUTING.md). There is no Signed-off-by requirement, no CLA signature
and no label to enforce.
The contributor flow is fork-only, including fork bots. Same-repository
PRs use normal CI and review, with no contributor merge status or /test.
The merge safeguards are the required openwork-tests-required and
warden-clear checks plus trusted maintainer review. warden-clear is
Warden's verdict on the head, posted by the diff-warden App; for forks it
appears after /test runs the sandboxed review. The fork screen and AI
screen statuses are advisory.
Everything below runs from dev and never executes PR code:
