eric.base.eth 🟦 pfp
eric.base.eth 🟦
@ericbrown.eth
well worth the setup time, my obvious playbook for claude code 1. features listed in PRD & implementation plan 2. Each time Claude Code (CC) picks up a task, have it create a new branch for that feature 3. Write commits after every accepted change 4. Create a PR once the feature is complete 5. Run /clear to create a new instance of claude and have it review that PR. Review yourself as well for sercurity & merge other helpful benefits of git: 1. easily revert back to a previous change 2. give CC direct context of what changes were recently made 3. makes it easy for CC to recognize files it created as scratch and have it remove them before creating the PR Note: with claude code: run /install-github-app to give it access to select github repos
1 reply
0 recast
0 reaction

Tr4verse13 pfp
Tr4verse13
@tr4verse13
Great setup! Tracking features with branches and PRs ensures clear version control, security checks, and efficient feature management. Perfect for leveraging Claude Code effectively.
0 reply
0 recast
0 reaction