skills.rest
mia-cx
mia-cxOFFICIAL
Explore all skills by this author →
WebsiteGitHub

pr-resolve-discussions

Identify unresolved GitHub PR review threads and implement architectural fixes.

Updated Mar 23, 2026
Search Tags:#architecture#code-quality#code-review#pull-request#gitHub#pr-resolution
One-click install
npx skills add https://github.com/mia-cx/.agents --skill pr-resolve-discussions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-resolve-discussions
Source: https://github.com/mia-cx/.agents/tree/main/skills/pr-resolve-discussions
Command: npx skills add https://github.com/mia-cx/.agents --skill pr-resolve-discussions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Resolve unresolved PR review discussions by validating findings and implementing architectural fixes so that pull requests can merge cleanly.

Core Features & Use Cases

  • Trace unresolved review threads on a GitHub PR, categorize findings as real bugs or design smells, and determine the necessary corrective action.
  • Apply architectural fixes that address root causes rather than quick surface patches, reducing tech debt.
  • Communicate results by replying to threads and confirming resolutions, while preserving tests and contracts.

Quick Start

Identify a PR with unresolved discussions and start the resolution workflow to classify findings and implement architectural fixes.

Frequently Asked Questions about pr-resolve-discussions

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

FAQPage Schema
How do I resolve unresolved GitHub pull request discussions?▼

Resolve unresolved GitHub pull request discussions by tracing review threads, classifying findings as bugs or design smells, and implementing architectural fixes to unblock merging while preserving tests and contracts.

How do I fix design smells found in a code review?▼

Fix design smells found in a code review by applying architectural fixes that address root causes rather than quick surface patches, effectively reducing technical debt while maintaining existing software contracts.

What is the best way to trace the blast radius of a bug found in a PR review?▼

Trace the blast radius of a bug found in a PR review by classifying the unresolved finding and tracking its architectural impact across the codebase to determine the necessary corrective action for a clean merge.

Can I automate replying to GitHub PR threads after implementing fixes?▼

Automate replying to GitHub PR threads by following an end-to-end workflow that communicates architectural fix results directly to unresolved review discussions and confirms their resolution.

Does this PR resolution workflow preserve existing tests and contracts?▼

This PR resolution workflow preserves existing tests and contracts while implementing architectural fixes to resolve unresolved code review threads and unblock pull request merging.

When should I use architectural fixes instead of quick patches for PR review comments?▼

Use architectural fixes instead of quick patches for PR review comments when unresolved threads indicate real bugs or design smells, requiring root cause analysis to reduce long-term technical debt.

Related Skills

Explore More Software Engineering Skills→
getty104getty104
11

resolve-pr-comments

Resolve unresolved GitHub pull request review threads via the GraphQL API.

Community
Intermediate
CrumbgrabberCrumbgrabber
3

finishing-a-development-branch

Verify tests and execute merge, Pull Request, or cleanup workflows.

Community
Intermediate
AvihusittonAvihusitton

brooks-lint

Review code for design smells, coupling issues, and architectural risks.

Community
Intermediate
sylvandingsylvanding
9

resolve-pr-parallel

Resolve GitHub pull request review comments via parallel agent processing.

Community
Intermediate