DEDUPED Hot AI repos. Real use cases. What people build. Get the Monday 5

How to see which parts an AI change touched, and keep the map current with Floorplan

Update the Floorplan after each change and use Recent work and the Health check.

Short answer: Let the agent make its change; then Ask: Update the Floorplan; open Recent work to see which parts were touched. All steps.

Who it is forA developer letting Claude or Codex make changes who wants to see their blast radius.

The problemAfter an agent edits many files it is hard to see which parts it touched and why.

The outcomeAn updated map showing recent work and a health check, with secret values never stored or shown.

What you need first

  • Claude Code or Codex
  • Node.js
  • A project in a supported language (TypeScript, JavaScript, Python, Go, Rust, Java and more)

Steps

  1. Let the agent make its change
  2. Ask: Update the Floorplan.
  3. Open Recent work to see which parts were touched
  4. Run the Health check; rename parts by asking, or edit floorplan/architecture.json

Prompt for your agent

Update the floorplan for this repo, then list the parts the last change touched using Recent work and report anything the Health check flags.

Caveat. This card is written from the haydenschmitty/floorplan README, not from a test run by Deduped. Before you start, make sure you have Claude Code or Codex. Check the repo for newer instructions before you rely on these steps.

Use this in your AI agent

Ask your agent

Using the Deduped MCP, get the setup steps for haydenschmitty/floorplan and "See which parts an AI change touched, and keep the map current"

Add Deduped to Claude Code once

claude mcp add --transport http deduped https://dedupedai.com/mcp

Cursor, ChatGPT, others

Share: X LinkedIn Hacker News Email Copy link

Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer