manage-pull-requests

Automate Harness Code pull request workflows via MCP to list, create, update, and merge PRs.

80|16|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/harness/harness-skills --skill manage-pull-requests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manage-pull-requests
Source: https://github.com/harness/harness-skills/tree/main/skills/manage-pull-requests
Command: npx skills add https://github.com/harness/harness-skills --skill manage-pull-requests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing Harness Code pull requests across multiple repositories is error-prone and manual. This Skill orchestrates PR workflows via MCP to streamline listing, creating, updating, merging PRs, and handling reviews, comments, and checks in a consistent, automated fashion.

Core Features & Use Cases

  • List PRs in a repo and filter by state using MCP.
  • Create new pull requests with titles and descriptions.
  • Update PR metadata (title, description, state) and merge PRs using various methods.
  • Manage reviewers: add reviewers and submit reviews (approve / request changes).
  • Post, update, and delete comments; read the discussion timeline.
  • Inspect CI status checks on a PR head to determine merge readiness.

Quick Start

Open a PR from feature/foo into main with a concise title and description.

Frequently Asked Questions about manage-pull-requests

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

FAQPage Schema
How do I automate pull request workflows across multiple repositories?

You can automate pull request workflows across multiple repositories by using MCP to orchestrate listing, creating, updating, and merging PRs, as well as managing reviewers and comments consistently.

Can I assign reviewers and approve code changes using MCP?

Yes, you can assign reviewers and approve code changes using MCP. The workflow supports adding reviewers, submitting reviews, approving changes, or requesting modifications directly through MCP tools.

How do I check CI status on a pull request head to determine merge readiness?

To check CI status on a PR head, you can inspect CI status checks directly through the MCP workflow. This allows you to verify whether all required checks have passed before determining merge readiness.

What is the best way to manage PR comments and read the discussion timeline?

The best way to manage PR comments is through MCP, which allows you to post, update, and delete comments, as well as read the full discussion timeline to track review progress.

Does this approach require any specific dependencies to manage Harness Code PRs?

No specific dependencies are required to manage Harness Code PRs. The Skill operates independently using MCP tools like harness_create, harness_update, and harness_comment to execute PR actions.