awesome-AI-driven-development

🥈Silver

AI-driven development tools for automating code generation, testing, and maintenance. Benefits developers and operations teams by speeding up development cycles and reducing manual work. Integrates with GitHub, GitLab, and other version control systems.

347250Updated Today

Intermediate30min to implementautomation

Saves ~20 min per use

Quick InstallView Source

git clone https://github.com/eltociear/awesome-AI-driven-development.git

Works with:

Claude

Overview

About This Skill

How to Use

1. **Prepare Your Repository:** Ensure your code is pushed to a GitHub/GitLab repository and has a clear [ISSUE_DESCRIPTION] or feature request to address. Enable GitHub Actions or GitLab CI for automated testing. 2. **Run the Prompt:** Paste the prompt template into your AI tool (e.g., Claude, ChatGPT) and replace [REPOSITORY_NAME], [GIT_PLATFORM_URL], [ISSUE_DESCRIPTION], and [CODING_STYLE_GUIDE] with your specific details. For example, use `[CODING_STYLE_GUIDE]` as `PEP 8` for Python or `Google Java Style` for Java. 3. **Review and Refine:** The AI will generate a pull request with code fixes, tests, and optimizations. Review the changes for accuracy, security, and alignment with your project’s standards. Use tools like `ESLint`, `Pylint`, or `SonarQube` to validate the output. 4. **Test and Deploy:** Run the generated unit tests locally or in CI. If tests fail, ask the AI to adjust the implementation or tests. Once validated, merge the PR and deploy to staging/production. 5. **Iterate:** Use the AI to generate additional PRs for related issues or to refactor legacy code. Track metrics like test coverage, performance improvements, and bug reduction to measure impact.

Setup & Installation

Quick Install

No install command available. Check the GitHub repository for manual installation instructions.

Alternative Install (Git Clone)

git clone https://github.com/eltociear/awesome-AI-driven-development

Requirements

Claude Code or compatible AI agent
Works with: Claude

Quick Start Guide

Install the Skill

Copy the install command above and run it in your terminal.

Open Your AI Agent

Launch Claude Code, Cursor, or your preferred AI coding agent.

Try It Out

Use the prompt template or examples below to test the skill.

Customize

Adapt the skill to your specific use case and workflow.

Usage Examples

Prompt Template

Act as an AI-driven development assistant. For the repository [REPOSITORY_NAME] at [GIT_PLATFORM_URL], perform the following tasks: 1) Generate a pull request with a code fix for [ISSUE_DESCRIPTION] using the most efficient approach, 2) Write unit tests for the modified code covering edge cases, and 3) Suggest performance optimizations for the affected components. Include comments explaining your changes and ensure the code follows [CODING_STYLE_GUIDE].

Example Output

Here’s a pull request for the `payment-service` repository (https://github.com/acme/payment-service) addressing a critical bug where the `processPayment` function fails to validate the `transactionId` format, causing payment failures for 12% of users.

**Changes Made:**
1. **Code Fix:** Updated the `processPayment` function in `src/payment/handler.js` to validate `transactionId` against a regex pattern (`/^[A-Z0-9]{10}$/`). Added a new error class `InvalidTransactionIdError` for consistent error handling. The fix reduces payment failures by 98% in testing.

2. **Unit Tests:** Added 15 new test cases in `tests/payment.test.js` covering:
   - Valid transaction IDs (e.g., `AB12345678`)
   - Invalid formats (e.g., `ab12345678`, `AB1234567`, `AB123456789`)
   - Edge cases like empty strings or non-string inputs
   - Integration with the `paymentGateway` mock to ensure the error propagates correctly.

3. **Performance Optimization:** Suggested caching the regex pattern in `src/payment/validator.js` to avoid recompilation on every call. Benchmarked the change: reduced validation time from 1.2ms to 0.3ms per transaction (75% improvement).

**Next Steps:**
- Review the PR and approve if the changes meet requirements.
- Merge after CI passes (all 47 existing tests + 15 new tests pass).
- Deploy to staging for further validation.

**Files Modified:**
- `src/payment/handler.js` (12 lines added)
- `src/payment/validator.js` (3 lines modified)
- `tests/payment.test.js` (15 test cases added)

**Metrics:**
- Code coverage: 94% (up from 88%)
- Performance improvement: 75% faster validation
- Bug fix success rate: 98% reduction in payment failures