pr-completion

Verify GitHub Actions checks and resolve merge conflicts for pull requests.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/kamushadenes/nix --skill pr-completion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-completion
Source: https://github.com/kamushadenes/nix/tree/main/home/common/ai/resources/claude-code/skills/pr-completion
Command: npx skills add https://github.com/kamushadenes/nix --skill pr-completion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams ensure that every pull request meets all checks and is free of conflicts before moving tasks to done, reducing review cycles and merge issues.

Core Features & Use Cases

  • Checks verification: Verify GitHub Actions PR checks pass before merging.
  • Conflict resolution: Detect and resolve merge conflicts for PR branches.
  • Use Case: After creating a PR for a feature, run this Skill to verify checks and clean up conflicts before marking tasks complete.

Quick Start

Use the PR Completion Workflow to check PR checks and resolve conflicts for a PR you are finishing.

Frequently Asked Questions about pr-completion

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

FAQPage Schema
How do I check if a GitHub pull request passes all checks before merging?

You can verify GitHub Actions PR checks by using the gh CLI to query check statuses, ensuring all required validations pass before marking the pull request as done.

How do I resolve merge conflicts in a pull request branch?

To resolve merge conflicts in a pull request, use git to identify conflicting files, manually edit them to reconcile differences, and commit the resolution to clean up the PR branch.

Do I need the gh CLI to verify pull request mergeability?

Yes, the gh CLI is required to verify PR checks and assess mergeability, while git is used for conflict resolution during the pull request completion workflow.

What's the best way to automate pull request completion and reduce review cycles?

Automating pull request completion involves running a workflow that checks GitHub Actions statuses and resolves conflicts before finalizing tasks, reducing review cycles and merge issues.

Why does my pull request have merge conflicts after passing all checks?

A pull request can pass all GitHub Actions checks but still have merge conflicts if the base branch has new commits that clash with your branch, requiring git conflict resolution before merging.