resolve-comments

Resolves inline review comment threads in markdown and HTML planning documents.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/mistakenot/skills --skill resolve-comments-mistakenot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resolve-comments
Source: https://github.com/mistakenot/skills/tree/main/plugins/planning-workflow/skills/resolve-comments
Command: npx skills add https://github.com/mistakenot/skills --skill resolve-comments-mistakenot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Review cycles on planning documents leave scattered inline comment threads that must each be addressed, answered, or escalated. Manually tracking which threads are resolved, rejected, or still open across markdown and HTML docs is error-prone and loses decision history. ## Core Features & Use Cases - Thread Triage: Parses review comment threads in markdown (HTML comment blocks) and HTML (pd-thread/pd-comment elements) planning docs, then resolves, rejects, or leaves each thread unresolved with an author reply. - Append-Only History: Preserves full decision history by never deleting prior comments, updating only thread status labels (RESOLVED, REJECTED, UNRESOLVED) and appending AUTHOR replies. - Use Case: After a reviewer leaves P1/P2 comments on plan.html and context.md in docs/tasks/042-auth-redesign/, run this skill to fix valid concerns in place, reject inapplicable ones with cited rationale, and get a summary of threads still needing human input. ## Quick Start Resolve all review comments left on the planning docs for task 042 and summarize which threads were resolved, rejected, or still need my input.

Frequently Asked Questions about resolve-comments

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

FAQPage Schema
How do I resolve review comments on planning documents?▼

Point the skill at the files or task ID containing the comments. It parses each thread, fixes valid concerns in the document, marks threads RESOLVED or REJECTED with an author reply, and summarizes anything still needing your input.

What comment formats does this skill support?▼

It supports markdown files using HTML comment blocks with UNRESOLVED/RESOLVED/REJECTED status labels, and HTML planning docs using pd-thread and pd-comment elements from the pd-* web component library. The format is chosen by file extension.

Can I use this for PR code review feedback?▼

No. This skill is explicitly scoped to inline comments in planning documents, not pull request code review feedback. For PR review comments, the workflow directs you to the address-feedback skill instead.

Does resolving comments delete the original review history?▼

No. Threads are append-only: prior review comments are never deleted or rewritten. Resolution adds an AUTHOR reply and updates the thread status, so the full decision log stays in the document source.

What happens when a comment cannot be resolved automatically?▼

The thread stays UNRESOLVED and gets an AUTHOR reply describing the question or blocker. The final summary lists these threads so you know exactly which items need human input before proceeding.