Open the changed files in Cursor, Copilot, Claude Code, Codex, Windsurf, or your git client and confirm the agent only touched the intended scope.
AI Workflow Tools
AI Coding Ship Checklist
Generate a local launch checklist for AI-built apps and AI-assisted code changes: build, env vars, auth, payments, SEO, mobile, docs, and release notes.
Progress0/15
Must0/7
Should0/7
Optional0/1
Cursor / editor agent · Web app / landing page · Public website
Run the command that your host will run, such as npm run build, next build, mvn package, flutter build, or the platform build step. A dev server is not enough.
Open a fresh browser profile or incognito window and complete the key path as a real user: landing, sign in if needed, create or submit data, and finish the expected action.
Search for secrets, service-role keys, private tokens, test credentials, and variables accidentally exposed to the frontend after AI edits.
Confirm build command, output directory, runtime version, region, environment variables, custom domain, CORS, redirects, and callback URLs.
Search visible pages, README, errors, empty states, and meta tags for lorem ipsum, TODO, fake testimonials, model disclaimers, or generic marketing text.
Check 360px to 430px widths for horizontal scroll, fixed buttons covering inputs, clipped dialogs, overflowing cards, and long words breaking layout.
Force failed network calls, empty lists, invalid forms, expired sessions, and 404 or not-found states. AI-built happy paths often miss these.
Run the checks that exist in the project. If there are no automated tests, write a short manual test list instead of pretending coverage exists.
Document install, local dev, build, deploy, required env vars, known limitations, and rollback steps so the next AI session or teammate has context.
For payments or external services, confirm repeated webhook delivery does not create duplicate orders, credits, emails, or records.
For public pages, inspect meta title, description, canonical URL, robots rules, sitemap inclusion, Open Graph, and whether placeholder pages are indexable.
Make sure headings, FAQ answers, definitions, and tool descriptions give short, factual answers that search engines and AI assistants can quote accurately.
For APIs or external integrations, verify request payload shape, status codes, auth headers, and cURL examples that AI may have invented.
Tab through the main UI, verify focus is visible, labels are attached to inputs, buttons have names, and dialogs can be closed without a mouse.
This tool is part of AI Workflow Tools. View the full workflow · AI Coding Workflow Checklist Before You Ship
About this tool
The AI Coding Ship Checklist is a local launch checklist for AI-built apps and AI-assisted code changes. It helps people who use Cursor, GitHub Copilot, Claude Code, Codex, ChatGPT, Windsurf, Replit Agent, Bolt, Lovable, or similar tools check the work that still has to happen after the model writes code.
How to use this tool
Choose the AI coding source, project type, stack, launch goal, and risky features. The tool generates a checklist you can complete before publishing or handing the project back to an AI agent.
- Select how the code was produced: editor agent, Copilot, CLI agent, copied chat code, vibe coding builder, or mixed manual work.
- Choose the project type, stack, launch target, and features such as auth, payments, database, public SEO, i18n, file upload, admin, and external APIs.
- Work through Must, Should, and Optional checks. Add evidence for build output, env review, mobile testing, SEO inspection, and release notes.
- Copy the Markdown report and keep it in a pull request, issue, README, release note, or the next AI coding prompt.
Features
This first version does not upload code, call a model, or claim to automatically judge quality. It generates a practical local checklist from explicit choices.
- Rules for AI-generated web apps, APIs, mobile releases, browser tools, and vibe-coded prototypes.
- Checks for build commands, environment variables, secrets, auth, payments, webhooks, SEO, mobile layout, docs, observability, and rollback.
- Local saving for configuration, checked items, and evidence notes.
- Markdown export for PRs, issue trackers, release notes, and AI agent handoff prompts.
FAQ
What is an AI coding checklist?
An AI coding checklist is a release checklist for code generated or modified with AI coding tools. It focuses on verification: diff review, build commands, tests, secrets, deployment config, auth, payments, SEO, mobile layout, and release notes.
Does this tool scan my repository?
No. The checklist is generated locally from the options you choose. It does not upload files, read your repository, call an AI model, or automatically judge code quality.
Who is this useful for?
It is useful for developers using Cursor, Copilot, Claude Code, Codex, or Windsurf, and for non-developers shipping apps from Bolt, Lovable, Replit Agent, or ChatGPT-generated code.
Can I use it for vibe coding projects?
Yes. Select the AI-built prototype or vibe coding builder options. The checklist will include prototype limits, placeholder copy, env vars, mobile checks, and public launch risks.