merge-check - Assess whether a pull request is safe to merge
Summarizes a pull request, verifies merged behavior, checks regressions, builds, tests, and CI, then lists screens for manual review.
Tags
Updated: 2026-10-12Capabilities
Typical Inputs
Typical Outputs
What this skill does
- Summarize pull request changes
- Verify merged build and tests
- Inspect regression risks
- Check CI failures
- Assess intended behavior
- List screens for manual review
- Report merge readiness
Inputs
- Pull request link or linked branch
- Repository source and history
- Upstream master state
- GitHub PR metadata and CI results
- Local working tree state
- Repository review rules
Outputs
- Pull request change summary
- Build, test, lint, and CI results
- Regression findings
- Mergeability assessment
- Manual screen checklist
- Unverified items requiring confirmation
Requirements
- Git installed
- GitHub CLI access
- Repository read access
- Yarn workspace dependencies
- Upstream master remote
- Backend at localhost:8080 for data-backed dev checks