skills.rest
lgtm-hq
lgtm-hqOFFICIAL
Explore all skills by this author →
GitHub

which-pr

Detect pull request numbers, titles, URLs, branches, and paths in conversation history.

Updated Aug 23, 2026
Search Tags:#git#development#pull request#pr#conversations
One-click install
npx skills add https://github.com/lgtm-hq/claude-skills --skill which-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: which-pr
Source: https://github.com/lgtm-hq/claude-skills/tree/main/skills/which-pr
Command: npx skills add https://github.com/lgtm-hq/claude-skills --skill which-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps users determine which pull request is being referenced during a conversation, enabling clearer context and communication.

Core Features & Use Cases

  • PR Identification: Recognizes PR numbers, titles, branch names, URLs, and worktree paths discussed in conversation history.
  • Context Verification: Reports whether any PR has been mentioned, avoiding ambiguous references.
  • Use Case: A developer reviews a conversation and wants to quickly see which PR is being discussed without executing any git commands, ensuring context clarity.

Quick Start

Look through the conversation history to identify and report the current PR details based on the discussed branch, PR number, or URL.

Frequently Asked Questions about which-pr

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

FAQPage Schema
How do I identify which pull request is being discussed in a conversation?▼

To identify which pull request is being discussed, this Skill analyzes conversation history to detect and report current PR details. It extracts PR numbers, titles, URLs, branch names, and worktree paths to maintain context clarity without executing git commands.

What pull request details can I extract from chat history without running git commands?▼

You can extract pull request numbers, titles, URLs, branch names, and worktree paths from chat history. This Skill reports these PR details directly from conversation context to help track code review discussions without executing any git commands.

How do I verify if a specific branch name mentioned in a conversation links to an active pull request?▼

To verify if a mentioned branch name links to an active pull request, this Skill scans the conversation history for context. It accurately identifies PR details by matching the discussed branch names, PR numbers, or URLs without needing to run development commands.

Does this PR identification tool execute git commands to check the integration status?▼

No, this PR identification tool does not execute git commands to check integration status. It strictly analyzes conversation history to report pull request details, ensuring developers can track discussions and verify context safely without running any code.

What is the best way to track pull request context in team communication without leaving the chat?▼

The best way to track pull request context in team communication is by analyzing the chat history. This Skill detects and reports current PR details like numbers and branch names from conversations, aiding developers in maintaining clarity during code reviews.

Related Skills

Explore More Software Engineering Skills→
bs-koobs-koo

pull-request

Automates GitHub Pull Request creation from commit history and branch analysis.

Community
Advanced
rkz91rkz91
264

gsd-ship

Push a feature branch, create a pull request with an auto-generated body, and track merge status.

Community
Advanced
paultyngpaultyng
9

set-session-context

Configure agent session names and colors from git branch and pull request context.

Community
Intermediate
encero-systemsencero-systems
92

create-pr-description

Generate PR descriptions from repository templates and git diff changes.

Official
Intermediate