answer-pr-questions

To find unanswered stakeholder questions in GitHub pull requests, this Skill scans issue timelines, PR timelines, and review threads to identify currently relevant questions lacking clear answers. It automatically filters out previously resolved items based on current PR state.

Yes, you can generate plain language summaries from GitHub issue discussions for clients. This Skill produces client-ready markdown responses with concise 2-4 sentence answers per question, explicitly stating missing information and required stakeholders when thread details are lacking.

Yes, analyzing pull request review threads requires using GitHub CLI as the primary tool, with an MCP fallback. The Skill loads cursor editor rules and project.mdc files first to establish context before scanning discussions for unanswered questions.

The best way to track unanswered questions across GitHub issue timelines is using context-aware filtering that scans both issue and related PR timelines. This approach discovers stakeholder questions lacking clear answers while ignoring previously resolved items based on current PR state.

To format GitHub pull request updates for non-technical project managers, this Skill outputs unified responses in a specified markdown format using the assignment language. Each answer contains 2-4 short sentences written in plain language, explicitly noting missing information and responsible parties.

Context-aware filtering for GitHub PR discussions works by scanning the issue timeline, related PR timeline, and review threads to identify unanswered stakeholder questions. It ignores questions already answered in the same context, keeping only items relevant to the current PR state.