Pr issue context check

Skill bakerstreetco/skills/pr-issue-context-check

Search GitHub issues and pull requests to determine whether a feature, bug, or implementation is already in progress, discussed, shipped, rejected, or unresolved. Use when asked to check if anyone is working on something, find existing PRs or issues for a topic, understand the status of a GitHub conversation, determine if work has started on a feature, search for related discussions before opening a duplicate, or investigate who is tackling a particular problem. Trigger on phrases like "has anyone started", "is there already a PR", "who's working on", "find related work", or "search issues and PRs".From its SKILL.md

Install

npx -y skills add bakerstreetco/skills --skill pr-issue-context-check

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.2 KB, 569 tokens by cl100k_base, as published. Nobody here has run it

PR / Issue Context Check

Search GitHub issues and pull requests to find existing work before duplicating effort. Look for explicit signals like assignees, draft PRs, WIP labels, and maintainer comments that indicate someone has already started.

Do not search the local codebase unless the user explicitly asks you to connect GitHub context back to implementation.

Workflow

Parse the query into search terms. Extract the feature name, bug, component, and synonyms. Build both exact and fuzzy keyword lists. For "who's working on" queries, prioritize assigned items, draft PRs, WIP labels, and recent activity.
Identify the repository from git remote get-url origin. If ambiguous, check available remotes. If no repo can be inferred, ask for the GitHub URL.
Search PRs with gh pr list --search "<keywords>" across open, merged, and all states. For promising results, read the body and comments with gh pr view <number>. Capture number, title, URL, state, author, dates, labels, assignees, linked issues, and relevance.
Search issues with gh issue list --search "<keywords>" across open and all states. Read promising threads with gh issue view <number>. Capture number, title, URL, state, author, dates, labels, assignees, closing references, and maintainer guidance.
Cross-reference links between issues and PRs. Follow "duplicate of", "closes", and "fixed by" references to find canonical threads.
Consolidate and de-duplicate results. Keep borderline matches with an uncertainty note rather than dropping them.
Determine the conversation status using evidence:
- active_pr: open PR with implementation work
- active_discussion: open issue or PR thread deciding direction
- shipped: merged PR or maintainer completion statement
- rejected_or_abandoned: closed as not planned or stalled
- duplicate_or_superseded: redirected to another canonical thread
- no_relevant_context_found: no credible match found
Recommend where to participate next. Choose the single best open PR or issue when one exists. If nothing suitable exists, recommend opening a new issue or PR.

Output

Return a report with the query, final status and confidence, evidence summary with counts, a table of PR incidents with links, a table of issue incidents with links, a timeline of major discussion points, any gaps or uncertainty, a recommended next action, and the single best place to contribute (or None).

Always include GitHub URLs for every incident. Do not claim something shipped without a merged PR or maintainer confirmation. When evidence is ambiguous, lower confidence and explain what is missing.

What ships with it: 2 files

856 B alongside SKILL.md

agents/

openai.yaml250 B

skill.json606 B