skills.rest
unblocked
unblockedOFFICIAL
Explore all skills by this author →
WebsiteGitHub

unblocked-context-search-prs

Semantically search PR descriptions and review discussions for code change history.

11|1|Updated Feb 11, 2026
Search Tags:#github#semantic search#change history#code reasoning#pr search
One-click install
npx skills add https://github.com/unblocked/skills --skill unblocked-context-search-prs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: unblocked-context-search-prs
Source: https://github.com/unblocked/skills/tree/main/skills/unblocked-context-search-prs
Command: npx skills add https://github.com/unblocked/skills --skill unblocked-context-search-prs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Navigates the intricate reasoning behind code changes, aiding in understanding the historical context and decision-making process without the noise of additional document sources.

Core Features & Use Cases

  • PR-Specific Semantic Search: Focuses solely on PR descriptions and review discussions, filtering out noise from other sources like Slack or documentation.
  • Tracing Change Histories: Identifies the origin of a code behavior, tracing back changes to specific PRs.
  • Use Case: When you want to know the 'why' behind a code implementation, understand the change history of a behavior, or investigate previous decisions about a PR.

Quick Start

Query the 'context_search_prs' with your query, for example: context_search_prs --query "Why was feature X implemented?".

Frequently Asked Questions about unblocked-context-search-prs

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

FAQPage Schema
How do I search PR history to find out why a specific code change was made?▼

To search PR history for code change reasoning, you can semantically query PR descriptions and review discussions to uncover the historical context and decision-making process behind specific implementations.

Can I trace the origin of a code behavior through GitHub pull request discussions?▼

Yes, you can trace the origin of a code behavior through GitHub pull request discussions by semantically searching review histories to identify the specific PRs where the implementation decisions were originally made.

Does this semantic search include Slack messages or documentation alongside PR reviews?▼

This semantic search does not include Slack messages or documentation; it focuses solely on PR descriptions and review discussions to filter out noise and isolate the code reasoning history.

What is the best way to investigate previous implementation decisions across connected repositories?▼

The best way to investigate previous implementation decisions across connected repositories is to run a semantic search targeting PR descriptions to reveal the historical context of the codebase changes.

How do I query the PR-centric search to understand the decision history of a feature?▼

To query the PR-centric search for feature decision history, pass a natural language question like "Why was feature X implemented?" to the search function to retrieve the relevant review discussions.

Related Skills

Explore More Software Engineering Skills→
dr-codedr-code

github-automation

Automate GitHub issues, pull requests, branches, CI/CD, and deployments via Rube MCP.

Community
Advanced
tfunk1030tfunk1030
1

research

Document a codebase as-is with parallel sub-agents and metadata-rich architecture references.

Community
Intermediate
urschreiurschrei
12

zotero-search

Search local Zotero libraries and cross-reference citations with Semantic Scholar.

Community
Advanced
tianzecntianzecn
2

code-search-selector

Automate code search strategy selection for multi-file codebase investigations.

Community
Intermediate