Skip to content

Add Codegen team workflow documentation #1065

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
codegen-sh wants to merge 1 commit into
base: develop
Choose a base branch
from
Draft

Add Codegen team workflow documentation #1065

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
37 changes: 36 additions & 1 deletion docs/gen/capabilities.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,4 +64,39 @@ Codegen's brain (powered by Claude 3.7 Sonnet) intelligently selects and combine
3. Execute the necessary actions across GitHub, Linear, and your codebase
4. Provide clear, helpful responses back in Slack

This seamless integration allows you to manage your entire development workflow through simple conversations, without having to switch between different platforms and interfaces.
This seamless integration allows you to manage your entire development workflow through simple conversations, without having to switch between different platforms and interfaces.

## How the Codegen Team Uses Codegen

The Codegen team itself uses Codegen to build and improve Codegen! Here's how the team maximizes productivity with their own tool:

### Workflow Integration

- **Small bug fixes**: For minor issues, Codegen is used for instant merges
- **Larger tickets**: The team uses a multi-step approach:
1. Ask Codegen to do a first pass (triggered from Slack thread discussing the bug/feature or Linear ticket)
2. Check out the branch and review the changes
3. Add any necessary adjustments
4. QA the changes
5. Merge the code

### IDE vs. Codegen

The team uses Codegen for:
- Initial exploration and first pass on the majority of tickets and engineering efforts
- Quickly gathering context on issues (e.g., explaining sentry errors in Slack notification threads)
- Specifying the "blast radius" of a given change to understand its impact
- Treating Codegen as a solid first pass at 80% of their work

The team then uses their IDE (like Cursor) for:
- Making precise adjustments after Codegen's first pass
- Detailed work that requires deep context

### Best Practices

- The team is diligent about analyzing tasks and determining how an agent would approach them
- They split complex tasks into manageable chunks
- They're liberal with deleting unhelpful outputs in Slack/Linear
- They view Codegen as a very solid first pass rather than an infallible oracle

This approach allows the Codegen team to leverage their own tool effectively while maintaining high code quality and productivity.
Loading