mcpField
A
android-ci-cd-release-playstore

android-ci-cd-release-playstore

github.com/krutikjainCloud & DevOps1463 installsUpdated 31w ago
Repository

About android-ci-cd-release-playstore

A release automation skill for Android engineering teams, covering CI, versioning, signing boundaries, release channels, and Play-ready delivery. It emphasizes reproducible checks, actionable failure guidance, and credential protection.

Key features

  1. 01Plan Android CI and release workflows
  2. 02Handle versioning and signing boundaries
  3. 03Set up release channels and Play delivery
  4. 04Prefer reproducible CI checks
  5. 05Keep signing credentials out of examples

Use cases

  1. 01Validate repository CI and version metadata flows
  2. 02Dry-run canary and stable release scripts
  3. 03Design Android signing and release automation
  4. 04Provide clear remediation for CI failures

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/krutikjain/android-agent-skills --skill android-ci-cd-release-playstore

After installing, type/android-ci-cd-release-playstorein Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

agents/
openai.yaml
references/
official-links.md
patterns.md
scenarios.md
scripts/
run_examples.sh

Details

From the project README

Android CI CD Release PlayStore

When To Use

  • Use this skill when the request is about: android ci cd pipeline, play store release automation, android signing and release.
  • Primary outcome: Automate Android CI, versioning, signing boundaries, release channels, and Play-ready delivery workflows.
  • Handoff skills when the scope expands:
  • android-gradle-build-logic
  • android-security-best-practices

Workflow

  1. Scope the risk surface: correctness, security, performance, test depth, or release automation.
  2. Pick the narrowest verification strategy that still catches the likely regressions.
  3. Instrument the workflow so failures are actionable rather than just red.
  4. Run the relevant checks on the showcase apps and packaging outputs.
  5. Capture any residual risk with explicit follow-up work and owner skills.

Guardrails

  • Prefer reproducible checks in CI over one-off local heroics.
  • Fail with a precise remediation path instead of a vague quality gate.
  • Keep secrets, signing material, and production credentials out of examples and fixtures.
  • Treat performance and security work as engineering tasks with evidence, not folklore.

Anti-Patterns

  • Adding more tests without increasing signal.
  • Shipping benchmarks or security scans that no one can reproduce.
  • Hard-coding release credentials into build logic.
  • Using synthetic metrics with no user-impact interpretation.

Examples

Happy path
  • Scenario: Validate the repo CI workflow, adapter generation, and version metadata flow.
  • Command: python3 scripts/validate_repo.py
Edge case
  • Scenario: Check canary and stable release script behavior before tagging.
  • Command: python3 scripts/release.py --channel canary --dry-run
Failure recovery
  • Scenario: Avoid routing pure build-logic or security work into release automation.
  • Command: python3 scripts/eval_triggers.py --skill android-ci-cd-release-playstore

Done Checklist

  • The implementation path is explicit, minimal, and tied to the right Android surface.
  • Relevant example commands and benchmark prompts have been exercised or updated.
  • Handoffs to adjacent skills are documented when the request crosses boundaries.
  • Official references cover the chosen pattern and the main migration or troubleshooting path.

Official References

Comments

Markdown supported