agentleFS
Sign inStart free
khadinakbarlabskhadinakbarlabs/shopify-app-builder/skills/app-release-readiness/SKILL.md

app-release-readiness

Skill2 starsChanged 39 days agoMITView on GitHub

Create and execute an evidence-based Shopify app release checklist covering security, privacy, billing, UX, tests, hosting, migrations, review assets and post-launch support. Deployment and submission require explicit authorization.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After deployment verify actual server health, correct configuration version, authorized install and core task.

    line 28
  2. Distinctive:

    Use a compact gate list with observed evidence, blocker and next action.

    line 32
  3. Distinctive:

    If account access prevents a test, mark it unverified and explain the exact manual check.

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Know what is ready before you ship

A passing build is not a production release. Shopify review and Built for Shopify designation are separate external decisions.

Start here

Inspect the app type/distribution, intended release target, current docs and actual feature set. Explain "ready", "blocked" and "not tested"; don't invent a numerical readiness score. Do not make optional B2B, Functions, Hydrogen, paid ads or paid billing mandatory for every app.

Release gates

  1. Core feature: install, first-value task, saved state, error recovery, uninstall/reinstall and relevant extensions on an authorized dev store.
  2. Security: app-auth, minimal scopes, shop isolation, validated inputs, injection/XSS/CSRF protections appropriate to framework, abuse/rate limits, secrets and dependency audit, redacted logging.
  3. Events and privacy: webhooks, duplicate/out-of-order handling, durable processing, uninstall and applicable compliance requests, protected-data approval, data minimization and documented retention/deletion. A 200 response alone is not cleanup.
  4. Commerce: app-billing if paid, test-mode decline/cancel/trial/entitlements, disclosed limits and no unauthorized real charge.
  5. Usability: app-accessibility, ux-onboarding, ux-empty-error-states, mobile/keyboard and long-text testing.
  6. Reliability: app-performance, primary-path regression tests, queues/retries, observed error handling and tenant-safe caching.
  7. Operations: app server/database hosting separate from Shopify config/extensions, HTTPS and URLs, secret-store configuration confirmed without revealing values, migration backup/recovery, health checks, rollback, error alerts and support runbook.
  8. Review: current App Store requirements, product evidence, accurate screenshots, privacy/terms/support URLs, distribution and protected-data eligibility. Use app-listing-optimization; built-for-shopify-standards is an optional additional program review.

Execute safely

Present release target, changes, costs and recovery path. Obtain explicit approval for deployment, production migrations, scope changes, charges and submissions. Use the project's existing release process; preserve unrelated changes and never perform irreversible cleanup silently. After deployment verify actual server health, correct configuration version, authorized install and core task. Keep source/build, deployment, store QA and marketplace acceptance separate.

Deliver a beginner-readable handoff

Use a compact gate list with observed evidence, blocker and next action. Include only redacted diagnostics. Provide a short support/maintenance plan: monitor errors, test API upgrades before cutover, rehearse data recovery, maintain policies, and respond to merchant feedback. If account access prevents a test, mark it unverified and explain the exact manual check. Never award approval or call untested gates passed.

Sources: Shopify app review, protected data, privacy compliance.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free