Skip to content

binayshaw7777/Leaflekt-Maps / .agents/skills/android-gradle-release-readiness

android-gradle-release-readiness

Verified

Keep module structure, naming, and build configuration ready for future publishing. Handle new Gradle modules, library metadata, namespace and artifact readiness.

Android Gradle Release Readiness

Purpose:

  • Keep module structure, naming, and build configuration ready for future publishing.

When to use:

  • Adding new Gradle modules
  • Preparing library metadata
  • Reviewing namespace and artifact readiness

Workflow:

  1. Confirm module boundaries.
  2. Keep reusable dependencies inside the library and sample-only ones in the app.
  3. Prepare package/namespace choices that will not need churn later.
  4. Verify buildability after structural changes.

Outputs:

  • Gradle change list
  • Packaging notes
  • Verification results
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall