Awesome AI Coding Tools

★ 1.9kAwesome Lists

#awesome#tools#ai-coding

Overview

A panorama of AI coding tools for developers and teams (1.9k+ stars), split into nearly twenty categories — editors and assistants, code completion, coding agents, CLI tools, app builders, UI generators, code review, testing, code models, security, MCP and more. Its core value is finding a tool for each stage: from writing code to testing, reviewing and shipping, every stage has a dedicated category to search.

Who it's for

Developers and teams who want to select AI tools systematically by development stage — especially those advancing from editor completion to end-to-end agentic workflows.

What you'll learn

01A taxonomy cut by stage
The list separates 'Code Editors and Assistants' from 'Code Completion': the former covers deep-in-editor assistants like Cursor, Windsurf and GitHub Copilot that understand context and edit across files; the latter focuses on completion engines like Tabnine, Supermaven and Codeium. Decide first whether you need a context-aware multi-file assistant or an ultra-fast completer, then compare within the matching category.
02From agents to end-to-end builders
'Coding Agents' and 'CLI Tools' cover agents that autonomously plan, write and test — Claude Code, Codex CLI, Gemini CLI, Devin, OpenHands, Aider and more. 'App Builders' and 'UI Generators' cover prompt- or screenshot-to-app entry points like Bolt.new, Lovable, v0 and screenshot-to-code, forming different routes from a one-line requirement to a complete application.
03Quality guardrails: review, testing and security
'Code Review and Refactoring' lists CodeRabbit, Sweep and What The Diff; 'Testing and QA' lists Playwright, Qodo and Testim; 'Security' lists Snyk, Semgrep and GitGuardian. With these three categories, the list signals that the quality of AI-generated code should be backstopped by review, testing and security tooling rather than by trusting the model itself.
04Foundations: models, MCP and local inference
The list dedicates 'Code Models' to Claude, GPT, DeepSeek Coder, Qwen2.5-Coder and others; 'MCP Servers and Directories' aggregates MCP server directories; 'Local LLM Tools' covers Ollama and LM Studio; plus DevOps, database and API tool sections — helping you understand the models, connection standards and deployment chains underneath the tools.
05How to pick a tool by stage
The usage guidance is direct: first identify which link is missing — writing, testing, review, deployment or security — then compare 2-3 candidates within that category; cross-check Code Models and Related Lists to judge the underlying model and ecosystem. It works both as a cognitive map for beginners and a reference manual for experienced selectors.

Practice tips

Pick one tool each from Code Completion and Code Editors, install them in your main IDE, run a week of real tasks and note the difference.
Run a Code Review category tool (e.g. CodeRabbit) on one real PR and compare its findings with human review.
Use a Testing category solution (e.g. Playwright plus an AI test tool) to add end-to-end tests to an existing project.
Browse Related Lists and follow links to larger directories like AI For Developers to broaden your selection horizon.