# Set Up Workflow: Comprehensive Claude Code Workflow for Automated Software Engineering
## What This Is
This project showcases a complete, automated software development lifecycle using the Claude Code AI agent. It provides a full template for setting up automated code generation, quality checks, code reviews, documentation updates, and integration with project management tools like JIRA.
Source: https://github.com/ChrisWiles/claude-code-showcase
## 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.)
- Whether this repository or a similar tool is already cloned or installed
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)?
## Fetch the Source
Clone or inspect the repository to understand what needs to be installed:
```bash
gh repo clone ChrisWiles/claude-code-showcase
```
Review the README, directory structure, and any install instructions before proceeding.
## 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 repository `ChrisWiles/claude-code-showcase` to use as a template for the user's project.
- Scan the user's existing codebase to identify key conventions, such as their UI component library, testing patterns, and API schema structure.
- Adapt the skills, hooks, and GitHub Actions from the template to match the user's project conventions, and integrate the automated workflows into their existing CI/CD pipeline.
## 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