chrome-extension-store-kit
Chrome Extension Store Kit
Turn an extension repository into a review-ready source package, store-assets package, and release ZIP. Preserve existing work, use real product behavior as the source of truth, and involve the user in visual identity decisions.
Start here
-
Locate the extension root and
manifest.json. If several manifests exist, identify development and built variants; ask only when the intended upload target remains ambiguous. -
Read references/chrome-web-store-spec.md. Recheck the linked official documentation when the user is actively submitting because Store requirements can change.
-
Run:
python3 scripts/audit_extension.py /absolute/path/to/extension -
Inspect the extension UI, purpose, permissions, host matches, data flows, existing brand assets, README, tests, build process, and Git status.
-
State the proposed deliverables and where they will be written. Do not push, publish, change repository visibility, or overwrite approved branding unless the user requests it.