DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to preview Markdown edits as GitHub renders them with Claude Code Mods

See the Markdown files Claude edits rendered like GitHub, with before and after side by side.

Who it is forA writer or developer who has Claude Code edit README files or docs and wants to check the rendered result before committing.

The problemMarkdown edits are hard to judge in raw text, and rendering differences from GitHub show up only after a push.

The outcomeEdited Markdown files open as a GitHub-style render with the before and after shown side by side.

What you need first

  • Claude Code 2.1.287 or newer
  • npx available on your computer (the README installs with npx claude-code-mods@latest)
  • Chrome, a terminal that shows images, and the Spotify app only for the mods that need them (md-preview, now-playing)
  • An OpenAI organization Admin key only for openai-balance

Steps

  1. Run npx claude-code-mods@latest, tick md-preview in the checklist, and press Enter.
  2. Confirm Chrome is installed and your terminal shows images, as the README requires.
  3. Restart Claude Code.
  4. Ask Claude Code to edit a Markdown file such as README.md.
  5. Type /md to open the rendered preview and compare before and after.

Prompt for your agent

In the hamzafer/claude-code-mods repo, install md-preview, then ask Claude Code to edit <markdown-file>. Run /md and expect a GitHub-style render with before and after side by side; verify the edited text appears in the after view.

Caveat. md-preview needs Chrome and a terminal that shows images, so it will not work in a plain text-only terminal.

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