revise-markdown

Identify, resolve, and remove all embedded review comments in markdown documents.

Updated May 21, 2026
One-click install
npx skills add https://github.com/wangcb8i8i/agent-skills --skill revise-markdown
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: revise-markdown
Source: https://github.com/wangcb8i8i/agent-skills/tree/main/revise-markdown
Command: npx skills add https://github.com/wangcb8i8i/agent-skills --skill revise-markdown

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually tracking and addressing review comments in markdown documents often leads to missed feedback, inconsistent revisions, and unnecessary back-and-forth with stakeholders, slowing down document finalization.

Core Features & Use Cases

  • Structured Review-Revise Loop: Systematically finds, analyzes, and addresses every embedded review comment until all are resolved.
  • Conflict Resolution: Evaluates overlapping or conflicting comments to prioritize changes that align with overall document goals.
  • Ambiguity Handling: Asks for clarification on vague feedback instead of making incorrect assumptions, reducing wasted revision cycles.
  • Use Case: Use this skill to finalize a team project proposal with multiple stakeholder review comments, ensuring no feedback is overlooked and the final document meets all requirements.

Quick Start

Ask the AI to revise the attached project-proposal.md file by addressing all embedded review comments and repeating the process until you give explicit approval.

Frequently Asked Questions about revise-markdown

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

FAQPage Schema
How do I resolve all review comments in a markdown document without missing any feedback?

To resolve markdown review comments comprehensively, use a structured review-revise loop that systematically identifies every embedded marker, addresses conflicting feedback, and removes resolved comments until explicit approval is granted.

What is the best way to handle conflicting stakeholder feedback in markdown technical specifications?

Handling conflicting stakeholder feedback in markdown technical specifications involves evaluating overlapping comments to prioritize changes that align with overall document goals, ensuring consistent revisions across the entire artifact.

Can I automate collaborative feedback resolution for project proposals in markdown format?

You can automate collaborative feedback resolution for markdown project proposals by applying a guardrailed review-revise loop that iteratively addresses embedded comments and terminates only upon explicit user approval.

Why does manually tracking review comments in markdown documents lead to inconsistent revisions?

Manually tracking markdown review comments leads to inconsistent revisions because unaddressed or partially resolved feedback creates incomplete edits, requiring unnecessary back-and-forth with stakeholders to finalize the document.

How do I get clarification on vague review comments in markdown documents instead of making assumptions?

To get clarification on vague markdown review comments instead of making incorrect assumptions, use an ambiguity handling process that asks stakeholders for direct clarification, reducing wasted revision cycles.

Does the markdown revision process work for iterative stakeholder feedback on technical reports?

The markdown revision process works for iterative stakeholder feedback on technical reports by implementing a guardrailed loop that finds all embedded review markers, resolves conflicts, and removes resolved comments systematically.