move-pr-forwards

Analyzes GitHub PR status, approver feedback, and failing CI logs to unblock pull requests.

1.1k|377|Updated Apr 8, 2019
One-click install
npx skills add https://github.com/GoogleCloudPlatform/k8s-config-connector --skill move-pr-forwards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: move-pr-forwards
Source: https://github.com/GoogleCloudPlatform/k8s-config-connector/tree/main/.gemini/skills/move-pr-forwards
Command: npx skills add https://github.com/GoogleCloudPlatform/k8s-config-connector --skill move-pr-forwards

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Pull requests in mature repositories like Kubernetes Config Connector often stall due to failing CI checks, merge conflicts, or pending feedback from project approvers. This Skill automates the diagnosis of a stalled PR so an agent can identify exactly what is blocking it and apply the right fix.

Core Features & Use Cases

  • PR Status Inspection: Runs a Python helper script that fetches PR metadata, merge state, and review decisions via the GitHub CLI.
  • Approver Feedback Filtering: Extracts comments and reviews specifically from KCC project OWNERS so critical maintainer feedback is never missed.
  • CI Log Analysis: Fetches failing GitHub Actions job logs and extracts actionable <hint_for_agent> directives, FAIL: messages, or ERROR lines.
  • Use Case: An agent is asked to move PR #8426 forward. It runs the check script, discovers a failing e2e fixture test with a hint to run a presubmit script, regenerates the golden output, commits, and pushes the fix.

Quick Start

Ask the agent to analyze and move forward pull request number 8426 using the move-pr-forwards skill.

Frequently Asked Questions about move-pr-forwards

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

FAQPage Schema
How do I diagnose a stalled GitHub pull request automatically?

Run the check-pr.py helper script with the PR number to fetch PR metadata, merge state, approver comments, and failing CI check logs in one structured summary. It highlights exactly what is blocking the merge and suggests next actions.

How to find actionable fixes in failing GitHub Actions logs?

The script fetches the full job log for each failing check and scans for <hint_for_agent> directives first, then FAIL: lines, then ERROR lines. Strong hints usually point to a presubmit script that regenerates golden files or fixes formatting.

Does this tool require the GitHub CLI to be installed?

Yes, the check-pr.py script relies on the gh CLI to fetch PR metadata, checks, and job logs. You must have gh installed and authenticated against the target repository before running the script.

How does the skill filter feedback from project approvers?

The script maintains a hardcoded list of KCC OWNERS approver usernames and filters PR comments and reviews to show only their feedback. This ensures maintainer requests are prioritized over automated bot comments.

What should I do when a PR has merge conflicts or is behind the base branch?

The script prints rebase instructions when the PR is CONFLICTING, BEHIND, or DIRTY. Check out the PR with gh, rebase onto the base branch, resolve conflicts, and force-push with --force-with-lease.