MapSense

"What prompt would have produced this code?"

A social feed where every post is a Pull Request. See the prompt that produced the code — or let an LLM reverse-engineer it from the diff.


Sign in with GitHub to get started

Want the quick overview first? See how it works.

Private repos are manual by default. Review before publishing, and use your own LLM if you prefer. Read Privacy & FAQ.


🔍 Reverse-Engineer Prompts

An LLM reads your PR diff and reverse-engineers the prompt that would have produced those code changes.

📣 Share Your Workflow

Include your actual AI prompt in PR descriptions and MapSense publishes it automatically. Zero effort.

❤️ Social Feed

Like, comment, bookmark, and follow. See what prompts other devs are using and how they structure their PRs.

🏷️ Auto-Detected Tags

Languages, frameworks, and AI tools detected from your diffs. Filter the feed by language, framework, or tool.

🔗 Direct PR Links

Every post links back to the original Pull Request. You can always check the actual code.

⌨️ CLI & Agent Ready

Post from your terminal with npx mapsense post #12. Works with Claude Code, Codex, and any coding agent.

🆓 Free Forever

MapSense is free for developers. Always. No paid tiers, no paywalls, no ads.


How it works

  1. Sign in with your GitHub account
  2. Connect the repos you want to publish from
  3. Open a PR — MapSense generates a post automatically
  4. Share — your post goes live on the feed

For private repos, keep manual review on and publish only what you are comfortable making public.

Read the full walkthrough →


Post from your terminal

Use the MapSense CLI to pick which PRs to post, use your own LLM for better quality, or integrate with your coding agent.

npx mapsense login
npx mapsense post #12

Works with Claude Code, Codex, GitHub Actions, or any environment with a terminal. Your LLM, your tokens, your choice.

Skip the LLM entirely and write your own post:

npx mapsense post #12 --prompt "Add rate limiting to all API endpoints" --yes