ask-unblocked

Research PRs, docs, chats, issues, and incidents to answer codebase questions with citations.

13|1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/unblocked/cookbook --skill ask-unblocked
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ask-unblocked
Source: https://github.com/unblocked/cookbook/tree/main/recipes/ask-unblocked
Command: npx skills add https://github.com/unblocked/cookbook --skill ask-unblocked

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams obtain accurate, contextual answers about the codebase, product decisions, and organizational context by researching organizational artifacts (PRs, docs, chat, issues, incidents, and code history) and delivering a cited, well-formatted response. It synthesizes information from multiple sources and does not modify code.

Core Features & Use Cases

  • Research-driven Q&A: classifies the question, then performs primary research via cross-source queries and pulls in relevant sources.
  • Follow-up research: retrieves full content from relevant URLs and traces connections between PRs, issues, and discussions to strengthen answers.
  • Structured outputs: renders diagrams (Mermaid), tables for tradeoffs, and timelines for historical events with inline citations.
  • Safe, citation-first philosophy: all factual statements are tied to sources with explicit citations and transparent limitations.

Quick Start

Ask a question about the codebase or team context, and let this skill research PRs, docs, chat discussions, issues, and incidents to produce a cited, structured answer.

Frequently Asked Questions about ask-unblocked

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

FAQPage Schema
How do I get cited answers about why specific codebase decisions were made?

To get cited answers about codebase decisions, you can ask a question and the skill researches organizational artifacts like PRs, docs, and issues. It then synthesizes the findings into a structured response with inline citations linking directly to the original sources.

Can I trace incident history and system connections across pull requests and chat discussions?

Yes, you can trace incident history and system connections by querying across pull requests, chat discussions, and issues. The skill performs cross-source research to retrieve full content and maps out historical events using timelines and diagrams.

What is the best way to research organizational context without modifying the codebase?

The best way to research organizational context without modifying the codebase is to use a research-driven Q&A tool. This approach aggregates sources like code history and incidents to deliver structured answers, ensuring no code changes occur while maintaining source provenance.

Does this cited Q&A approach support visual outputs like diagrams and tables for tradeoff analysis?

Yes, this cited Q&A approach supports visual outputs by rendering Mermaid diagrams and tables for tradeoff analysis. It formats historical events into timelines, ensuring all visual structures are backed by inline citations from the researched organizational artifacts.

How do I find out who contributed to a specific feature or what happened during a recent incident?

To find out who contributed or what happened during an incident, you ask a contextual question about your codebase. The tool classifies the query, performs primary research across chats and issues, and delivers a cited answer detailing contributions and incident timelines.

What are the limitations of using automated research for codebase and product decision queries?

A key limitation of using automated research for codebase queries is its reliance on accessible artifacts like PRs and docs; it provides transparent limitations for missing data. It strictly synthesizes existing information and does not modify code or execute changes.