Add two demo GIFs (abp-agent-code-generation.gif and abp-agent-ai-review.gif) to the ABP Studio AI Agent announcement and embed them in the markdown article under docs/en/Community-Articles/2026-05-12-Introducing-Abp-Studio-Ai-Agent to illustrate code generation and AI review flows.
@ -35,6 +35,8 @@ ABP Agent is the AI coding assistant built into ABP Studio. It operates in three
The agent is **ABP-aware by default**. It is instructed to prefer ABP base classes over plain POCOs, repositories over direct `DbContext` injection, `ApplicationService` over plain services, the ABP permission system over `[Authorize(Roles=…)]`, localized strings over hardcoded text, `BusinessException`/`UserFriendlyException` over plain `Exception`, the distributed cache abstraction over raw memory cache, and background job abstractions over hand-rolled hosted services. When it is unsure about an ABP feature, it consults the official ABP documentation as a primary source of truth, not random blog posts on the web.
The agent is **ABP-aware by default**. It is instructed to prefer ABP base classes over plain POCOs, repositories over direct `DbContext` injection, `ApplicationService` over plain services, the ABP permission system over `[Authorize(Roles=…)]`, localized strings over hardcoded text, `BusinessException`/`UserFriendlyException` over plain `Exception`, the distributed cache abstraction over raw memory cache, and background job abstractions over hand-rolled hosted services. When it is unsure about an ABP feature, it consults the official ABP documentation as a primary source of truth, not random blog posts on the web.
---
---
## How ABP Agent Sees Your Application: The Analyze Engine
## How ABP Agent Sees Your Application: The Analyze Engine
@ -149,6 +151,8 @@ Two AI-assisted touches make this loop especially smooth:
The result is a *closed loop*: the agent writes the change, you (or the AI reviewer agent) review the diff, you let the agent fix the comments, you commit with an AI-suggested message, you push, and you head to GitHub for the pull request, all from inside ABP Studio.
The result is a *closed loop*: the agent writes the change, you (or the AI reviewer agent) review the diff, you let the agent fix the comments, you commit with an AI-suggested message, you push, and you head to GitHub for the pull request, all from inside ABP Studio.
Yunus Emre Kalkan
4 months ago
