DEV Community: Harsh Rastogi

Shopify's AI Self-Review Tool: How to Pass App Store Review on the First Try

Harsh Rastogi — Sun, 26 Apr 2026 12:41:53 +0000

Shopify Just Released an AI Agent That Reviews Your App Before Shopify Does

If you've ever submitted an app to the Shopify App Store, you know the drill. You build for weeks, hit submit, wait days for review, get rejected for something you could have caught in five minutes, fix it, resubmit, and wait again. Weeks of back-and-forth for issues that should never have made it to a human reviewer.

Shopify just fixed that.

What Changed

On April 20, 2026, Shopify shipped three updates to the app submission process that fundamentally change how developers get apps approved:

1. AI-Powered Self-Review Tool

Before you submit your app, you can now run an AI agent against your codebase that checks compliance with Shopify's App Store requirements. It takes about two minutes. You get a compliance report that tells you what's passing, what needs fixing, and why.

Here's how it works: on your app submission page, you'll find a pre-built prompt. Copy it, run it against your codebase in any AI assistant (Claude Code, Cursor, Codex), and the agent — powered by the Shopify AI Toolkit — checks your app against the specific requirements for your app type and category. The results are tailored to what you're building, not a generic checklist.

You can run it as many times as you need. Fix issues, run again, confirm everything passes, then submit. There's a small token cost per run depending on your model provider, but compared to weeks of review back-and-forth, it's nothing.

Important caveat: passing the AI self-review does NOT guarantee approval. The tool is a recommendation system, not a blocker. But Shopify is direct about this — if the AI flags something, there's a high likelihood the human reviewer will flag the same thing. Fix it before submitting.

This is available directly on your app submission page in the Partner Dashboard and through the Shopify AI Toolkit.

The key insight here: Shopify's review team was drowning. Back in February 2026, they acknowledged that submission volume had grown faster than their review capacity, leading to longer wait times and frustrated developers. This tool is their answer — shift the obvious compliance checks to AI so human reviewers can focus on the nuanced decisions that actually need human judgment.

2. Review Feedback Moved to Partner Dashboard

Previously, review feedback came through email — scattered, hard to track, easy to miss a requirement buried in a thread. Now, every requirement has its own status tracker in the Partner Dashboard under App > Distribution. You see exactly what failed, read the reviewer's comments, ask questions directly through a notes section, and mark issues as resolved before resubmitting.

The critical change: resubmission is blocked until ALL flagged issues are resolved. You can't partially fix things and resubmit hoping the rest slides through. This sounds strict, but it's actually the smartest thing Shopify did — it ensures that when your app re-enters the queue, it's genuinely ready. No more wasted rounds where you fix 3 of 5 issues and get bounced again for the remaining 2.

You can also disagree with a requirement failure. Use the notes section to explain why you believe it should pass, and the reviewer will see your reasoning during re-review.

3. Automated Pre-Submission Checks

Theme app extensions and App Store listing requirements are now verified automatically during pre-submission. Instant feedback instead of waiting for manual review. If your app icon is the wrong size, your compliance webhooks aren't configured, or your listing fields are incomplete — you know immediately, not three days later.

Why This Matters (From Someone Who Builds Shopify Apps)

I build Shopify apps at Modelia — a generative AI platform for fashion image generation. Our app serves hundreds of merchants and generates thousands of AI images daily. I've been through the Shopify app review process multiple times, and I can tell you exactly why this update matters.

The Old Process Was Broken

Here's what a typical app submission used to look like:

Build app for 2-4 weeks
Submit to App Store
Wait 4-7 business days for initial review
Receive email with 3-5 issues (some obvious, some nuanced)
Fix issues — 1-3 days
Resubmit and go back into the queue
Wait another 3-5 days
Get 1-2 more issues
Fix, resubmit, wait again
Finally approved — total elapsed time: 3-6 weeks

The worst part wasn't the wait. It was that at least half the rejection reasons were things an automated check could have caught: wrong webhook subscriptions, missing OAuth scopes, incorrect API version usage, Polaris design violations, listing field issues. You'd wait a week to learn something a linter could have told you in seconds.

The New Process Eliminates the Obvious

With the AI self-review tool, step 2 now looks like:

