DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to edit an AI-written Markdown plan and send feedback in one batch with Human Review

Mark up a Markdown plan in the browser and send all edits and comments to your agent at once.

  • Top pick
  • Content
  • Intermediate
  • 15 minutes
  • From the README
  • Claude Code
  • Codex

Who it is forA founder or team lead who asked an AI agent for a project plan or doc and wants to fix wording and structure without typing a long chat message.

The problemChat feedback like 'change X to Y in the third paragraph' is slow, and you cannot be sure the agent applied every instruction.

The outcomeThe agent updates the Markdown source with every edit and comment you sent, and the page refreshes for another review.

What you need first

  • A coding agent that can install skills, such as Claude Code or Codex
  • A web browser
  • An HTML or Markdown file on your computer, or a page running on localhost
  • npx available on your computer if you use the npm install option

Steps

  1. Paste this into Claude Code or Codex: Install the /human-review skill globally from https://github.com/petergyang/human-review
  2. Or run npx -y human-review setup --global in your terminal
  3. Ask your agent to open your file with /human-review (your file)
  4. Edit text directly, add comments on selected phrases, and reorder blocks by dragging their handles
  5. Click Send so the agent receives all feedback in one batch and updates the source

Prompt for your agent

Install the human-review skill from the petergyang/human-review repo, then open <path-to-markdown-file> with /human-review. After I click Send, confirm the agent applied every edit and comment to the Markdown source and report any change it could not make.

Caveat. For Markdown files you must click Send for changes to reach the source, since only HTML file edits save automatically.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page