skills.rest
gautam-achieveai
gautam-achieveaiCOMMUNITY
Explore all skills by this author →
GitHub

pr-context

Extract full business context from pull requests by walking issue hierarchies on GitHub or Azure DevOps.

2|Updated Apr 12, 2026
Search Tags:#code review#github#azure devops#business context#pr-context#issue hierarchy
One-click install
npx skills add https://github.com/gautam-achieveai/ClaudePlugins --skill pr-context-gautam-achieveai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-context
Source: https://github.com/gautam-achieveai/ClaudePlugins/tree/main/code-reviewer/skills/pr-context
Command: npx skills add https://github.com/gautam-achieveai/ClaudePlugins --skill pr-context-gautam-achieveai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ado:setup-ado-mcp, gh:setup-gh-mcp, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Understanding the context behind a pull request, such as the full issue/work item hierarchy on GitHub or Azure DevOps, can be time-consuming. This Skill streamlines this process.

Core Features & Use Cases

  • Full Business Context: Walks the issue/work item hierarchy for a PR, providing a comprehensive understanding of its purpose and placement within a larger project.
  • Use Case: During code review, you need to know the why behind the PR and what larger features or issues it affects.

Quick Start

Gather the full business context for PR number 1234 using the /pr-context command.

Frequently Asked Questions about pr-context

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

FAQPage Schema
How do I get full business context for a pull request during code review?▼

To get business context for a pull request, you can traverse the issue and work item hierarchy. This provides a comprehensive understanding of the PR's purpose and its placement within larger project objectives.

How does traversing an issue hierarchy help with reviewing code changes?▼

Traversing an issue hierarchy helps reviewing code changes by linking the pull request to its parent features or epics. This ensures reviewers understand the broader impact and the why behind the modifications before approving.

Can I use this to extract work item context from both GitHub and Azure DevOps?▼

Yes, you can extract work item context from both GitHub and Azure DevOps. The Skill traverses the issue and work item hierarchy on either platform to gather the necessary PR context for reviewers.

Do I need to set up MCPs to gather PR context?▼

Yes, you need to set up MCPs to gather PR context. The Skill requires the ado:setup-ado-mcp and gh:setup-gh-mcp dependencies to access Azure DevOps and GitHub APIs for walking the work item hierarchy.

What is the best way to understand the impact of code changes on project objectives?▼

The best way to understand the impact of code changes on project objectives is to extract the full business context of a PR. Walking the issue hierarchy reveals how the changes affect larger features and project goals.

Related Skills

Explore More Software Engineering Skills→
gautam-achieveaigautam-achieveai
2

ado-work-items

Automate Azure DevOps work item creation, querying, updating, and linking.

Community
Intermediate
EnigmaWUEnigmaWU
1

build-business-objectives-model

Construct a Business Objectives Model from project kickoff documents.

Community
Advanced
Progery222Progery222

github-workflow-automation

Automate GitHub repository management, CI/CD pipelines, and pull request workflows.

Community
Advanced
GabeujinGabeujin

breakdown-plan

Generate GitHub project plans and issue templates from feature artifacts.

Community
Advanced