introducing diffmap: a new document format for planning and reviewing agent code. The idea behind diffmap is letting you review the important design changes, not massive line diffs. "Write a diffmap spec for the changes on this branch. Use I've been working and iterating on this skill for more... than 2 months! I use it every day for any big feature or refactor. Excited to finally make it publicshow more

diffmap gives your agent a ton of interactive diagrams and widgets to help collaboratively plan and review with you. one example is a services diagram. it shows you different involved services, along with state changes and data flow over time

other ones include mermaid diagram diffs and of course, callstack diffs. the skill includes guidance on when to use each diagram.

the agent writes the plan in phases. Each phase is meant to be a single commit. after an agent completes a phase, it shows a commit widget, with the most important files ordered. Clicking on a file opens a diff panel (powered by @pierrecomputer ofc!)

You're also able to add comments to the diffmap and copy it for your agent

Diffmap is open-source and MIT licensed! Check it out

looks interesting! a few thoughts on the video - we don’t find out what it actually is until about half way through. from the first frame i already knew what you were trying to address (by having skimmed the post). i would deliver the before and after payoff right away. the other alternative is to come up with a really good hook but then you have to keep attention for every second up to the reveal

yeah i had the same thought, agreed! will have to show payoff faster

Good stuff. The psuedo code with links to actual implementation is the best part I think. I used it immediately to try to understand the repo itself and it did a great job. Nicely done.

glad to hear! Lmk if you have any feedback

this is so sick

Nice idea

Excellent! Been using crit.md which has similar goal. Those tools are the key to unlock productivity.

Nice! I was wondering if you'd release it since last time I saw you talk about it. 👏

yes it took a long time to dial in and until I was happy with it. Still a WIP honestly, but I use it every day so that was a good enough bar

Amazing Tanisqh!

Tried it on few PRs, great execution!

This is really cool

thanks! would love some feedback

Will see about trying it soon

This is crazy, I was working on the same idea and I was calling it replay.

This is awesome!

@bot save to my vault to check out

can you view this on mobile?

What do you use to make sure the map lines up with what’s in the code? Programmatic tools that check some of the mapping between the two would make it a lot easier to trust the info. (As long as it’s clear what precisely is verified by the tools, and what we’re taking on trust)

the diff panels are real code lines. everything else is written by the agent. the agent can reference the code lines in the diagrams, so you can audit whats in the diagram matches up with whats in the code, but realistically that’s not an issue

This is sweet! gonna try this.

lmk if you try it and have feedback!

this would be so good with a validator that checks every callstack node points at an actual changed hunk and flags files in the diff that no node covers lol

yes have thought about this! decided it was easier product ux to show a commit summary when implemented. but very interesting concept, just didnt know how to surface cleanly

Is the sharing feature being implemented via github gist a temporary thing? Would feel safer if it was something more restrictive.

agreed! yeah its temporary, ill implement something better if more people want it

Does the ✅ version of a phase usually look much like the plan? That gap feels like the bit most worth reviewing

basically, the plan is composed of phases (commit-length work). You review the plan, and (my preferred way of working) is going phase by phase, but you can also just decide to build the whole thing in one shot

cc @karrisaarinen ☝️

@karrisaarinen oh yeah saw their recent launch! Need to dig into it more