github-pr

Coordinate GitHub Pull Request workflows with context extraction and branch synchronization.

3|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Cogni-AI-OU/cogni-ai-agent-skills --skill github-pr-cogni-ai-ou
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: github-pr
Source: https://github.com/Cogni-AI-OU/cogni-ai-agent-skills/tree/main/github-pr
Command: npx skills add https://github.com/Cogni-AI-OU/cogni-ai-agent-skills --skill github-pr-cogni-ai-ou

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

github-pr prevents common automation mistakes when working on GitHub Pull Requests by enforcing correct context handling, safe branching/sync behavior, and reliable PR communication patterns.

Core Features & Use Cases

  • PR context routing: Extracts and uses the provided Pull Request Context (including explicit base branch targeting) to ensure updates apply to the correct PR branch and reference points.
  • Safe PR-thread replies: Routes responses back through the originating PR comment or review channel using the gh CLI/API instead of writing comment text into the workspace.
  • Upstream sync with guardrails: Requires a structured pre-completion upstream sync flow (including merge-based pulling with --no-rebase) to reduce rejected pushes and keep history intact.
  • Revert/correct support: When asked to revert or fix previous work, retrieves the original prompt and prior agent execution signals (logs and PR diffs) before revising changes.

Quick Start

Use the github-pr skill when your agent is triggered by a Pull Request comment and needs to review, update, or synchronize the PR branch with its base while posting any feedback back to the correct PR thread.

Frequently Asked Questions about github-pr

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

FAQPage Schema
How does branch synchronization work when updating a pull request?ā–¼

Branch synchronization works by enforcing a pre-completion upstream sync flow using merge-based pulling with --no-rebase. This approach reduces rejected pushes, keeps commit history intact, and ensures test and verify steps run before completion.

Can I revert changes made by an automated agent on a GitHub pull request?ā–¼

Yes, you can revert automated agent changes by retrieving the original prompt and prior execution logs alongside PR diffs. The skill uses these prior signals to revisit, correct, or revert modifications made during previous workflow runs.

Does github-pr support posting review feedback directly to the pull request thread?ā–¼

Yes, posting review feedback is supported by routing responses back through the originating PR comment or review channel via the gh CLI/API instead of writing text into the workspace, ensuring correctly threaded communication.

Why do my automated pull request pushes get rejected after upstream merges?ā–¼

Automated pull request pushes get rejected when branch syncing lacks proper merge semantics. This skill enforces structured pre-completion upstream syncs with merge-based pulling to prevent rejected pushes and maintain workspace cleanliness.