# Set Up Workflow: Automated Code and Design Review Workflow Using Claude Code and GitHub Actions
## What This Is
This workflow uses AI agents to automatically review new code and visual design changes submitted by developers. By automating checks for bugs, style standards, and UI consistency, it frees up engineering teams to focus on building new features rather than performing manual reviews.
Source: https://www.youtube.com/watch?v=Xs942zwWfdY
## Before You Start
Scan my workspace and analyze:
- The project language, framework, and directory structure
- Existing AI provider config (check .env, .env.local, config files for API keys — OpenRouter, OpenAI, Anthropic, Google AI, etc.)
Then ask me before proceeding:
1. Which AI provider/API should this use? (Use whatever I already have configured, or ask me to set one up — options include direct provider APIs or a unified service like OpenRouter)
2. Where in my project should this be integrated?
3. Are there any customizations I need (model preferences, naming conventions, constraints)?
## Source Access Note
The source URL (https://www.youtube.com/watch?v=Xs942zwWfdY) may not be directly accessible from the terminal. Use the Reference Implementation and Additional Context sections below instead. If you need more details, ask me to paste relevant content from the source.
## What to Implement
This is an **AI Workflow** — an end-to-end automation pattern or integration pipeline.
- Study the workflow architecture from the source and context below
- Identify which parts I can implement locally vs. parts that need external services
- For local parts: implement them using my existing stack and API keys
- For external parts: tell me exactly what services I need and help me configure the integration code
- Wire up any required API calls using keys from my .env files
## Additional Context
- Clone the 'claude-code-workflows' repository from GitHub (github.com/OneRedOak/claude-code-workflows) into the user's workspace.
- Analyze the cloned repository's `.github/workflows/` directory, specifically the `code_review.yml` and `design_review.yml` files. Explain to the user how these GitHub Actions are triggered and how they invoke the Claude Code agents for PR analysis.
- Inspect the user's current project for an existing CI/CD pipeline. Propose a plan to adapt the cloned workflow files, including modifying the triggers and configuring repository secrets for the Claude API key, using a key from the user's .env if available.
## Guidelines
- Adapt everything to my existing project — do not assume a specific stack or directory layout
- Use whichever AI provider I already have configured; if I need a new one, tell me what to sign up for and I'll give you the key
- Check my .env files for existing API keys (OpenRouter, OpenAI, Anthropic, Google AI) before asking me to add one
- Review any fetched code for safety before installing or executing it
- After setup, run a quick verification and show me a summary of exactly what was installed, where, and how to use it