--- title: "How We Ship Quality at mabl" url: https://daily.dev/posts/how-we-ship-quality-at-mabl-yx9gy8bal source_url: https://www.mabl.com/blog/how-we-ship-quality-at-mabl type: article source: "Mabl Engineering Blog" published: 2026-06-11T13:01:04.482Z updated: 2026-06-11T13:03:07.635Z tags: ["testing", "cicd", "ai-coding"] reading_time: 18 upvotes: 0 comments: 0 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # How We Ship Quality at mabl **[Mabl Engineering Blog](https://daily.dev/sources/mabl)** · 18 min read · 0 upvotes · 0 comments ## Summary mabl's engineering team describes how they scaled their verification layer to match a 4.5x increase in PR throughput (179 to 810 PRs/month) driven by AI coding agents. Their stack includes seven layers from local TypeScript checks to 24/7 production monitoring, using two completely separate mabl stacks (prod and dev) that test each other to avoid shared fate. Key practices include: scoped test routing via Claude skills, automatic Claude Opus PR reviews with on-demand Codex second opinions, an MCP server that feeds deployment test results directly into coding assistants, and treating the test suite as a maintained product with composable flows, flake containment hierarchies, and self-describing plan names. 31% of PRs now flow through agent-only review. The core insight is that at AI-native throughput, the verification layer becomes the system's organizing principle, not a CI detail. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: --- Tags: [#testing](https://daily.dev/tags/testing), [#cicd](https://daily.dev/tags/cicd), [#ai-coding](https://daily.dev/tags/ai-coding) [View this post on daily.dev](https://daily.dev/posts/how-we-ship-quality-at-mabl-yx9gy8bal)