Run AI self-review (~2 minutes)
Get compliance report
Fix flagged issues BEFORE submitting
Submit a clean app
Human reviewer focuses on actual quality and security concerns
Faster approval with fewer rounds

This doesn't just save developer time — it saves Shopify's review team time too. Fewer apps bouncing back for trivial issues means the queue moves faster for everyone.

What the AI Agent Actually Checks

Based on the announcement and the Shopify AI Toolkit documentation, the self-review tool validates:

GraphQL query compliance — Are you using the correct API version? Are your queries structured properly against Shopify's current schemas?
Webhook implementation — Are compliance webhooks (customer data request, customer data erasure, shop data erasure) properly subscribed?
OAuth flow — Is your authentication flow following Shopify's current standards?
Liquid template validation — For theme app extensions, are your Liquid files valid against Shopify's schemas?
UI extension structure — Are your extensions following the required patterns?
App Store listing — Are all required fields populated with valid content?
Polaris compliance — Does your admin UI follow Shopify's design system requirements?

The agent essentially runs the same checks a human reviewer would on the first pass — the mechanical, rule-based checks that don't require human judgment.

How to Use It

Option 1: Partner Dashboard (Simplest)

Go to your app in the Partner Dashboard
Navigate to App > Distribution
Before hitting submit, click the self-review option
Wait ~2 minutes for the compliance report
Fix any flagged issues
Submit when everything passes

Option 2: Shopify AI Toolkit (For Power Users)

If you're already using the Shopify AI Toolkit with Claude Code, Cursor, or other AI coding tools, the self-review is available through the toolkit. This means you can run compliance checks directly from your IDE while developing — not just at submission time.

# If using Claude Code
/plugin marketplace add Shopify/shopify-ai-toolkit
/plugin install shopify-plugin@shopify-ai-toolkit

# Then ask Claude to run the self-review
"Run the Shopify app self-review against our codebase"

This is the more powerful approach because you can catch issues during development, not after you think you're done.

What This Signals About Shopify's Direction

This update is part of a broader pattern from Shopify in 2026:

AI Toolkit launched April 9 — connecting coding agents to Shopify's platform with live documentation, schema validation, and store management. The self-review tool extends this toolkit into the submission pipeline.

Agentic commerce is becoming real — Shopify shipped Catalog MCP, Storefront MCP, Checkout MCP, and the Universal Commerce Protocol (UCP). They're building an ecosystem where AI agents interact with stores as first-class citizens. If Shopify expects AI agents to build and manage stores, it makes sense that AI agents should also review the apps running on those stores.

The "AI-first engineering" philosophy — Shopify's VP of Engineering publicly said "if you don't figure out how to harness agents in 2026, you'll be behind." They're not just saying that — they're building the infrastructure to prove it. The self-review tool is another brick in that wall.

Practical Advice

If you're building or maintaining a Shopify app, here's what I'd do now:

Run the self-review on your existing app — even if you're not planning a submission. The compliance report will flag technical debt you didn't know existed. At Modelia, we discovered issues with our webhook configuration that hadn't caused problems yet but would have flagged in any future review.

Integrate the AI Toolkit into your dev workflow — don't wait for submission time. Run schema validation and compliance checks as part of your development cycle. Catching a GraphQL query issue during development is minutes; catching it during review is weeks.

Update your CI/CD — if you have automated deployments, consider adding the AI Toolkit's validation checks as a pre-deployment gate. This ensures every release is compliant before it reaches merchants.

Track your requirements in the Partner Dashboard — if you have an app currently in review or about to submit, switch to the dashboard-based tracking. The structured workflow is significantly better than email threads.

FAQ — Quick Answers

Does passing the AI self-review guarantee approval?
No. It's a recommendation system, not an auto-approve gate. But if the AI flags it, the human reviewer almost certainly will too.

Can I run the self-review while my app is already in the queue?
Yes. Running it doesn't kick you out of the queue. You only lose your position if you resubmit.

Can I resubmit with some issues still unresolved?
No. The dashboard blocks resubmission until all requirements are marked resolved. This is intentional — it prevents wasted review rounds.

Can I disagree with a flagged requirement?
Yes. Use the notes section on each requirement to explain your reasoning. Reviewers see these notes during re-review and can adjust the status.

