skills.rest
bitsocialnet
bitsocialnetOFFICIAL
Explore all skills by this author →
Website𝕏@bitsocialnetGitHub

review-and-merge-pr

Triage GitHub PR feedback, apply fixes, and merge when checks pass.

1|1|Updated Feb 1, 2026
Search Tags:#automation#github#merge#review#triage#code-review#pull-request
One-click install
npx skills add https://github.com/bitsocialnet/bitsocial-web --skill review-and-merge-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-and-merge-pr
Source: https://github.com/bitsocialnet/bitsocial-web/tree/main/.cursor/skills/review-and-merge-pr
Command: npx skills add https://github.com/bitsocialnet/bitsocial-web --skill review-and-merge-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review an open GitHub pull request, inspect bot and human feedback, decide which findings are valid, implement fixes on the PR branch, and merge the PR into master when it is ready. Use when the user says "check the PR", "address review comments", "review PR feedback", or "merge this PR".

Core Features & Use Cases

  • Identify the target PR and determine whether a merge is safe based on checks and reviews.
  • Gather and triage signals from automated bots and human reviewers to decide which findings require action.
  • Apply fixes on the PR branch, document decisions, and merge only when all blockers are resolved and remaining items are non-blocking or explicitly deferred.
  • Use Case: When a feature branch has an open PR and CI checks pass, you can review comments, push fixes, and merge to master.

Quick Start

Review the open PR on bitsocialnet/bitsocial-web and begin triaging feedback immediately.

Frequently Asked Questions about review-and-merge-pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically triage and merge a GitHub pull request?▼

To automatically triage and merge a GitHub pull request, this Skill identifies the target PR, reads CI checks and human reviews, applies valid fixes on the branch, and safely merges when all blockers are resolved.

Can I push code fixes directly to a PR branch based on review comments?▼

Yes, you can push code fixes directly to a PR branch based on review comments. The Skill inspects bot and human feedback, determines which findings are valid, and implements those fixes directly on the pull request branch.

What is the safest way to merge a pull request after addressing review feedback?▼

The safest way to merge a pull request after addressing review feedback is to block on must-fix issues. This Skill enforces safe merge practices by only merging when all blockers are resolved and remaining items are non-blocking or explicitly deferred.

How does automated PR triage handle blocking issues from CI checks and reviewers?▼

Automated PR triage handles blocking issues by reading CI checks and reviewer signals, deciding which findings require action, and blocking the merge until those must-fix issues are resolved and documented.

Do I need passing CI checks before automating a pull request merge to master?▼

Yes, you need passing CI checks before automating a pull request merge to master. The Skill determines whether a merge is safe based on the status of CI checks and human reviews before applying fixes and merging the branch.

Related Skills

Explore More Software Engineering Skills→
daodaoedudaodaoedu

collect-pr-feedback

Collect and consolidate GitHub pull request feedback and CI check statuses.

Official
Intermediate
hongmaple0820hongmaple0820
9

github-pr-merge

Merge GitHub Pull Requests after validating pre-merge checks and cleanup.

Community
Advanced
treejhtreejh

hunt

Diagnose root causes of errors and failing tests with evidence-based hypotheses.

Community
Advanced
minfengyuanminfengyuan
1

finishing-a-development-branch

Verify tests, then merge, push, preserve, or discard a feature branch.

Community
Intermediate