feat: add android-cicd skill for automated Google Play publishing

[PapiScholz]

Summary

• Adds android-cicd skill under cli-tool/components/skills/development/android-cicd/
• Automates the full Android CI/CD pipeline to Google Play via GitHub Actions
• Installable via npx android-cicd

What this skill does

• Auto-detects Android framework (TWA, React Native, Flutter, native Android)
• Generates upload keystore cross-platform (Windows + macOS/Linux)
• Configures GitHub Secrets automatically via gh CLI
• Scaffolds .github/workflows/publish-android.yml with multi-stage pipeline
• Auto-increments versionCode on every push to main

Multi-stage pipeline

Git event	Google Play track
Push to main	internal
Tag v*-alpha	alpha
Tag v*-beta	beta
Tag v*	production

npm: https://www.npmjs.com/package/android-cicd

---

Summary by cubic

Adds the android-cicd skill to automate building and publishing Android apps to Google Play via GitHub Actions. Supports TWA, React Native, Flutter, and native projects with a multi‑stage release workflow.

• Area: components (cli-tool/components/)
• New component added (android-cicd) — regenerate catalog (docs/components.json) after merge
• Install via npx android-cicd; maps push/tag to tracks: internal, alpha, beta, production
• Auto-bumps versionCode on pushes to main
• Requires GitHub secrets: KEYSTORE_FILE, KEYSTORE_PASSWORD, KEY_ALIAS, KEY_PASSWORD, GOOGLE_PLAY_SERVICE_ACCOUNT_JSON

^{Written for commit 17e047a. Summary will update on new commits.}

[vercel]

@PapiScholz is attempting to deploy a commit to the Daniel Avila's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

👋 Thanks for contributing, @PapiScholz!

This PR touches cli-tool/components/** and has been marked review-pending.

What happens next

1. 🤖 Automated security audit runs and posts results on this PR.
2. 👀 Maintainer review — a human reviewer validates the component with the component-reviewer agent (format, naming, security, clarity).
3. ✅ Merge — once approved, your PR is merged to main.
4. 📦 Catalog regeneration — the component catalog is rebuilt automatically.
5. 🚀 Live on aitmpl.com — your component appears on the website after deploy.

While you wait

• Check the Security Audit comment below for any issues to fix.
• Make sure your component follows the contribution guide.

This is an automated message. No action is required from you right now — a maintainer will review soon.

[cubic-dev-ai]

No issues found across 1 file