I'm a senior Android dev and Claude Code has become part of my day, but I suspect my workflow is pretty primitive compared to what others have built.
Right now it's basically: copy the Jira story or the bug report, paste it into Claude Code, ask it to analyze it using my skills and experts agents, and produce a plan before it touches anything. Then I review the plan, push back on the parts that are wrong, and let it implement.
That's it. That's the whole loop.
What I want to know is what people do *around* that step:
- Do you paste the raw ticket, or do you have a command that pulls it from Jira/Linear and reformats it first?
- Do you give it the crash/stack trace and mapping file up front, or make it ask?
- Does it get to run the app on a device to reproduce, or is that still manual for you?
- Do you make it write a failing test before the fix, or is that too slow in practice?
- Anyone doing something smarter for "which module does this even live in" on a big multi-module codebase?
- And what do you do at the end . does it write the PR description and the ticket update, or do you still do that by hand?
Mostly curious whether people have gotten past the copy-paste-and-pray stage, and what the step was that actually made a difference for you.
submitted by /u/Ok-Swimming-2992[link] [comments]