Add development configuration

[daniel-richter]

• Just create a copy of the .env file and name it .env.development so you can use it for debugging.
• Added two VSCode launch configurations:
  • PR Summary (npm start)
  • PR Review (npm start)

---

This change standardizes the development environment setup by improving environment file handling, adding VS Code debugging support, and updating development tooling. The modifications focus on creating a consistent development workflow across both PR summary and PR review components while enhancing the gitignore patterns for better file exclusion.

Walkthrough

• Chore: Updated .gitignore to use wildcard pattern .env.* for broader environment file exclusion, removing specific test file references
• Chore: Added VS Code launch configuration with debugging support for both PR Summary and PR Review services using separate development environment files
• Chore: Configured VS Code settings to disable GitHub Copilot for shell scripts
• Chore: Created template .env files for both services with comprehensive configuration examples and placeholder values for local development
• Chore: Updated package.json scripts to reference .env.development instead of .env.test and added tsx dependency for improved TypeScript execution

_{Model: anthropic--claude-4-sonnet | Prompt Tokens: 1871 | Completion Tokens: 212}

[github-actions]

This change streamlines the development setup by broadening ignored env files, introducing consistent .env.development samples, and adding VSCode debug configurations. It also switches project start scripts to load the new development environment, updates editor settings, and includes required dependencies for TypeScript execution.

Walkthrough

• Chore: Ignore all .env.* files via .gitignore
• Chore: Add VSCode launch configurations for local debugging (pr-summary, pr-review)
• Style: Enable GitHub Copilot for non-shell scripts in editor settings
• Documentation: Provide sample .env.development files with environment variable templates
• Chore: Update start scripts to source .env.development instead of .env.test
• Chore: Add tsx dependency for seamless TypeScript execution

_{Model: o4-mini | Prompt Tokens: 1476 | Completion Tokens: 769}

[github-actions]

Here is a friendly code review powered by AI. Consider these suggestions as ideas rather than strict rules. Feel free to adopt or adapt any recommendation in a way that best matches your workflow. You hold the reins and make the final decisions. AI is here to help support your creativity and expertise, not to replace it.
_{Model: o4-mini | Prompt Tokens: 2383 | Completion Tokens: 1991}

[github-actions]

Here's a collaborative code review enhanced by AI assistance. These suggestions offer potential improvements and insights to consider, though they're recommendations rather than requirements. You have complete control over which ideas to implement based on your project's needs and your professional judgment. The AI serves as a supportive tool to help identify possibilities you might explore further.
_{Model: anthropic--claude-4-sonnet | Prompt Tokens: 2791 | Completion Tokens: 1172}