Does the AI Toolkit cost money?
The toolkit itself is free. Running the self-review prompt has a small token cost depending on your AI model provider (Claude, GPT-4, etc.). Negligible compared to weeks of review delays.

Will I still get email notifications?
Yes — status change emails still arrive. But detailed requirement-level feedback now lives in the dashboard, not the email body.

Bottom Line

Shopify's AI self-review tool isn't revolutionary technology — it's the right tool at the right time. The app review backlog was a genuine pain point that drove developers away from the platform. By automating the mechanical compliance checks and giving developers instant feedback, Shopify is removing friction from the developer experience while maintaining the quality bar.

For Shopify app developers, this is an unambiguous win. Run the self-review before every submission. Use the AI Toolkit during development. The days of waiting a week to learn your webhook config is wrong are over.

Harsh Rastogi is a Full Stack Engineer at Modelia, building production Generative AI systems for fashion commerce on the Shopify platform. He writes about AI systems, developer tooling, and production engineering at harshrastogi.tech.

Claude Opus 4.7: What Developers Actually Need to Know

Harsh Rastogi — Sat, 18 Apr 2026 19:38:10 +0000

Claude Opus 4.7: What Developers Actually Need to Know

Anthropic just released Claude Opus 4.7, and it's their most significant upgrade for engineers this year. Here's what matters, what changed, and what it means for how we build with AI — from someone who uses Claude in production daily.

The Big Picture

Opus 4.7 launched on April 16, 2026. It's a direct upgrade to Opus 4.6, available at the same pricing ($5/$25 per million tokens input/output) across the Claude API, Amazon Bedrock, Google Cloud Vertex AI, and Microsoft Foundry.

The headline: this model was built for engineers who delegate hard work to AI agents. It's not just smarter — it's more reliable when left unsupervised on complex, multi-step tasks. And that's the shift that matters most.

What Actually Changed

1. Advanced Software Engineering — The Killer Feature

Opus 4.7 shows major gains on the hardest coding tasks. Early testers report being able to hand off complex work — the kind that previously needed close supervision — with confidence.

The key improvement is self-verification. Opus 4.7 doesn't just generate code and ship it. It catches its own logical faults during the planning phase, verifies outputs before reporting back, and resists the pattern of generating plausible-but-incorrect fallbacks that plagued earlier models.

For production engineers, this changes the trust equation. With Opus 4.6, I'd review every line of AI-generated code for critical paths. With 4.7, the model is doing more of that review itself — and doing it well enough that early benchmarks show a 13% resolution improvement over 4.6 on a 93-task coding benchmark, including solving four tasks that neither Opus 4.6 nor Sonnet 4.6 could handle.

2. Vision — 3x Resolution Upgrade

Opus 4.7 supports images up to 2,576 pixels on the long edge — more than three times the resolution of prior Claude models. This sounds incremental until you consider what it enables: reading dense technical diagrams, processing high-resolution screenshots without downscaling, analyzing architectural drawings, and extracting information from complex UI mockups.

For engineering workflows where you're feeding Claude screenshots of dashboards, error logs, or architecture diagrams, this is a meaningful quality-of-life upgrade.

3. New Effort Controls — xhigh Level

Anthropic introduced a new effort level: "xhigh" — sitting between "high" and "max." This gives developers finer-grained control over the tradeoff between reasoning depth and response latency.

For agentic coding use cases, Anthropic recommends starting with "high" or "xhigh" effort. The practical implication: you can get near-max quality reasoning at lower latency and cost for most tasks, and reserve "max" for genuinely hard problems.

4. Task Budgets (Public Beta)

This is the feature enterprise teams have been waiting for. Task budgets let developers set limits on how much reasoning Claude can do on a given task — controlling both cost and execution time for long-running agent workflows.

If you're running dozens of concurrent agents (like in CI/CD pipelines or automated code review), unpredictable token costs have been a real pain point. Task budgets directly address this.

5. Cybersecurity Safeguards — Project Glasswing

Here's where it gets interesting. Opus 4.7 is Anthropic's first model with built-in cyber safeguards that automatically detect and block prohibited or high-risk cybersecurity uses. During training, Anthropic actually experimented with reducing the model's cyber capabilities — a deliberate tradeoff between capability and safety.

