prepush-android
Skill56 starsChanged 34 days agoApache-2.0View on GitHub
Run the fast Android pre-push smoke check for changed Kotlin modules, then interpret emulator CI failures from boot diagnostics before treating them as regressions.
In this repository35 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/AGENTS.mdAGENTS.md
- android/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .github/CLAUDE.mdCLAUDE.md
- ios/CLAUDE.mdCLAUDE.md
- auto-mobile-code-reviewSkill
- ci-failure-triageSkill
- github-pr-feedbackSkill
- ios-swift-ciSkill
- node-prepushSkill
- prepush-androidSkill
- shell-prepushSkill
- android-gradlewSkill
- auto-mobile-code-reviewSkill
- bun-tasksSkill
- check-ciSkill
- ci-failure-triageSkill
- dead-codeSkill
- device-session-lifecycleSkill
- fan-out-fan-inSkill
- github-cliSkill
- github-pr-feedbackSkill
- ios-swift-ciSkill
- manual-testSkill
- node-prepushSkill
- observeSkill
- pr-analysisSkill
- push-my-prsSkill
- push-prSkill
- researchSkill
- shell-prepushSkill
- ship-issueSkill
- testSkill
- validateSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Run scripts/prepush-android.sh from the repository root before pushing android/ changes.
- Distinctive: line 9
Treat its scoped Detekt result as a local smoke check, not a replacement for CI's full-tree Detekt job.
- Very specific: line 12
Use android-gradlew for targeted Gradle validation and check-ci for exact-head CI logs and artifacts.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Android Pre-push Smoke Check
- Run
scripts/prepush-android.shfrom the repository root before pushingandroid/changes. - Treat its scoped Detekt result as a local smoke check, not a replacement for CI's full-tree Detekt job.
- Copy
android/local.propertiesfrom a working checkout into a new Android worktree before Gradle work. - For Playground or JUnit-runner emulator CI red, inspect
.github/actions/android-emulatorboot diagnostics first: missing runner-health means infra/runner readiness, while a booted emulator with failed tests is a regression. - Use
android-gradlewfor targeted Gradle validation andcheck-cifor exact-head CI logs and artifacts.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.