convez.ai
PluginAutomaçãoIntermediário
SUDARSHANCHAUDHARI

DroidForge

SUDARSHANCHAUDHARI/DroidForge

Automatiza keystore, assinatura, versionamento e release Android

Ver no GitHub
InicialPluginScore · de 0 a 100

Plugin Claude Code que automatiza tarefas repetitivas de desenvolvimento Android: geração de keystores, configuração de assinatura, gerenciamento de versões, catálogos Gradle e scaffolding de apps. Elimina erros manuais em 22+ apps em produção e implementa checklists de pré-lançamento para Play Store.

Instalação

$npx convez-ai SUDARSHANCHAUDHARI/DroidForge

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
1
Forks
0
Acompanhando
0
Saúde
42%
Último commit
há 1 semana
Versão
—
Issues abertas
1
Contribuidores
1

Casos de uso

  • Gerar keystores com convenções consistentes para múltiplos apps Android
  • Bumpar versionCode/versionName com verificação de semver
  • Atualizar libs.versions.toml com validação de compatibilidade AGP/Gradle/Kotlin
  • Executar checklist interativo pré-submissão Play Store
  • Scaffolding automático de novo app com configuração completa

Veredito

Plugin bem estruturado para times Android que lidam com múltiplos apps em produção. Codifica experiência operacional real (22+ apps), não apenas automação teórica. Recomendado para devs que precisam executar releases frequentes e consistentes no Play Store.

README

A tradução para o português deste README ainda está na fila.

DroidForge — Claude Code Plugin

Automate every repetitive Android dev task — keystore creation, signing config, version bumping, Gradle version catalog management, new app scaffolding, and release checklists.

Version License Platform Target


What It Does

  1. Run /droidforge:setup once — saves your developer conventions locally per project
  2. Scaffold a complete new Android app with correct package names, signing config, and version catalog
  3. Generate keystores with consistent conventions — shows the keytool command, asks before running
  4. Bump versionCode and versionName with semver (patch / minor / major)
  5. Update libs.versions.toml with compatibility checks (AGP ↔ Gradle ↔ Kotlin ↔ Compose)
  6. Run an interactive pre-submission checklist before every Play Store release

Why This Exists

By app number twenty, the Android release checklist was twelve manual steps. Keystore signing errors were occurring because the signing config wasn't regenerated after credential changes. Version codes were being submitted unchanged because versionCode lived in build.gradle.kts alongside everything else and was easy to miss.

DroidForge encodes the entire Android release preparation layer — signing config generation, version management, Gradle catalog updates, pre-submission checklist — into repeatable commands. Each command was built in response to a specific failure at fleet scale, not as a philosophical preference for automation.

The plugin manages 22+ Android apps in production under SudarshanTechLabs.


Install

Step 1 — Add the marketplace

/plugin marketplace add SUDARSHANCHAUDHARI/DroidForge

Step 2 — Install the plugin

/plugin install droidforge

Run /droidforge:setup once per project to save your conventions. All other commands use your saved config automatically — no repeated questions, no hardcoded values.


Quick Start

1. Set up your conventions

/droidforge:setup

Saves your developer name, package prefix, keystore password, and GitHub info to .claude-plugin-config.json (auto-added to .gitignore).

2. Scaffold a new app

/droidforge:new-app

Generates app/build.gradle.kts, gradle/libs.versions.toml, AndroidManifest.xml, MainActivity.kt, and .gitignore.

3. Generate a keystore

/droidforge:keystore MyApp

Shows the full keytool command, asks for confirmation, then runs it and outputs the signing config block.

4. Before submitting to Play Store

/droidforge:release-checklist

Interactive section-by-section checklist covering build, testing, Play Console, content, and post-submission.


Commands

CommandDescription
/droidforge:setupOne-time setup — saves your Android developer conventions
/droidforge:new-appScaffold a complete new Android app with all files
/droidforge:keystoreGenerate a keystore (shows keytool command, asks first)
/droidforge:signing-configWrite signing config for build.gradle.kts
/droidforge:version-bumpBump versionCode and versionName (patch / minor / major)
/droidforge:gradle-updateUpdate version catalog with compatibility checks
/droidforge:release-checklistInteractive pre-submission checklist for Play Store

Agents

Triggered automatically when relevant, or explicitly invoked:

AgentPurpose
setup-agentScaffolds complete Android project files
gradle-agentHandles Gradle / version catalog issues and updates
release-agentVersion bump, changelog generation, git tagging

Skills

Loaded automatically by Claude when relevant context is detected:

SkillLoaded when...
keystore-conventionsCreating keystores or configuring signing
package-namingCreating new apps or setting up package names
gradle-best-practicesEditing build.gradle.kts or libs.versions.toml
multi-app-structureWorking across multiple apps or managing a portfolio
release-workflowPreparing a release or building a signed AAB

Hooks

HookWhen it fires
pre-build-checkBefore gradlew bundleRelease / assembleRelease — warns if signing config or keystore is missing
post-version-bumpAfter build.gradle.kts version change — reminds about changelog and git tag

How It Works

/droidforge:setup ──► .claude-plugin-config.json (local only)
                               │
              ┌────────────────┼────────────────┐
              ▼                ▼                ▼
        new-app           keystore        version-bump
        signing-config    gradle-update   release-checklist
  • setup — saves your conventions once, all commands read from it silently
  • setup-agent — scaffolds complete Android project files on demand
  • gradle-agent — enforces AGP ↔ Gradle ↔ Kotlin ↔ Compose compatibility
  • release-agent — version bump, changelog from git log, annotated tags

Plugin Structure

DroidForge/
├── .claude-plugin/
│   ├── plugin.json              # Plugin manifest
│   └── marketplace.json         # Marketplace listing
├── commands/                    # setup, new-app, keystore, signing-config,
│                                #   version-bump, gradle-update, release-checklist
├── agents/                      # setup-agent, gradle-agent, release-agent
├── skills/                      # keystore-conventions, package-naming,
│                                #   gradle-best-practices, multi-app-structure,
│                                #   release-workflow
├── hooks/                       # pre-build-check, post-version-bump
├── README.md
├── DOCUMENTATION.md
├── CHANGELOG.md
└── LICENSE

Troubleshooting

"Run /droidforge:setup first" — Run /droidforge:setup in your project directory to create the config file.

keytool: command not found — Install a JDK or add Android Studio's bundled JDK to your PATH. See DOCUMENTATION.md for platform-specific instructions.

AGP / Gradle sync failure — Update gradle-wrapper.properties to a compatible Gradle version. See the Gradle Compatibility Matrix.


Documentation

For full details — all command examples, Gradle compatibility matrix, troubleshooting, and plugin architecture — see DOCUMENTATION.md.


Requirements

  • Claude Code
  • keytool in PATH for /droidforge:keystore (part of any Java JDK)
  • No external MCP servers required

Privacy Policy

View Privacy Policy


Author

SUDARSHANCHAUDHARI — github.com/SUDARSHANCHAUDHARI SudarshanTechLabs


License

MIT — see LICENSE

Ver o original no GitHub

Bom para

Relacionados