Cool! Looks like a genuinely useful tool, reducing some pretty common friction within the code review process.<p>Three features I'd want before using it:<p>1) Rather than triggering Sedy immediately on a reviewer comment, I'd like the trigger to be the original requester <i>reacting</i> to the comment with a thumbs-up. The requester knows what they're trying to say, and they should decide if the changes get made.<p>2) I wish there were an option to restrict it to comments for supported languages. Your examples are just changing markdown (not code), and I think rightfully so — I can easily see this tool becoming a way for a senior dev reviewer to attempt to avoid the back-and-forth with a junior dev by just posting some complex code substitutions... substitutions which could easily screw things up.<p>3) sed replacement actually seems <i>too</i> powerful for this job. For instance, if I want to make a replacement like:<p><pre><code> s/**bold** thing/**bold thing**/
</code></pre>
...I really don't want to try escaping that without feedback. I'd rather have direct string replacement without regex than the full power of sed. This probably goes against your design goals, but for me it would be much more useful.