skills.rest
wooyek
wooyekCOMMUNITY
Explore all skills by this author →
Website𝕏@wooyekGitHub

dev10x-gh-context

Detect GitHub Pull Request context via GitHub API calls, avoiding local git state inaccuracies.

Updated Aug 23, 2026
Search Tags:#automation#git#context#pull request#github#cli#issue tracking
One-click install
npx skills add https://github.com/wooyek/dev10x-ai --skill dev10x-gh-context
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev10x-gh-context
Source: https://github.com/wooyek/dev10x-ai/tree/main/codex-skills/dev10x-gh-context
Command: npx skills add https://github.com/wooyek/dev10x-ai --skill dev10x-gh-context

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that GitHub actions correctly identify the target Pull Request (PR) context, especially in complex multi-worktree setups, preventing errors and ensuring operations target the right PR.

Core Features & Use Cases

  • Accurate PR Detection: Reliably determines the PR number, repository, URL, and branch from various inputs like URLs, PR numbers, or the current branch.
  • Avoids Local Git Pitfalls: Crucially, it avoids using local git branch --show-current which can be misleading in multi-worktree environments, instead fetching branch information directly from GitHub.
  • Issue Tracker Identification: Includes a helper script to detect the issue tracker type (GitHub, Linear, Jira) based on ticket ID prefixes and GitHub autolinks.

Quick Start

Use the dev10x gh context skill to detect the PR number and repository from the URL https://github.com/owner/repo/pull/123.

Frequently Asked Questions about dev10x-gh-context

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

FAQPage Schema
How do I get GitHub PR context in a multi-worktree environment?▼

To get GitHub PR context in a multi-worktree environment, use a detection script that queries the GitHub API for the PR number, repository, URL, and branch, bypassing misleading local git state.

Why does local git branch detection fail for pull request automation?▼

Local git branch detection fails for pull request automation because commands like `git branch --show-current` can be misleading in multi-worktree setups, causing operations to target the wrong PR.

How to detect issue tracker type from ticket IDs for GitHub, Linear, and Jira?▼

You can detect issue tracker types like GitHub, Linear, and Jira by using a helper script that identifies the source tracker based on ticket ID prefixes and configured GitHub autolinks.

Can I extract a PR number and repository directly from a GitHub URL?▼

Yes, you can extract a PR number and repository directly from a GitHub URL by passing the URL to the context detection script to accurately parse and return the specific PR details.

What is the best way to ensure GitHub actions target the correct pull request?▼

The best way to ensure GitHub actions target the correct pull request is prioritizing GitHub API calls over local Git state to accurately determine the PR number, repository, URL, and branch.

Related Skills

Explore More Software Engineering Skills→
gqf2008gqf2008

github-auth

Authenticate Hermes Agent with GitHub via gh CLI or git tokens and SSH keys.

Community
Intermediate
breakingcircuits1337breakingcircuits1337

github

Automate GitHub issue and pull request management using the gh CLI.

Community
Intermediate
marcuskroghmarcuskrogh

tracker

Standardize issue lifecycle operations across GitHub, Jira, Linear, and Markdown backends.

Community
Advanced
team-attentionteam-attention
282

create-pr

Create GitHub pull requests from the current branch using the GitHub PR API.

Official
Advanced