github-pr-fix

GitHub PR Fix Skill

Summary

Use this skill when you need to remediate an existing pull request: diagnose what is broken, apply targeted fixes, push commits, and reply on review threads.

When To Use

• Fixing CI failures on an existing PR
• Addressing requested changes or review feedback
• Updating the PR branch and publishing review replies

Do Not Use

• Opening a brand-new PR from an issue
• Performing a review-only pass without code changes
• Project-wide triage or roadmap planning

Prerequisites

• gh CLI authentication is required.
• GITHUB_TOKEN/GH_TOKEN must allow PR read-write operations.

Runtime Paths

• GITHUB_OUTPUT_DIR: optional caller-provided output artifacts directory.
• GITHUB_CONTEXT_DIR: context directory (default ${GITHUB_OUTPUT_DIR}/github-context).
• Do not create fixed output files unless the caller or an integration explicitly requires them.

Inputs (Manifest-First)

Preferred input when already available:

• ${GITHUB_CONTEXT_DIR}/manifest.json

Optional inputs:

• Any artifact listed as status=present in manifest.artifacts[].

If no manifest is provided, collect PR context directly with gh:

gh pr view <pr_number> --repo <owner/repo> --json number,title,body,state,url,baseRefName,headRefName,headRefOid,author,createdAt,updatedAt,mergeable,reviews,changedFiles,additions,deletions
gh pr view <pr_number> --repo <owner/repo> --json files
gh api repos/<owner>/<repo>/issues/<pr_number>/comments --paginate
gh api graphql -f query='
  query($owner:String!, $repo:String!, $number:Int!) {
    repository(owner:$owner, name:$repo) {
      pullRequest(number:$number) {
        reviewThreads(first:100) {
          nodes {
            isResolved
            comments(first:100) {
              nodes { id body path line author { login } }
            }
          }
        }
      }
    }
  }' -F owner=<owner> -F repo=<repo> -F number=<pr_number>

Do not assume fixed github/*.json files. Resolve available context through artifact metadata (id, path, status, description).