dean_stratakos

4 ms·

1.
by dean_stratakos 5mo ago
Thanks for the kind words! Excited to have you try it out
2.
by dean_stratakos 5mo ago
the cool part is that you can run the skill from the same agent session so it has the context on the plan and implementation process but if you run the skill in a fresh session, it naturally wouldn't have the plan
3.
by dean_stratakos 5mo ago
appreciate it! and yep, we've got lots of ideas on the roadmap to bring a more complete iteration experience closer to the coding agent. we've found it pretty silly that we have to push to GitHub in order to get comments from a re
4.
by dean_stratakos 5mo ago
parley looks awesome! we're planning to add support for comments soon, which is definitely a key feature to being able to iterate back and forth with a coding agent
5.
by dean_stratakos 6mo ago
Ideally, the world trends towards enabling less technical people to get more involved in the whole software loop! Stage is still geared toward a more technical audience, but I think we are going to start reviewing at a higher level for cert
6.
by dean_stratakos 6mo ago
Yeah it's getting easier to have agents just add "one more thing" to a PR, and I think there is still an aspect of human engineering judgement to know when to break up PRs versus trusting AI/tools to keep velocity high.
7.
by dean_stratakos 6mo ago
Agree that agents are definitely handling more and more of the coding side, and there's almost no doubt they will get better slop-wise. In our view, even vibe coders should understand how the codebase works, and we think review is a na
8.
by dean_stratakos 6mo ago
It's possible, but at the same time it's been years and they haven't copied things like Graphite's dashboard or stacked PR interface yet. We have the advantage of speed :)
9.
by dean_stratakos 6mo ago
In our experience, it's difficult to create well-mannered commits as you code and new ideas pop into your head or you iterate on different designs (even for LLMs). One concept we toyed around with was telling an LLM to re-do a branch u
10.
by dean_stratakos 6mo ago
Chapters are regenerated every time a new commit is pushed to a PR. Our thinking is that the chapters should serve as "auto stacked diffs" since they should follow a logical order. Do you or your team use stacking in your workflow
11.
by dean_stratakos 6mo ago
We don't support that currently, but would love to see examples where you disagree with the chapters so we can figure out the best interface You can regenerate the chapters anytime, but it might lead to similar results as the first tim
12.
by dean_stratakos 6mo ago
100%. A big part of code review in my mind is to automate away specific mistakes and anti-patterns across a team. I think there are a lot of interesting things to be done to merge the code writing and code reviewing cycles.
13.
by dean_stratakos 6mo ago
Yeah that could be useful, especially with the increased popularity of stacked PRs But I see it working together with chapters, not instead of bc it's still good to see the granularity within a PR