This is directly tied to Claude Mythos Preview, Anthropic's most powerful model that isn't publicly available due to security concerns around its cyber capabilities. Opus 4.7 is the testing ground for safeguards that could eventually allow Mythos-class models to be released broadly.

What This Means for Production AI Systems

I build production Generative AI systems at Modelia, and previously built an Agentic AI interviewer at Asynq. Here's what Opus 4.7 changes in practice:

Agentic Workflows Get More Reliable

The self-verification capability is the most impactful change for anyone running AI agents in production. When your agent is making decisions autonomously — processing resumes, generating images, executing multi-step workflows — the model's ability to catch its own mistakes before acting on them reduces the error rate that previously required human checkpoints.

This doesn't eliminate the need for human-in-the-loop (you still want that for critical actions), but it makes the "autonomous within bounds" pattern much more practical.

The Cost Equation Shifts

Task budgets + xhigh effort level = more predictable costs for agentic workloads. Before, you'd either overspend with "max" effort everywhere or under-invest with "high" and get inconsistent results. Now you can fine-tune per task:

Code generation → xhigh effort with task budget
Code review → high effort (faster, cheaper)
Complex debugging → max effort (when you need it)

Updated Tokenizer — Plan for It

One gotcha: Opus 4.7 uses an updated tokenizer. The same input can map to roughly 1.0-1.35x more tokens depending on content type. If you're managing token budgets carefully (especially at scale), you'll need to account for this. It's not a dealbreaker, but it can surprise you if you're not expecting the 15-35% increase.

Migration Checklist

If you're currently on Opus 4.6, here's what to do:

Update your model string: Change claude-opus-4-6 to claude-opus-4-7 in your API calls.

Test your prompts: Anthropic notes that Opus 4.7 responds differently to certain input patterns. Prompts optimized for 4.6 may need adjustment. In my experience, Opus 4.7 is more precise with instruction following — which means vague prompts that 4.6 interpreted generously might need to be more explicit.

Account for tokenizer changes: Monitor your token usage after switching. The 1.0-1.35x increase in tokens per input means your costs may rise slightly even at the same per-token pricing.

Test effort levels: If you were using "high" everywhere, try "xhigh" for your most complex tasks. If you were using "max" everywhere, you can likely downgrade some tasks to "xhigh" and save on both latency and cost.

Check deprecation timeline: Opus 4.6 will be deprecated, and Claude Sonnet 4 and Claude Opus 4 are retiring on June 15, 2026. Plan your migration now, not last minute.

The Mythos Shadow

The most interesting subtext of this release is what it says about Claude Mythos Preview. Anthropic is being remarkably transparent: Opus 4.7 is good, but Mythos is better. They're essentially saying "we have a more powerful model that we won't release because the cybersecurity implications are too significant."

Whether you view this as responsible AI development or strategic positioning (or both), it signals that the frontier of what's possible in AI is further ahead than what's currently available. The safeguards being tested on Opus 4.7 are practice for the eventual broader release of Mythos-class capabilities.

For engineers building production systems, the takeaway is pragmatic: Opus 4.7 is the best generally available model right now. Use it. But design your systems to be model-agnostic — the upgrade cycle is accelerating (Opus 4.5 → 4.6 → 4.7, each two months apart), and your architecture should handle model swaps without rewrites.

Bottom Line

Opus 4.7 isn't a revolutionary leap — it's a meaningful, practical upgrade that makes AI-assisted engineering more reliable and more controllable. The self-verification, task budgets, and xhigh effort level are the features that will matter most in day-to-day engineering work.

If you're building with Claude in production, upgrade. If you're evaluating AI models for your engineering workflow, this is the strongest generally available option on the market right now.

The pace of improvement is what should excite you most: two-month upgrade cycles, with each release meaningfully better than the last. The compounding effect of that pace over the next 12 months will change what's possible in software engineering.

Harsh Rastogi is a Full Stack Engineer at Modelia, building production Generative AI systems. He previously built an Agentic AI interviewer at Asynq. He writes about AI systems, system design, and production engineering at harshrastogi.tech.